Add a few '/' and remove an errant '>'.

Note that this changes a patch proposed for backport to 2.2 (PR34602 & r573831).

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

diff --git a/docs/manual/mod/mod_rewrite.xml b/docs/manual/mod/mod_rewrite.xml
index b7649afc417331d7ffed726af0caac9b14a235e8..7f06d7a8d702790ee9cb5972a283c81bb278f012 100644 (file)
--- a/docs/manual/mod/mod_rewrite.xml
+++ b/docs/manual/mod/mod_rewrite.xml
@@ -1267,11 +1267,11 @@ cannot use <code>$N</code> in the substitution string!
         Using the B flag, non-alphanumeric characters in backreferences
         will be escaped.  For example, consider the rule:</p>
         <pre><code> RewriteRule RewriteRule ^(.*)$   index.php?show=$1 </code></pre>
-        <p>This will map <code>/C++</code> to <code>index.php?show=C++</code>.
+        <p>This will map <code>/C++</code> to <code>index.php?show=/C++</code>.
         But it will also map <code>/C%2b%2b</code> to
-        <code>index.php?show=C++</code>, because the <code>%2b</code>
+        <code>index.php?show=/C++</code>, because the <code>%2b</code>
         has been unescaped.  With the B flag, it will instead map to
-        <code>index.php?show=>/C%2b%2b</code>.</p>
+        <code>index.php?show=/C%2b%2b</code>.</p>
         <p>This escaping is particularly necessary in a proxy situation,
         when the backend may break if presented with an unescaped URL.</p>
         </dd>