Wrap module mentions in <module>

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

diff --git a/docs/manual/rewrite/flags.xml b/docs/manual/rewrite/flags.xml
index 714711b2aa8df9cffc691b609b7e66a2df883c9e..09347d5a68f8848e15d3ed00ada60ec7cdaa520b 100644 (file)
--- a/docs/manual/rewrite/flags.xml
+++ b/docs/manual/rewrite/flags.xml
@@ -71,7 +71,7 @@ of how you might use them.</p>
 module="mod_rewrite">RewriteRule</directive> to escape non-alphanumeric
 characters before applying the transformation.</p>
 
-<p><code>mod_rewrite</code> has to unescape URLs before mapping them,
+<p><module>mod_rewrite</module> has to unescape URLs before mapping them,
 so backreferences are unescaped at the time they are applied.
 Using the B flag, non-alphanumeric characters in backreferences
 will be escaped. For example, consider the rule:</p>
@@ -257,7 +257,7 @@ RewriteRule   "^/index\.html"   "-" [CO=frontdoor:yes:.example.com:1440:/]
 </highlight>
 
 <p>In the example give, the rule doesn't rewrite the request.
-The "-" rewrite target tells mod_rewrite to pass the request
+The "-" rewrite target tells <module>mod_rewrite</module> to pass the request
 through unchanged. Instead, it sets a cookie
 called 'frontdoor' to a value of 'yes'. The cookie is valid for any host
 in the <code>.example.com</code> domain. It is set to expire in 1440
@@ -274,12 +274,12 @@ compares against is the concatenation of the current values of the URI
 and PATH_INFO.</p>
 
 <p>The current URI can be the initial URI as requested by the client, the
-result of a previous round of mod_rewrite processing, or the result of
-a prior rule in the current round of mod_rewrite processing.</p>
+result of a previous round of <module>mod_rewrite</module> processing, or the result of
+a prior rule in the current round of <module>mod_rewrite</module> processing.</p>
 
 <p>In contrast, the PATH_INFO that is appended to the URI before each
 rule reflects only the value of PATH_INFO before this round of
-mod_rewrite processing. As a consequence, if large portions
+<module>mod_rewrite</module> processing. As a consequence, if large portions
 of the URI are matched and copied into a substitution in multiple
 <directive>RewriteRule</directive> directives, without regard for
 which parts of the URI came from the current PATH_INFO, the final
@@ -288,8 +288,8 @@ URI may have multiple copies of PATH_INFO appended to it.</p>
 <p>Use this flag on any substitution where the PATH_INFO that resulted
 from the previous mapping of this request to the filesystem is not of
 interest.  This flag permanently forgets the PATH_INFO established
-before this round of mod_rewrite processing began. PATH_INFO will
-not be recalculated until the current round of mod_rewrite processing
+before this round of <module>mod_rewrite</module> processing began. PATH_INFO will
+not be recalculated until the current round of <module>mod_rewrite</module> processing
 completes.  Subsequent rules during this round of processing will see
 only the direct result of substitutions, without any PATH_INFO
 appended.</p>
@@ -865,11 +865,11 @@ invariably be a less efficient solution than the alternatives.</p>
 
 <p>
 If used in per-directory context, use only <code>-</code> (dash)
-as the substitution <em>for the entire round of mod_rewrite processing</em>,
+as the substitution <em>for the entire round of <module>mod_rewrite</module> processing</em>,
 otherwise the MIME-type set with this flag is lost due to an internal
-re-processing (including subsequent rounds of mod_rewrite processing).
+re-processing (including subsequent rounds of <module>mod_rewrite</module> processing).
 The <code>L</code> flag can be useful in this context to end the
-<em>current</em> round of mod_rewrite processing.</p>
+<em>current</em> round of <module>mod_rewrite</module> processing.</p>
 </section>
 
 <section id="flag_unsafe_allow_3f"><title>UnsafeAllow3F</title>