svn commit: r1869816 - in /httpd/httpd/trunk/docs/manual: install.xml sections.xml suexec.xml

[ja...@apache.org]

Author: jailletc36
Date: Thu Nov 14 21:29:15 2019
New Revision: 1869816

URL: http://svn.apache.org/viewvc?rev=1869816&view=rev
Log:
Fix some spelling errors
(see PR 63923)

in suexec.xml, remove a useless comment and slighly improve layout

Modified:
    httpd/httpd/trunk/docs/manual/install.xml
    httpd/httpd/trunk/docs/manual/sections.xml
    httpd/httpd/trunk/docs/manual/suexec.xml

Modified: httpd/httpd/trunk/docs/manual/install.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/install.xml?rev=1869816&r1=1869815&r2=1869816&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/install.xml (original)
+++ httpd/httpd/trunk/docs/manual/install.xml Thu Nov 14 21:29:15 2019
@@ -460,7 +460,7 @@ $ tar xvf httpd-<em>NN</em>.tar
 
     <p>A <a
     href="http://wiki.apache.org/httpd/DistrosDefaultLayout">description
-    of these third-party distrubutions</a> is maintained in the HTTP
+    of these third-party distributions</a> is maintained in the HTTP
     Server wiki, and should reflect the current state of these
     third-party distributions. However, you will need to familiarize
     yourself with your particular platform's package management and

Modified: httpd/httpd/trunk/docs/manual/sections.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/sections.xml?rev=1869816&r1=1869815&r2=1869816&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/sections.xml (original)
+++ httpd/httpd/trunk/docs/manual/sections.xml Thu Nov 14 21:29:15 2019
@@ -305,7 +305,7 @@ and modules like <module>mod_rewrite</mo
 
 <highlight language="config">
 &lt;DirectoryMatch "^/var/www/combined/(?&lt;SITENAME&gt;[^/]+)"&gt;
-    require ldap-group "cn=%{env:MATCH_SITENAME},ou=combined,o=Example"
+    Require ldap-group "cn=%{env:MATCH_SITENAME},ou=combined,o=Example"
 &lt;/DirectoryMatch&gt;
 </highlight>
 
@@ -567,7 +567,7 @@ are interpreted, it is important to unde
         <li><directive>Directory</directive> "/" matches and an initial configuration to set the <code>CustomHeaderName</code> header with the value <code>one</code> is created.</li>
         <li><directive>Directory</directive> "/example" matches, and since <module>mod_headers</module> specifies in its code to override in case of a merge, a new configuration is created to set the <code>CustomHeaderName</code> header with the value <code>two</code>.</li>
         <li><directive>FilesMatch</directive> ".*" matches and another merge opportunity arises, causing the <code>CustomHeaderName</code> header to be set with the value <code>three</code>.</li>
-        <li>Eventually during the next steps of the HTTP request processing <module>mod_headers</module> will be called and it will receive the configuration to set the <code>CustomHeaderName</code> header with the value <code>three</code>. <module>mod_headers</module> normally uses this configuration to perfom its job, namely setting the foo header. This does not mean that a module can't perform a more complex action like discarding directives because not needed or deprecated, etc..</li>
+        <li>Eventually during the next steps of the HTTP request processing <module>mod_headers</module> will be called and it will receive the configuration to set the <code>CustomHeaderName</code> header with the value <code>three</code>. <module>mod_headers</module> normally uses this configuration to perform its job, namely setting the foo header. This does not mean that a module can't perform a more complex action like discarding directives because not needed or deprecated, etc..</li>
     </ul>
 
     <p>This is true for .htaccess too since they have the same priority as <directive>Directory</directive> in the merge order. The important concept to understand is that configuration sections like  <directive>Directory</directive> and <directive>FilesMatch</directive> are not comparable to module specific directives like <directive module="mod_headers">Header</directive> or <directive module="mod_rewrite">RewriteRule</directive> because they operate on different levels.

Modified: httpd/httpd/trunk/docs/manual/suexec.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/suexec.xml?rev=1869816&r1=1869815&r2=1869816&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/suexec.xml (original)
+++ httpd/httpd/trunk/docs/manual/suexec.xml Thu Nov 14 21:29:15 2019
@@ -367,7 +367,7 @@
       root user.  If this option is used, the <code>suexec</code>
       binary will instead be installed with only the setuid/setgid
       "capability" bits set, which is the subset of full root
-      priviliges required for suexec operation.  Note that
+      privileges required for suexec operation.  Note that
       the <code>suexec</code> binary may not be able to write to a log
       file in this mode; it is recommended that the
       <code>--with-suexec-syslog --without-suexec-logfile</code>
@@ -578,17 +578,14 @@ Group webgroup
     Warnings &amp; Examples</title>
 
     <p><strong>NOTE!</strong> This section may not be
-    complete. For the latest revision of this section of the
-    documentation, see the <a
-    href="http://httpd.apache.org/docs/&httpd.docs;/suexec.html">Online
-    Documentation</a> version.</p>
+    complete.</p>
 
     <p>There are a few points of interest regarding
     the wrapper that can cause limitations on server setup. Please
     review these before submitting any "bugs" regarding suEXEC.</p>
 
+    <p><strong>suEXEC Points Of Interest</strong></p>
     <ul>
-      <li><strong>suEXEC Points Of Interest</strong></li>
 
       <li>
         Hierarchy limitations