Merge branch 'nd/doc-check-ref-format-typo' into maint

* nd/doc-check-ref-format-typo:
git-check-ref-format.txt: typo, s/avoids/avoid/

diff --combined Documentation/git-check-ref-format.txt
index 9044dfaadae10047281dfdfd06a75e634e1309fa,cbbedea17149539b0c50581e26aab6b7b19f41af..91a3622ee4e270a11c699e310fb4d544e37845c9
--- 1/Documentation/git-check-ref-format.txt
--- 2/Documentation/git-check-ref-format.txt
+++ b/Documentation/git-check-ref-format.txt
@@@ -60,7 -60,7 +60,7 @@@ Git imposes the following rules on how 
  
  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
@@@ -94,8 -94,8 +94,8 @@@ OPTION
        Interpret <refname> as a reference name pattern for a refspec
        (as used with remote repositories).  If this option is
        enabled, <refname> is allowed to contain a single `*`
 -      in place of a one full pathname component (e.g.,
 -      `foo/*/bar` but not `foo/bar*`).
 +      in the refspec (e.g., `foo/bar*/baz` or `foo/bar*baz/`
 +      but not `foo/bar*/baz*`).
  
  --normalize::
        Normalize 'refname' by removing any leading slash (`/`)