diff options
| author | brian greenfield <briang@cpan.org> | 2011-07-29 13:55:10 +0100 |
|---|---|---|
| committer | Father Chrysostomos <sprout@cpan.org> | 2011-08-04 13:07:55 -0700 |
| commit | c9d1da359da6a3d527d7a64d9eed3f8ab441bb8b (patch) | |
| tree | 9a731cfa9d30d1eba9da43545582b5579451187c | |
| parent | 54d18cdceede591a29c5e0beebe4eec4a0baae42 (diff) | |
| download | perl-c9d1da359da6a3d527d7a64d9eed3f8ab441bb8b.tar.gz | |
Fix typos in pod/perlgit.pod
| -rw-r--r-- | pod/perlgit.pod | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/pod/perlgit.pod b/pod/perlgit.pod index eef06dab6d..a316e7bf97 100644 --- a/pod/perlgit.pod +++ b/pod/perlgit.pod @@ -51,7 +51,7 @@ branches in the repository: The branches that begin with "origin" correspond to the "git remote" that you cloned from (which is named "origin"). Each branch on the -remote will be exactly tracked by theses branches. You should NEVER do +remote will be exactly tracked by these branches. You should NEVER do work on these remote tracking branches. You only ever do work in a local branch. Local branches can be configured to automerge (on pull) from a designated remote tracking branch. This is the case with the @@ -720,7 +720,7 @@ repository is "p5p"): $ git rebase p5p/blead You will see your commits being re-applied, and you will then be able to -push safetly. More information about rebasing can be found in the +push safely. More information about rebasing can be found in the documentation for the git-rebase(1) command. For larger sets of commits that only make sense together, or that would |