@@ -66,19 +66,24 @@ Server.</p>
6666 <p >httpd configuration files contain one directive per line.
6767 The backslash "\" may be used as the last character on a line
6868 to indicate that the directive continues onto the next line.
69- There must be no other characters or white space between the
70- backslash and the end of the line.</p >
69+ To be interpreted as such a continuation, there must be no
70+ other characters or white space between the backslash and the
71+ end of the line. </p >
7172
72- <p >Arguments to directives are separated by whitespace. If an
73+ <p >Lines that begin with the hash character "#" are considered
74+ comments, and are ignored. Comments may <strong >not</strong > be
75+ included on the same line as a configuration directive, including
76+ at the start of a line that has been continued as described in the
77+ preceding pargraph.
78+ </p >
79+
80+ <p > White space occurring before a directive is ignored, so
81+ you may indent directives for clarity. Blank lines are also ignored.
82+ Arguments to directives are separated by whitespace. If an
7383 argument contains spaces, you must enclose that argument in quotes.</p >
7484
7585 <p >Directives in the configuration files are case-insensitive,
76- but arguments to directives are often case sensitive. Lines
77- that begin with the hash character "#" are considered
78- comments, and are ignored. Comments may <strong >not</strong > be
79- included on the same line as a configuration directive.
80- White space occurring before a directive is ignored, so
81- you may indent directives for clarity. Blank lines are also ignored.</p >
86+ but arguments to directives are often case sensitive. </p >
8287
8388 <p >The values of variables defined with the <directive
8489 module =" core" >Define</directive > or of shell environment variables can
0 commit comments