Skip to content

Commit 0b7e4e0

Browse files
jrstjohngitster
authored andcommitted
Documentation/gitcli.txt: fix double quotes
Replace double quotes around literal examples with backticks Signed-off-by: Jason St. John <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent becb433 commit 0b7e4e0

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

Documentation/gitcli.txt

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -79,12 +79,12 @@ scripting Git:
7979
`git log -1 HEAD` but write `git log -1 HEAD --`; the former will not work
8080
if you happen to have a file called `HEAD` in the work tree.
8181

82-
* many commands allow a long option "--option" to be abbreviated
82+
* many commands allow a long option `--option` to be abbreviated
8383
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
8686
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`,
8888
to make a short prefix that used to be unique no longer unique.
8989

9090

@@ -145,7 +145,7 @@ prefix of a long option as if it is fully spelled out, but use this
145145
with a caution. For example, `git commit --amen` behaves as if you
146146
typed `git commit --amend`, but that is true only until a later version
147147
of Git introduces another option that shares the same prefix,
148-
e.g `git commit --amenity" option.
148+
e.g. `git commit --amenity` option.
149149

150150

151151
Separating argument from the option

0 commit comments

Comments
 (0)