doc: camelCase the config variables to improve readability
References to multi-word configuration variable names in our documentation must consistently use camelCase to highlight where the word boundaries are, even though these are treated case insensitively. Fix a few places that spell them in all lowercase, which makes them harder to read. Signed-off-by: Kaartic Sivaraam <kaarticsivaraam91196@gmail.com> Reviewed-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Kaartic Sivaraam committed
Sep 23, 2017 at 10:26 UTC
c3342b362e77ad22b751e00fee00f96ea6ff0884
2 files changed
+3
-3
Documentation/git-branch.txt
+2
-2
@@ -92,10 +92,10 @@ OPTIONS
92
all changes made to the branch ref, enabling use of date
93
based sha1 expressions such as "<branchname>@\{yesterday}".
94
Note that in non-bare repositories, reflogs are usually
95
- enabled by default by the `core.logallrefupdates` config option.
95
+ enabled by default by the `core.logAllRefUpdates` config option.
96
The negated form `--no-create-reflog` only overrides an earlier
97
`--create-reflog`, but currently does not negate the setting of
98
- `core.logallrefupdates`.
98
+ `core.logAllRefUpdates`.
99
100
-f::
101
--force::
Documentation/git-tag.txt
+1
-1
@@ -174,7 +174,7 @@ This option is only applicable when listing tags without annotation lines.
174
`core.logAllRefUpdates` in linkgit:git-config[1].
175
The negated form `--no-create-reflog` only overrides an earlier
176
`--create-reflog`, but currently does not negate the setting of
177
- `core.logallrefupdates`.
177
+ `core.logAllRefUpdates`.
178
179
<tagname>::
180
The name of the tag to create, delete, or describe.