svn commit: r1371058 - in /httpd/httpd/trunk/docs/manual/mod: mod_cache.xml mod_proxy_ajp.xml

[hu...@apache.org]

Author: humbedooh
Date: Thu Aug  9 07:32:04 2012
New Revision: 1371058

URL: http://svn.apache.org/viewvc?rev=1371058&view=rev
Log:
typo fixes

Modified:
    httpd/httpd/trunk/docs/manual/mod/mod_cache.xml
    httpd/httpd/trunk/docs/manual/mod/mod_proxy_ajp.xml

Modified: httpd/httpd/trunk/docs/manual/mod/mod_cache.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_cache.xml?rev=1371058&r1=1371057&r2=1371058&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_cache.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_cache.xml Thu Aug  9 07:32:04 2012
@@ -178,7 +178,7 @@ LoadModule cache_module modules/mod_cach
   becomes stale, and the time the stale entity is fully refreshed. On a busy
   server, a significant number of requests might arrive during this time, and
   cause a <strong>thundering herd</strong> of requests to strike the backend
-  suddenly and unpredicably.</p>
+  suddenly and unpredictably.</p>
   <p>To keep the thundering herd at bay, the <directive>CacheLock</directive>
   directive can be used to define a directory in which locks are created for
   URLs <strong>in flight</strong>. The lock is used as a <strong>hint</strong>

Modified: httpd/httpd/trunk/docs/manual/mod/mod_proxy_ajp.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_proxy_ajp.xml?rev=1371058&r1=1371057&r2=1371058&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/mod_proxy_ajp.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_proxy_ajp.xml Thu Aug  9 07:32:04 2012
@@ -120,10 +120,10 @@ ProxyPassReverse /apps/foo http://www.ex
     the connection can be in one of the following states:</p>
     <ul>
     <li> Idle <br/> No request is being handled over this connection. </li>
-    <li> Assigned <br/> The connecton is handling a specific request.</li>
+    <li> Assigned <br/> The connection is handling a specific request.</li>
     </ul>
     <p>Once a connection is assigned to handle a particular request, the basic
-    request informaton (e.g. HTTP headers, etc) is sent over the connection in
+    request information (e.g. HTTP headers, etc) is sent over the connection in
     a highly condensed form (e.g. common strings are encoded as integers).
     Details of that format are below in Request Packet Structure. If there is a
     body to the request <code>(content-length > 0)</code>, that is sent in a
@@ -139,7 +139,7 @@ ProxyPassReverse /apps/foo http://www.ex
     been transferred yet.  This is necessary because the packets have a fixed
     maximum size and arbitrary amounts of data can be included the body of a
     request (for uploaded files, for example).  (Note: this is unrelated to
-    HTTP chunked tranfer).</li>
+    HTTP chunked transfer).</li>
     <li>END_RESPONSE <br/> Finish the request-handling cycle.</li>
     </ul>
     <p>Each message is accompanied by a differently formatted packet of data.
@@ -277,7 +277,7 @@ ProxyPassReverse /apps/foo http://www.ex
     <p>To ensure some basic security, the container will only actually do the
     <code>Shutdown</code> if the request comes from the same machine on which
     it's hosted.</p>
-    <p>The first <code>Data</code> packet is send immediatly after the
+    <p>The first <code>Data</code> packet is send immediately after the
     <code>Forward Request</code> by the web server.</p>
     <p>The servlet container can send the following types of messages to the
     webserver:</p>
@@ -578,7 +578,7 @@ AJP13_GET_BODY_CHUNK :=
   <section><title>Get Body Chunk</title>
     <p>The container asks for more data from the request (If the body was
     too large to fit in the first packet sent over or when the request is
-    chuncked). The server will send a body packet back with an amount of data
+    chunked). The server will send a body packet back with an amount of data
     which is the minimum of the <code>request_length</code>, the maximum send
     body size <code>(8186 (8 Kbytes - 6))</code>, and the number of bytes
     actually left to send from the request body.<br/>