httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From lgen...@apache.org
Subject svn commit: r1053663 - in /httpd/httpd/branches/2.2.x/docs/manual/mod: mod_headers.xml mpm_common.xml
Date Wed, 29 Dec 2010 16:17:14 GMT
Author: lgentis
Date: Wed Dec 29 16:17:13 2010
New Revision: 1053663

URL: http://svn.apache.org/viewvc?rev=1053663&view=rev
Log:
Typos.

Modified:
    httpd/httpd/branches/2.2.x/docs/manual/mod/mod_headers.xml
    httpd/httpd/branches/2.2.x/docs/manual/mod/mpm_common.xml

Modified: httpd/httpd/branches/2.2.x/docs/manual/mod/mod_headers.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/docs/manual/mod/mod_headers.xml?rev=1053663&r1=1053662&r2=1053663&view=diff
==============================================================================
--- httpd/httpd/branches/2.2.x/docs/manual/mod/mod_headers.xml (original)
+++ httpd/httpd/branches/2.2.x/docs/manual/mod/mod_headers.xml Wed Dec 29 16:17:13 2010
@@ -308,7 +308,7 @@ headers</description>
     will have to read on for further complications.</p>
 
     <p> The default value of <code>onsuccess</code> may need to be changed
to 
-    <code>always</code> under the circumstances similar to those listed below
+    <code>always</code> under the circumstances similar to those listed below.
     Note also that repeating this directive with both conditions makes sense in
     some scenarios because <code>always</code> is not a superset of 
     <code>onsuccess</code> with respect to existing headers:</p>

Modified: httpd/httpd/branches/2.2.x/docs/manual/mod/mpm_common.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.2.x/docs/manual/mod/mpm_common.xml?rev=1053663&r1=1053662&r2=1053663&view=diff
==============================================================================
--- httpd/httpd/branches/2.2.x/docs/manual/mod/mpm_common.xml (original)
+++ httpd/httpd/branches/2.2.x/docs/manual/mod/mpm_common.xml Wed Dec 29 16:17:13 2010
@@ -905,7 +905,7 @@ client connections</description> 
       of adjustment should only be made in a test environment which allows
       the full set of web server processing can be exercised, as there
       may be infrequent requests which require more stack to process.
-      The minumum required stack size strongly depends on the modules
+      The minimum required stack size strongly depends on the modules
       used, but any change in the web server configuration can invalidate
       the current <directive>ThreadStackSize</directive> setting.</li>
     </ul>



Mime
View raw message