summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRené Genz <liebundartig@freenet.de>2017-04-30 14:54:25 (GMT)
committerJunio C Hamano <gitster@pobox.com>2017-05-01 02:03:08 (GMT)
commitd395745d8108568934006c6411146bc93cc54737 (patch)
tree65c7c99d05c27aee23515a4536cabb10d28734bc
parent49800c940790cc7465d1b03e08d472ffd8684808 (diff)
downloadgit-d395745d8108568934006c6411146bc93cc54737.zip
git-d395745d8108568934006c6411146bc93cc54737.tar.gz
git-d395745d8108568934006c6411146bc93cc54737.tar.bz2
doc: git-pull.txt use US spelling, fix minor typo
Signed-off-by: René Genz <liebundartig@freenet.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--Documentation/git-pull.txt5
1 files changed, 3 insertions, 2 deletions
diff --git a/Documentation/git-pull.txt b/Documentation/git-pull.txt
index 4470e4b..942af8e 100644
--- a/Documentation/git-pull.txt
+++ b/Documentation/git-pull.txt
@@ -67,7 +67,7 @@ with uncommitted changes is discouraged: while possible, it leaves you
in a state that may be hard to back out of in the case of a conflict.
If any of the remote changes overlap with local uncommitted changes,
-the merge will be automatically cancelled and the work tree untouched.
+the merge will be automatically canceled and the work tree untouched.
It is generally best to get any local changes in working order before
pulling or stash them away with linkgit:git-stash[1].
@@ -210,7 +210,8 @@ EXAMPLES
current branch:
+
------------------------------------------------
-$ git pull, git pull origin
+$ git pull
+$ git pull origin
------------------------------------------------
+
Normally the branch merged in is the HEAD of the remote repository,