From: Yoshiki Hayashi <yoshiki@apache.org>
Date: Wed, 31 Jul 2002 05:38:55 +0000 (+0000)
Subject: Make this file valid XML.
X-Git-Tag: 2.0.40~68
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=6f3b8547b2e1713b6654e0ad3158c0789678faad;p=apache

Make this file valid XML.

Submitted by:	Vincent de Lau <vincent@delau.nl>


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

diff --git a/docs/manual/mod/mod_rewrite.xml b/docs/manual/mod/mod_rewrite.xml
index 1b4bc5ffa3..f11e1b1fdc 100644
--- a/docs/manual/mod/mod_rewrite.xml
+++ b/docs/manual/mod/mod_rewrite.xml
@@ -175,11 +175,11 @@ URLs on the fly</description>
       directives). For historical reasons the conditions are given
       first, and so the control flow is a little bit long-winded. See
       Figure 1 for more details.</p>
-<section>
+<blockquote>
       <img src="../images/mod_rewrite_fig1.gif" border="1" width="428"
            height="385" alt="[Needs graphics capability to display]" />
       <p><strong>Figure 1:</strong>The control flow through the rewriting ruleset</p>
-</section>
+</blockquote>
       <p>As you can see, first the URL is matched against the
       <em>Pattern</em> of each rule. When it fails mod_rewrite
       immediately stops processing this rule and continues with the
@@ -226,11 +226,11 @@ URLs on the fly</description>
       Figure 2 shows to which locations the back-references are
       transfered for expansion.</p>
 
-<section>
+<blockquote>
       <img src="../images/mod_rewrite_fig2.gif" border="1" width="381"
            height="179" alt="[Needs graphics capability to display]" />
       <p><strong>Figure 2:</strong> The back-reference flow through a rule.</p>
-</section>
+</blockquote>
       <p>We know this was a crash course on mod_rewrite's internal
       processing. But you will benefit from this knowledge when
       reading the following documentation of the available