Skip to content

Commit b7ee226

Browse files
bebarinogitster
authored andcommitted
config.txt: clarify sentences in the configuration and syntax sections
Signed-off-by: Stephen Boyd <bebarino@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
1 parent 773002a commit b7ee226

1 file changed

Lines changed: 6 additions & 6 deletions

File tree

Documentation/config.txt

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -8,9 +8,9 @@ is used to store the information for that repository, and
88
fallback values for the `.git/config` file. The file `/etc/gitconfig`
99
can be used to store system-wide defaults.
1010

11-
They can be used by both the git plumbing
12-
and the porcelains. The variables are divided into sections, where
13-
in the fully qualified variable name the variable itself is the last
11+
The configuration variables are used by both the git plumbing
12+
and the porcelains. The variables are divided into sections, wherein
13+
the fully qualified variable name of the variable itself is the last
1414
dot-separated segment and the section name is everything before the last
1515
dot. The variable names are case-insensitive and only alphanumeric
1616
characters are allowed. Some variables may appear multiple times.
@@ -38,9 +38,9 @@ in the section header, like in the example below:
3838

3939
--------
4040

41-
Subsection names can contain any character except newline (doublequote
42-
`"` and backslash have to be escaped as `\"` and `\\`,
43-
respectively) and are case sensitive. Section headers cannot span multiple
41+
Subsection names are case sensitive and can contain any characters except
42+
newline (doublequote `"` and backslash have to be escaped as `\"` and `\\`,
43+
respectively). Section headers cannot span multiple
4444
lines. Variables may belong directly to a section or to a given subsection.
4545
You can have `[section]` if you have `[section "subsection"]`, but you
4646
don't need to.

0 commit comments

Comments
 (0)