Documentation/config.txt: avoid unnecessary negation
Section names and variable names are both case-insensitive, but one is described as "not case sensitive". Use "case-insensitive" for both. Instead of saying "... have to be escaped" without telling what that escaping achieves, state it in a more positive way, i.e. "... can be included by escaping". Signed-off-by: Junio C Hamano <gitster@pobox.com>
Junio C Hamano committed
Mar 3, 2015 at 20:03 UTC
05c3e5c7719a4b25237d00a696877bdd47488678
1 file changed
+3
-3
Documentation/config.txt
+3
-3
@@ -25,7 +25,7 @@ blank lines are ignored.
25
26
The file consists of sections and variables. A section begins with
27
the name of the section in square brackets and continues until the next
28
-section begins. Section names are not case sensitive. Only alphanumeric
28
+section begins. Section names are case-insensitive. Only alphanumeric
29
characters, `-` and `.` are allowed in section names. Each variable
30
must belong to some section, which means that there must be a section
31
header before the first setting of a variable.
@@ -40,8 +40,8 @@ in the section header, like in the example below:
40
--------
41
42
Subsection names are case sensitive and can contain any characters except
43
-newline (doublequote `"` and backslash have to be escaped as `\"` and `\\`,
44
-respectively). Section headers cannot span multiple
43
+newline (doublequote `"` and backslash can be included by escaping them
44
+as `\"` and `\\`, respectively). Section headers cannot span multiple
45
lines. Variables may belong directly to a section or to a given subsection.
46
You can have `[section]` if you have `[section "subsection"]`, but you
47
don't need to.