From: Eric Covener <covener@apache.org>
Date: Fri, 29 Aug 2025 12:11:59 +0000 (+0000)
Subject: reorder, tweak wording
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=471036b5fe0c39e21c172b31c7ae529959578d29;p=thirdparty%2Fapache%2Fhttpd.git

reorder, tweak wording

help emphasize the moral of PR69698, that continued lines
win out over comments.



git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1928078 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/docs/manual/configuring.xml b/docs/manual/configuring.xml
index cfa52f361a..9e76f1658b 100644
--- a/docs/manual/configuring.xml
+++ b/docs/manual/configuring.xml
@@ -66,19 +66,24 @@ Server.</p>
     <p>httpd configuration files contain one directive per line.
     The backslash "\" may be used as the last character on a line
     to indicate that the directive continues onto the next line.
-    There must be no other characters or white space between the
-    backslash and the end of the line.</p>
+    To be interpreted as such a continuation, there must be no
+    other characters or white space between the backslash and the
+    end of the line. </p>
 
-    <p>Arguments to directives are separated by whitespace. If an
+    <p>Lines that begin with the hash character "#" are considered
+    comments, and are ignored. Comments may <strong>not</strong> be
+    included on the same line as a configuration directive, including
+    at the start of a line that has been continued as described in the
+    preceding pargraph.
+    </p>
+
+    <p> White space occurring before a directive is ignored, so
+    you may indent directives for clarity. Blank lines are also ignored.
+    Arguments to directives are separated by whitespace. If an
     argument contains spaces, you must enclose that argument in quotes.</p>
 
     <p>Directives in the configuration files are case-insensitive,
-    but arguments to directives are often case sensitive. Lines
-    that begin with the hash character "#" are considered
-    comments, and are ignored. Comments may <strong>not</strong> be
-    included on the same line as a configuration directive.
-    White space occurring before a directive is ignored, so
-    you may indent directives for clarity. Blank lines are also ignored.</p>
+    but arguments to directives are often case sensitive. </p>
 
     <p>The values of variables defined with the <directive
     module="core">Define</directive> or of shell environment variables can