xforms

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

diff --git a/docs/manual/rewrite/avoid.html.en b/docs/manual/rewrite/avoid.html.en
index bfe4b3a0b6dfcc98e2cf682c6945aa0f10eb2bd5..1fedff908ee792a1998dc47a54c3aa40002e5f1d 100644 (file)
--- a/docs/manual/rewrite/avoid.html.en
+++ b/docs/manual/rewrite/avoid.html.en
@@ -170,7 +170,7 @@ RewriteRule ^/?images(.*) http://imageserver.local/images$1 [P]
 </code></p></div>
 
 <p>However, in many cases, when there is no actual pattern matching
-meeded, as in the example shown above, the <code class="directive"><a href="../mod/mod_proxy.html#proxypass">ProxyPass</a></code> directive is a better choice.
+needed, as in the example shown above, the <code class="directive"><a href="../mod/mod_proxy.html#proxypass">ProxyPass</a></code> directive is a better choice.
 The example here could be rendered as:</p>
 
 <div class="example"><p><code>
@@ -196,7 +196,7 @@ accomplish.</p>
 <h2><a name="setenv" id="setenv">Environment Variable Testing</a></h2>
 
 <p><code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> is frequently used to take a particular
-action based on the presence or absense of a particular environment
+action based on the presence or absence of a particular environment
 variable or request header. This can be done more efficiently using the
 <code class="directive"><a href="../mod/core.html#if">&lt;If&gt;</a></code>.</p>
 

diff --git a/docs/manual/rewrite/index.html.en b/docs/manual/rewrite/index.html.en
index f826dcce3118b95f87ef2b996cd30ba9914d70e9..759c352e699b22036a4fd7a6bc4e6ae1a16e410f 100644 (file)
--- a/docs/manual/rewrite/index.html.en
+++ b/docs/manual/rewrite/index.html.en
@@ -51,7 +51,7 @@
       <p>Since mod_rewrite is so powerful, it can indeed be rather
       complex. This document supplements the <a href="../mod/mod_rewrite.html">reference documentation</a>, and
       attempts to allay some of that complexity, and provide highly
-      annoted examples of common scenarios that you may handle with
+      annotated examples of common scenarios that you may handle with
       mod_rewrite. But we also attempt to show you when you should not
       use mod_rewrite, and use other standard Apache features instead,
       thus avoiding this unnecessary complexity.</p>