Wrap module names in <module>

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1933067 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/rewrite/advanced.xml b/docs/manual/rewrite/advanced.xml
index e83bc23ff9d96d30f329b865a8801e9b35476acf..87f8710c5a43b07ddeee59f28603bea10df30fc4 100644 (file)
--- a/docs/manual/rewrite/advanced.xml
+++ b/docs/manual/rewrite/advanced.xml
@@ -29,7 +29,7 @@
 
 <p>This document supplements the <module>mod_rewrite</module>
 <a href="../mod/mod_rewrite.html">reference documentation</a>. It provides
-a few advanced techniques using mod_rewrite.</p>
+a few advanced techniques using <module>mod_rewrite</module>.</p>
 
 <!--
 I question whether anything remailing in this document qualifies as
@@ -165,7 +165,7 @@ RewriteRule "^(.+)\.html$"     "/regenerate_page.cgi"   [PT,L]
 
     <dd>
       <p>We wish to randomly distribute load across several servers
-      using mod_rewrite.</p>
+      using <module>mod_rewrite</module>.</p>
     </dd>
 
     <dt>Solution:</dt>
@@ -198,7 +198,7 @@ others, add it more times to the list.</p>
    <dd>
 <p>Apache comes with a load-balancing module -
 <module>mod_proxy_balancer</module> - which is far more flexible and
-featureful than anything you can cobble together using mod_rewrite.</p>
+featureful than anything you can cobble together using <module>mod_rewrite</module>.</p>
    </dd>
   </dl>
 
@@ -245,7 +245,7 @@ RewriteRule   "^/~(<strong>([a-z])</strong>[a-z0-9]+)(.*)"  "/home/<strong>$2</s
 
     <dd>
     <p>By default, redirecting to an HTML anchor doesn't work,
-    because mod_rewrite escapes the <code>#</code> character,
+    because <module>mod_rewrite</module> escapes the <code>#</code> character,
     turning it into <code>%23</code>. This, in turn, breaks the
     redirection.</p>
     </dd>
@@ -260,7 +260,7 @@ RewriteRule   "^/~(<strong>([a-z])</strong>[a-z0-9]+)(.*)"  "/home/<strong>$2</s
 
     <dt>Discussion:</dt>
     <dd>This technique will of course also work with other
-    special characters that mod_rewrite, by default, URL-encodes.</dd>
+    special characters that <module>mod_rewrite</module>, by default, URL-encodes.</dd>
   </dl>
 
 </section>
@@ -273,7 +273,7 @@ RewriteRule   "^/~(<strong>([a-z])</strong>[a-z0-9]+)(.*)"  "/home/<strong>$2</s
     <dt>Description:</dt>
 
     <dd>
-      <p>We wish to use mod_rewrite to serve different content based on
+      <p>We wish to use <module>mod_rewrite</module> to serve different content based on
       the time of day.</p>
     </dd>
 

diff --git a/docs/manual/rewrite/htaccess.xml b/docs/manual/rewrite/htaccess.xml
index 1160f31aa85c9a11e9462d5d89ea93d8dd9a799c..66e5ce32afcc8ff6b9a3bd5a6b39f6c5aaa79a43 100644 (file)
--- a/docs/manual/rewrite/htaccess.xml
+++ b/docs/manual/rewrite/htaccess.xml
@@ -29,7 +29,7 @@
 
 <p>This document supplements the <module>mod_rewrite</module>
 <a href="../mod/mod_rewrite.html">reference documentation</a>. It describes
-the way that the rules change when you use mod_rewrite in .htaccess files,
+the way that the rules change when you use <module>mod_rewrite</module> in .htaccess files,
 and how to deal with these changes.</p>
 
 </summary>

diff --git a/docs/manual/rewrite/proxy.xml b/docs/manual/rewrite/proxy.xml
index 8a255e891dbb6a231e9ad8e80de936780daa1989..7d643e65fd03e73f4c13bf3be75a05f4c15e1bab 100644 (file)
--- a/docs/manual/rewrite/proxy.xml
+++ b/docs/manual/rewrite/proxy.xml
@@ -52,8 +52,8 @@ A number of recipes are provided that describe common scenarios.</p>
 
     <dd>
     <p>
-    mod_rewrite provides the [P] flag, which allows URLs to be passed,
-    via mod_proxy, to another server. Two examples are given here. In
+    <module>mod_rewrite</module> provides the [P] flag, which allows URLs to be passed,
+    via <module>mod_proxy</module>, to another server. Two examples are given here. In
     one example, a URL is passed directly to another server, and served
     as though it were a local URL. In the other example, we proxy
     missing content to a back-end server.</p>
@@ -95,7 +95,7 @@ ProxyPassReverse "/" "http://old.example.com/"
     <p>Consider using either <directive
     module="mod_proxy">ProxyPass</directive> or <directive
     module="mod_proxy">ProxyPassMatch</directive> whenever possible in
-    preference to mod_rewrite.</p>
+    preference to <module>mod_rewrite</module>.</p>
     </dd>
   </dl>