Remove unnecessary <pre> tags in <example> blocks.

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

diff --git a/docs/manual/rewrite/proxy.xml b/docs/manual/rewrite/proxy.xml
index 8d94a5f95f04d67811e3fba4b8a79b7f1697e663..89c7676d08f9fad3f36fa5bb6969eb269e7e066e 100644 (file)
--- a/docs/manual/rewrite/proxy.xml
+++ b/docs/manual/rewrite/proxy.xml
@@ -65,24 +65,24 @@ A number of recipes are provided that describe common scenarios.</p>
       <p>To simply map a URL to another server, we use the [P] flag, as
       follows:</p>
 
-<example><pre>
-RewriteEngine  on
-RewriteBase    /products/
-RewriteRule    ^<strong>widget/</strong>(.*)$  <strong>http://product.example.com/widget/</strong>$1  [<strong>P</strong>]
+<example>
+RewriteEngine  on<br />
+RewriteBase    /products/<br />
+RewriteRule    ^<strong>widget/</strong>(.*)$  <strong>http://product.example.com/widget/</strong>$1  [<strong>P</strong>]<br />
 ProxyPassReverse /products/widget/ http://product.example.com/widget/
-</pre></example>
+</example>
 
    <p>In the second example, we proxy the request only if we can't find
    the resource locally. This can be very useful when you're migrating
    from one server to another, and you're not sure if all the content
    has been migrated yet.</p>
 
-<example><pre>
-RewriteCond %{REQUEST_FILENAME}       <strong>!-f</strong>
-RewriteCond %{REQUEST_FILENAME}       <strong>!-d</strong>
-RewriteRule ^/(.*) http://<strong>old</strong>.example.com$1 [<strong>P</strong>]
+<example>
+RewriteCond %{REQUEST_FILENAME}       <strong>!-f</strong><br />
+RewriteCond %{REQUEST_FILENAME}       <strong>!-d</strong><br />
+RewriteRule ^/(.*) http://<strong>old</strong>.example.com$1 [<strong>P</strong>]<br />
 ProxyPassReverse / http://old.example.com/
-</pre></example>
+</example>
     </dd>
 
     <dt>Discussion:</dt>

diff --git a/docs/manual/rewrite/remapping.xml b/docs/manual/rewrite/remapping.xml
index 423ef5d763e7a2f3ff452c6a6bd98c34d3a1f500..1a3b5411834a937003e0a504e68979e5571acb7c 100644 (file)
--- a/docs/manual/rewrite/remapping.xml
+++ b/docs/manual/rewrite/remapping.xml
@@ -154,7 +154,7 @@ RewriteRule   ^/docs/(.+)  http://new.example.com/docs/$1  [R,L]
 RedirectMatch ^/docs/(.*) http://new.example.com/docs/$1
 </example>
 
-<example><title>With Redirect</title><pre>
+<example><title>With Redirect</title>
 Redirect /docs/ http://new.example.com/docs/
 </example>
     </dd>

diff --git a/docs/manual/rewrite/rewritemap.xml b/docs/manual/rewrite/rewritemap.xml
index d8bd1a8bdcdeda88b40082cd1d55f2dc138e765f..ff26edee6df1ce013e249bb9671b8571871448e4 100644 (file)
--- a/docs/manual/rewrite/rewritemap.xml
+++ b/docs/manual/rewrite/rewritemap.xml
@@ -155,17 +155,15 @@ may be used, and give examples of each.</p>
     the following:</p>
 
     <example><title>Product to ID map</title>
-      <pre>
-##
-##  productmap.txt - Product to ID map file
-##
-
-television 993
-stereo     198
-fishingrod 043
-basketball 418
+##<br />
+##  productmap.txt - Product to ID map file<br />
+##<br />
+<br />
+television 993<br />
+stereo     198<br />
+fishingrod 043<br />
+basketball 418<br />
 telephone  328
-</pre>
     </example>
 
     <p>Thus, when <code>http://example.com/product/television</code> is
@@ -208,14 +206,12 @@ telephone  328
     else is sent to one of the 'dynamic' pool.</p>
 
     <example><title>Rewrite map file</title>
-      <pre>
-##
-##  map.txt -- rewriting map
-##
-
-static   www1|www2|www3|www4
+##<br />
+##  map.txt -- rewriting map<br />
+##<br />
+<br />
+static   www1|www2|www3|www4<br />
 dynamic  www5|www6
-</pre>
     </example>
 
     <example><title>Configuration directives</title>