summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNguyễn Thái Ngọc Duy <pclouds@gmail.com>2015-12-04 18:09:32 (GMT)
committerJunio C Hamano <gitster@pobox.com>2015-12-04 21:09:48 (GMT)
commit56a8aea0c61c26e2644514ede24cec35b06ee0d0 (patch)
tree678c0137bc327060a6094ce40ff02094e32a42d4
parent24358560c3c0ab51c9ef8178d99f46711716f6c0 (diff)
downloadgit-56a8aea0c61c26e2644514ede24cec35b06ee0d0.zip
git-56a8aea0c61c26e2644514ede24cec35b06ee0d0.tar.gz
git-56a8aea0c61c26e2644514ede24cec35b06ee0d0.tar.bz2
git-check-ref-format.txt: typo, s/avoids/avoid/
Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
-rw-r--r--Documentation/git-check-ref-format.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/git-check-ref-format.txt b/Documentation/git-check-ref-format.txt
index fc02959..cbbedea 100644
--- a/Documentation/git-check-ref-format.txt
+++ b/Documentation/git-check-ref-format.txt
@@ -60,7 +60,7 @@ Git imposes the following rules on how references are named:
These rules make it easy for shell script based tools to parse
reference names, pathname expansion by the shell when a reference name is used
-unquoted (by mistake), and also avoids ambiguities in certain
+unquoted (by mistake), and also avoid ambiguities in certain
reference name expressions (see linkgit:gitrevisions[7]):
. A double-dot `..` is often used as in `ref1..ref2`, and in some