Should never use <module> inside an existing <a> tag, as that leads to

double/nested <a> tags in the generated HTML.

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

diff --git a/docs/manual/rewrite/avoid.xml b/docs/manual/rewrite/avoid.xml
index 5ae7a6c379c8a78616886468b8fd6254bc191b4f..2dab02fefeb610d470efc030aa92db09cf74898e 100644 (file)
--- a/docs/manual/rewrite/avoid.xml
+++ b/docs/manual/rewrite/avoid.xml
@@ -156,7 +156,7 @@ server.</p>
 
 <section id="vhosts"><title>Virtual Hosting</title>
 <p>Although it is possible to handle <a href="vhosts.html">virtual hosts
-with <module>mod_rewrite</module></a>, it is seldom the right way. Creating individual
+with mod_rewrite</a>, it is seldom the right way. Creating individual
 <directive module="core" type="section">VirtualHost</directive> blocks is
 almost always the right way to go. In the
 event that you have an enormous number of virtual hosts, consider using

diff --git a/docs/manual/rewrite/vhosts.xml b/docs/manual/rewrite/vhosts.xml
index 41322a094c8487bb19ffcf0e1ca508280291d4c7..3c7d4a36fa2a4625cc74806c47946ba4fb6a9ca4 100644 (file)
--- a/docs/manual/rewrite/vhosts.xml
+++ b/docs/manual/rewrite/vhosts.xml
@@ -36,7 +36,7 @@ configured virtual hosts.</p>
 virtual hosts. You should first consider the <a
 href="../vhosts/mass.html">alternatives</a> before resorting to
 mod_rewrite. See also the "<a href="avoid.html#vhosts">how to avoid
-<module>mod_rewrite</module></a> document.</note>
+mod_rewrite</a> document.</note>
 
 </summary>
 <seealso><a href="../mod/mod_rewrite.html">Module documentation</a></seealso>