</example>
<p>However, in many cases, when there is no actual pattern matching
-meeded, as in the example shown above, the <directive
+needed, as in the example shown above, the <directive
module="mod_proxy">ProxyPass</directive> directive is a better choice.
The example here could be rendered as:</p>
<section id="setenv"><title>Environment Variable Testing</title>
<p><module>mod_rewrite</module> 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
<directive module="core" type="section">If</directive>.</p>
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>
projects / apache / commitdiff