</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>
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>
hostname but before any question mark indicating the beginning of a query
string) or, in per-directory context, against the request's path relative
to the directory for which the rule is defined. Once a substitution has
-occured, the rules that follow are matched against the substituted
+occurred, the rules that follow are matched against the substituted
value.
</p>
projects / thirdparty / apache / httpd.git / commitdiff
