Minor tweaks to grammar and examples.

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

diff --git a/docs/manual/rewrite/rewrite_flags.html.en b/docs/manual/rewrite/rewrite_flags.html.en
index dda320cc87920d86dc79ebbc40bf2474c17f83d9..7972d7dfc21c8779df7b1d2fed254e553d1bc9e9 100644 (file)
--- a/docs/manual/rewrite/rewrite_flags.html.en
+++ b/docs/manual/rewrite/rewrite_flags.html.en
@@ -182,14 +182,14 @@ redirect - either internal or external - causing the request process to
 start over.</p>
 
 <p>It is therefore important, if you are using <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> directives in one of these
-context that you take explicit steps to avoid rules looping, and not
+contexts, that you take explicit steps to avoid rules looping, and not
 count solely on the [L] flag to terminate execution of a series of
 rules, as shown below.</p>
 
 <p>The example given here will rewrite any request to
 <code>index.php</code>, giving the original request as a query string
-argument to <code>index.php</code>, however, if the request is already
-for <code>index.php</code>, this rule will be skipped.</p>
+argument to <code>index.php</code>, however, the <code class="directive"><a href="../mod/mod_rewrite.html#rewritecond">RewriteCond</a></code> ensures that if the request 
+is already for <code>index.php</code>, the <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> will be skipped.</p>
 
 <div class="example"><p><code>
 RewriteCond %{REQUEST_URI} !index\.php<br />
@@ -214,7 +214,9 @@ RewriteRule (.*)A(.*) $1B$2 [N]
 </code></p></div>
 
 <p>You can think of this as a <code>while</code> loop: While this
-pattern still matches, perform this substitution.</p>
+pattern still matches (i.e., while the URI still contains an
+<code>A</code>), perform this substitution (i.e., replace the
+<code>A</code> with a <code>B</code>).</p>
 
 
 

diff --git a/docs/manual/rewrite/rewrite_flags.xml b/docs/manual/rewrite/rewrite_flags.xml
index 9befdede1be0690bbaa41c1d268af8c10bdd96b2..d7a63667c31ca692782357da3b6ecd906908f77e 100644 (file)
--- a/docs/manual/rewrite/rewrite_flags.xml
+++ b/docs/manual/rewrite/rewrite_flags.xml
@@ -192,14 +192,16 @@ start over.</p>
 
 <p>It is therefore important, if you are using <directive
 module="mod_rewrite">RewriteRule</directive> directives in one of these
-context that you take explicit steps to avoid rules looping, and not
+contexts, that you take explicit steps to avoid rules looping, and not
 count solely on the [L] flag to terminate execution of a series of
 rules, as shown below.</p>
 
 <p>The example given here will rewrite any request to
 <code>index.php</code>, giving the original request as a query string
-argument to <code>index.php</code>, however, if the request is already
-for <code>index.php</code>, this rule will be skipped.</p>
+argument to <code>index.php</code>, however, the <directive
+module="mod_rewrite">RewriteCond</directive> ensures that if the request 
+is already for <code>index.php</code>, the <directive
+module="mod_rewrite">RewriteRule</directive> will be skipped.</p>
 
 <example>
 RewriteCond %{REQUEST_URI} !index\.php<br />
@@ -224,7 +226,9 @@ RewriteRule (.*)A(.*) $1B$2 [N]
 </example>
 
 <p>You can think of this as a <code>while</code> loop: While this
-pattern still matches, perform this substitution.</p>
+pattern still matches (i.e., while the URI still contains an
+<code>A</code>), perform this substitution (i.e., replace the
+<code>A</code> with a <code>B</code>).</p>
 
 </section>