From 55f14c0351ad0650ce199838436837a1fa0d2b1e Mon Sep 17 00:00:00 2001
From: Eric Covener <covener@apache.org>
Date: Fri, 5 Nov 2010 15:56:09 +0000
Subject: [PATCH] fix typo pointed out by poirier offline.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1031647 13f79535-47bb-0310-9956-ffa450edef68
---
 docs/manual/mod/mod_proxy.html.en | 4 ++--
 docs/manual/mod/mod_proxy.xml     | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/manual/mod/mod_proxy.html.en b/docs/manual/mod/mod_proxy.html.en
index cf5d94009f..29f8f9f573 100644
--- a/docs/manual/mod/mod_proxy.html.en
+++ b/docs/manual/mod/mod_proxy.html.en
@@ -399,7 +399,7 @@
     <p>Under some circumstances, the server must spool request bodies
     to disk to satisfy the requested handling of request bodies.  For 
     example, this spooling will occur if the original body was sent with
-    chunked encoding (and and is large), but the administrator has
+    chunked encoding (and is large), but the administrator has
     asked for backend requests to be sent with Content-Length or as HTTP/1.0.
     This spooling can also occur if the request body already has a
     Content-Length header, but the server is configured to filter incoming
@@ -1672,4 +1672,4 @@ header for proxied requests</td></tr>
 </div><div id="footer">
 <p class="apache">Copyright 2010 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p>
 <p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div>
-</body></html>
\ No newline at end of file
+</body></html>
diff --git a/docs/manual/mod/mod_proxy.xml b/docs/manual/mod/mod_proxy.xml
index ba569933ff..fb849fcb1e 100644
--- a/docs/manual/mod/mod_proxy.xml
+++ b/docs/manual/mod/mod_proxy.xml
@@ -369,7 +369,7 @@
     <p>Under some circumstances, the server must spool request bodies
     to disk to satisfy the requested handling of request bodies.  For 
     example, this spooling will occur if the original body was sent with
-    chunked encoding (and and is large), but the administrator has
+    chunked encoding (and is large), but the administrator has
     asked for backend requests to be sent with Content-Length or as HTTP/1.0.
     This spooling can also occur if the request body already has a
     Content-Length header, but the server is configured to filter incoming
-- 
2.40.0