From: Eric Covener <covener@apache.org>
Date: Mon, 26 Jan 2015 16:00:29 +0000 (+0000)
Subject: Merge r1654831 from trunk:
X-Git-Tag: 2.4.13~472
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=0dcd21b132251de07f712d3b91a50374c23637dc;p=apache

Merge r1654831 from trunk:

comment feedback -- flow is confusing




git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1654833 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/docs/manual/rewrite/intro.xml b/docs/manual/rewrite/intro.xml
index 3b1ff57d05..798bd00e93 100644
--- a/docs/manual/rewrite/intro.xml
+++ b/docs/manual/rewrite/intro.xml
@@ -145,8 +145,18 @@ the expression.</p>
       <em>CondPattern</em>, back-references are internally created
       which can be used with the strings <code>$N</code> and
       <code>%N</code> (see below). These are available for creating
-      the strings <em>Substitution</em> and <em>TestString</em> as 
-      outlined in the following chapters. Figure 1 shows to which 
+      the <em>Substitution</em> parameter of a 
+      <directive module="mod_rewrite">RewriteRule</directive> or
+      the <em>TestString</em> parameter of a 
+      <directive module="mod_rewrite">RewriteCond</directive>.</p>
+      <p>  Captures in the <directive module="mod_rewrite"
+      >RewriteRule</directive> patterns are (counterintuitively) available to 
+       all preceding 
+      <directive module="mod_rewrite">RewriteCond</directive> directives,
+      because the <directive module="mod_rewrite">RewriteRule</directive>
+      expression is evaluated before the individual conditions.</p>
+
+      <p>Figure 1 shows to which 
       locations the back-references are transferred for expansion as 
       well as illustrating the flow of the RewriteRule, RewriteCond 
       matching. In the next chapters, we will be exploring how to use