Hi to all,
Here are 2 patches for file manual/rewrite/rewrite_intro.xml, one for
each branch 2.2.x and trunk.
Please verify modifications made by patches, I'm 90% sure those are typos.
Lucien
Index: docs/manual/rewrite/rewrite_intro.xml
===================================================================
--- docs/manual/rewrite/rewrite_intro.xml (revision 637581)
+++ docs/manual/rewrite/rewrite_intro.xml (working copy)
@@ -211,7 +211,7 @@
was matched by the expression inside the parenthesis in
the <var>Pattern</var>. For example, a request
for <code>http://example.com/product/r14df/view</code> will be mapped
-to the path <code>/var/web/productdbr14df</code>.</p>
+to the path <code>/var/web/productdb/r14df</code>.</p>
<p>If there is more than one expression in parenthesis, they are
available in order in the
@@ -224,7 +224,7 @@
<section id="flags"><title>Rewrite Flags</title>
<p>The behavior of a <directive
module="mod_rewrite">RewriteRule</directive> can be modified by the
-application of one more flags to the end of the rule. For example, the
+application of one or more flags to the end of the rule. For example, the
matching behavior of a rule can be made case-insensitive by the
application of the <code>[NC]</code> flag:
</p>
@@ -305,7 +305,7 @@
files</a> at the expense of some additional complexity. This technique
is called per-directory rewrites.</p>
-<p>The main difference with per-directory rewrites is that the path
+<p>The main difference with per-server rewrites is that the path
prefix of the directory containing the <code>.htaccess</code> file is
stripped before matching in
the <directive module="mod_rewrite">RewriteRule</directive>. In addition, the <directive module="mod_rewrite">RewriteBase</directive> should be used to assure the request is properly mapped.</p>
Index: manual/rewrite/rewrite_intro.xml
===================================================================
--- manual/rewrite/rewrite_intro.xml (revision 637581)
+++ manual/rewrite/rewrite_intro.xml (working copy)
@@ -211,7 +211,7 @@
was matched by the expression inside the parenthesis in
the <var>Pattern</var>. For example, a request
for <code>http://example.com/product/r14df/view</code> will be mapped
-to the path <code>/var/web/productdbr14df</code>.</p>
+to the path <code>/var/web/productdb/r14df</code>.</p>
<p>If there is more than one expression in parenthesis, they are
available in order in the
@@ -224,7 +224,7 @@
<section id="flags"><title>Rewrite Flags</title>
<p>The behavior of a <directive
module="mod_rewrite">RewriteRule</directive> can be modified by the
-application of one more flags to the end of the rule. For example, the
+application of one or more flags to the end of the rule. For example, the
matching behavior of a rule can be made case-insensitive by the
application of the <code>[NC]</code> flag:
</p>
@@ -305,7 +305,7 @@
files</a> at the expense of some additional complexity. This technique
is called per-directory rewrites.</p>
-<p>The main difference with per-directory rewrites is that the path
+<p>The main difference with per-server rewrites is that the path
prefix of the directory containing the <code>.htaccess</code> file is
stripped before matching in
the <directive module="mod_rewrite">RewriteRule</directive>. In addition, the <directive module="mod_rewrite">RewriteBase</directive> should be used to assure the request is properly mapped.</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
