Documentation/gitcli.txt: fix double quotes
Replace double quotes around literal examples with backticks Signed-off-by: Jason St. John <jstjohn@purdue.edu> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Jason St. John committed
Nov 19, 2013 at 20:34 UTC
0b7e4e0da4cf311d106fdc27e9eb46a73d0731c4
1 file changed
+5
-5
Documentation/gitcli.txt
+5
-5
@@ -79,12 +79,12 @@ scripting Git:
79
`git log -1 HEAD` but write `git log -1 HEAD --`; the former will not work
80
if you happen to have a file called `HEAD` in the work tree.
81
82
- * many commands allow a long option "--option" to be abbreviated
82
+ * many commands allow a long option `--option` to be abbreviated
83
only to their unique prefix (e.g. if there is no other option
84
- whose name begins with "opt", you may be able to spell "--opt" to
85
- invoke the "--option" flag), but you should fully spell them out
84
+ whose name begins with `opt`, you may be able to spell `--opt` to
85
+ invoke the `--option` flag), but you should fully spell them out
86
when writing your scripts; later versions of Git may introduce a
87
- new option whose name shares the same prefix, e.g. "--optimize",
87
+ new option whose name shares the same prefix, e.g. `--optimize`,
88
to make a short prefix that used to be unique no longer unique.
89
90
@@ -145,7 +145,7 @@ prefix of a long option as if it is fully spelled out, but use this
145
with a caution. For example, `git commit --amen` behaves as if you
146
typed `git commit --amend`, but that is true only until a later version
147
of Git introduces another option that shares the same prefix,
148
-e.g `git commit --amenity" option.
148
+e.g. `git commit --amenity` option.
149
150
151
Separating argument from the option