</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>
<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"><If></a></code>.</p>
<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>