summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2017-06-05 09:18:13 +0900
committerJunio C Hamano <gitster@pobox.com>2017-06-05 09:18:14 +0900
commitac935fca90b3258820c6fea9b7892eab184ef9db (patch)
treed5574577f8e664b1e059fd9b2388b96ecb95647a
parent35898eafab5dfd4ebc9daf2f4e422a1d4771954b (diff)
parent0c79cee697f7f4e304c53108ee895b706df1322e (diff)
downloadgit-ac935fca90b3258820c6fea9b7892eab184ef9db.tar.gz
Merge branch 'ad/pull-remote-doc'
Docfix. * ad/pull-remote-doc: docs: fix formatting and grammar
-rw-r--r--Documentation/git-pull.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/git-pull.txt b/Documentation/git-pull.txt
index 942af8e0f7..e414185f5a 100644
--- a/Documentation/git-pull.txt
+++ b/Documentation/git-pull.txt
@@ -159,15 +159,15 @@ present while on branch `<name>`, that value is used instead of
In order to determine what URL to use to fetch from, the value
of the configuration `remote.<origin>.url` is consulted
-and if there is not any such variable, the value on `URL: ` line
-in `$GIT_DIR/remotes/<origin>` file is used.
+and if there is not any such variable, the value on the `URL:` line
+in `$GIT_DIR/remotes/<origin>` is used.
In order to determine what remote branches to fetch (and
optionally store in the remote-tracking branches) when the command is
run without any refspec parameters on the command line, values
of the configuration variable `remote.<origin>.fetch` are
consulted, and if there aren't any, `$GIT_DIR/remotes/<origin>`
-file is consulted and its `Pull: ` lines are used.
+is consulted and its `Pull:` lines are used.
In addition to the refspec formats described in the OPTIONS
section, you can have a globbing refspec that looks like this: