Reformat a few lines a bit, to utilize the available horizontal space better.
There are no changes to the actual contents of the documentation.
Signed-off-by: Dragan Simic <dsimic@xxxxxxxxxxx>
---
Notes:
This patch, in a slightly less extensive form, previously belonged to
a small series. [1] After some discussion, [2] this patch was taken out
of the series, because the cleanups it introduces are rather unrelated
to the future purpose of the series. [3]
[1] https://lore.kernel.org/git/d50c0f22c41ec36b574e1ff67e68485d9a6f2a84.1710258538.git.dsimic@xxxxxxxxxxx/
[2] https://lore.kernel.org/git/f7fa6d9bc9835ad1139bced5ea2b20b3@xxxxxxxxxxx/T/#u
[3] https://lore.kernel.org/git/f7fa6d9bc9835ad1139bced5ea2b20b3@xxxxxxxxxxx/T/#mde1232c9e30b237e425fce9a0810d31e3a56ba2b
Documentation/config.txt | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/Documentation/config.txt b/Documentation/config.txt
index 782c2bab906c..450424ee830e 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -57,11 +57,11 @@ compared case sensitively. These subsection names follow the same
restrictions as section names.
All the other lines (and the remainder of the line after the section
-header) are recognized as setting variables, in the form
-'name = value' (or just 'name', which is a short-hand to say that
-the variable is the boolean "true").
-The variable names are case-insensitive, allow only alphanumeric characters
-and `-`, and must start with an alphabetic character.
+header) are recognized as setting variables, in the form 'name = value'
+(or just 'name', which is a short-hand to say that the variable is the
+boolean "true"). The variable names are case-insensitive, allow only
+alphanumeric characters and `-`, and must start with an alphabetic
+character.
A line that defines a value can be continued to the next line by
ending it with a `\`; the backslash and the end-of-line are
@@ -95,10 +95,10 @@ to be included. The variable takes a pathname as its value, and is
subject to tilde expansion. These variables can be given multiple times.
The contents of the included file are inserted immediately, as if they
-had been found at the location of the include directive. If the value of the
-variable is a relative path, the path is considered to
-be relative to the configuration file in which the include directive
-was found. See below for examples.
+had been found at the location of the include directive. If the value of
+the variable is a relative path, the path is considered to be relative to
+the configuration file in which the include directive was found. See
+below for examples.
Conditional includes
~~~~~~~~~~~~~~~~~~~~
