From: Rich Bowen <rbowen@apache.org>
Date: Thu, 15 Mar 2012 11:22:14 +0000 (+0000)
Subject: Typo and link breakage patches for mod_rewrite docs. via Daniel Gruno
X-Git-Tag: 2.4.2~192
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=8ad236a4710a5afa6a504344c9a1ec180fe9a19c;p=apache

Typo and link breakage patches for mod_rewrite docs. via Daniel Gruno
(rumble at cord dk)


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

diff --git a/docs/manual/rewrite/flags.xml b/docs/manual/rewrite/flags.xml
index 16d69f1f5f..c2ae0a0df8 100644
--- a/docs/manual/rewrite/flags.xml
+++ b/docs/manual/rewrite/flags.xml
@@ -277,7 +277,7 @@ redirects.</p>
 <section id="flag_f"><title>F|forbidden</title>
 <p>Using the [F] flag causes the server to return a 403 Forbidden status
 code to the client. While the same behavior can be accomplished using
-the <directive module="mod_access">Deny</directive> directive, this
+the <directive module="mod_access_compat">Deny</directive> directive, this
 allows more flexibility in assigning a Forbidden status.</p>
 
 <p>The following rule will forbid <code>.exe</code> files from being
@@ -522,7 +522,7 @@ use of the [PT] flag causes the result of the <directive
 module="mod_rewrite">RewriteRule</directive> to be passed back through
 URL mapping, so that location-based mappings, such as <directive
 module="mod_alias">Alias</directive>, <directive
-module="core">Redirect</directive>, or <directive
+module="mod_alias">Redirect</directive>, or <directive
 module="mod_alias">ScriptAlias</directive>, for example, might have a
 chance to take effect.
 </p>
diff --git a/docs/manual/rewrite/proxy.xml b/docs/manual/rewrite/proxy.xml
index c7a8663e6a..41b2d56fef 100644
--- a/docs/manual/rewrite/proxy.xml
+++ b/docs/manual/rewrite/proxy.xml
@@ -94,7 +94,7 @@ ProxyPassReverse / http://old.example.com/
 
     <p>Consider using either <directive
     module="mod_proxy">ProxyPass</directive> or <directive
-    module="mod_rewrite">ProxyPassMatch</directive> whenever possible in
+    module="mod_proxy">ProxyPassMatch</directive> whenever possible in
     preference to mod_rewrite.</p>
     </dd>
   </dl>
diff --git a/docs/manual/rewrite/remapping.xml b/docs/manual/rewrite/remapping.xml
index 974fb1030e..a5db6e8ff3 100644
--- a/docs/manual/rewrite/remapping.xml
+++ b/docs/manual/rewrite/remapping.xml
@@ -249,7 +249,7 @@ RewriteRule ^(.*).html$ $1.php<br />
     &lt;Directory&gt; block or in a .htaccess file), so that the
     <code>-f</code> checks are looking at the correct directory path.
     You may need to set a <directive
-    module="mod_rewite">RewriteBase</directive> directive to specify the
+    module="mod_rewrite">RewriteBase</directive> directive to specify the
     directory base that you're working in.</p>
     </dd>
   </dl>
@@ -275,7 +275,7 @@ RewriteRule ^(.*).html$ $1.php<br />
         <dd>
 
 <p>The very best way to solve this doesn't involve mod_rewrite at all,
-but rather uses the <directive module="alias">Redirect</directive>
+but rather uses the <directive module="mod_alias">Redirect</directive>
 directive placed in a virtual host for the non-canonical
 hostname(s).</p>