From: Daniel Gruno <humbedooh@apache.org>
Date: Thu, 9 Aug 2012 06:54:30 +0000 (+0000)
Subject: some more typo fixes
X-Git-Tag: 2.2.23~70
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=32361a2e8db4c61cbb703123fa4c953d0c1c6635;p=thirdparty%2Fapache%2Fhttpd.git

some more typo fixes

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x@1371050 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/docs/manual/mod/mod_proxy.xml b/docs/manual/mod/mod_proxy.xml
index 98f93f7478f..0577b693783 100644
--- a/docs/manual/mod/mod_proxy.xml
+++ b/docs/manual/mod/mod_proxy.xml
@@ -1535,7 +1535,7 @@ directly</description>
 <compatibility>Available in Apache 2.0.31 and later</compatibility>
 
 <usage>
-    <p>This directive allows a user to specifiy a timeout on proxy requests.
+    <p>This directive allows a user to specify a timeout on proxy requests.
     This is useful when you have a slow/buggy appserver which hangs, and you
     would rather just return a timeout and fail gracefully instead of waiting
     however long it takes the server to return.</p>
diff --git a/docs/manual/mod/mod_rewrite.xml b/docs/manual/mod/mod_rewrite.xml
index 130ad74b313..21864511da1 100644
--- a/docs/manual/mod/mod_rewrite.xml
+++ b/docs/manual/mod/mod_rewrite.xml
@@ -1121,7 +1121,7 @@ and automatically <em>added</em> after any relative (not starting with a
 slash or protocol name) substitution encounters the end of a rule set.  
 See the <directive module="mod_rewrite">RewriteBase</directive> 
 directive for more information regarding what prefix will be added back to 
-relative substitions.</li>
+relative substitutions.</li>
 
 <li> If you wish to match against the full URL-path in a per-directory 
 (htaccess) RewriteRule, use the <code>%{REQUEST_URI}</code> variable in
diff --git a/docs/manual/mod/mod_ssl.xml b/docs/manual/mod/mod_ssl.xml
index c0fc0b93a74..697ea883dc6 100644
--- a/docs/manual/mod/mod_ssl.xml
+++ b/docs/manual/mod/mod_ssl.xml
@@ -314,7 +314,7 @@ The following <em>source</em> variants are available:</p>
     consumes minimum CPU cycles under runtime and hence can be always used
     without drawbacks. The source used for seeding the PRNG contains of the
     current time, the current process id and (when applicable) a randomly
-    choosen 1KB extract of the inter-process scoreboard structure of Apache.
+    chosen 1KB extract of the inter-process scoreboard structure of Apache.
     The drawback is that this is not really a strong source and at startup
     time (where the scoreboard is still not available) this source just
     produces a few bytes of entropy. So you should always, at least for the
@@ -1062,7 +1062,7 @@ clients don't have a valid certificate. Notice that this directive can be
 used both in per-server and per-directory context. In per-server context it
 applies to the client authentication process used in the standard SSL
 handshake when a connection is established. In per-directory context it forces
-a SSL renegotation with the reconfigured client verification depth after the
+a SSL renegotiation with the reconfigured client verification depth after the
 HTTP request was read but before the HTTP response is sent.</p>
 <p>
 The depth actually is the maximum number of intermediate certificate issuers,