xforms

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

diff --git a/docs/manual/rewrite/intro.html.en b/docs/manual/rewrite/intro.html.en
index b3edda267ba21069ae9c66990cd8e53c21513c45..3f31fef8d6eb2407bcfe6a4cef5cf671c013ad65 100644 (file)
--- a/docs/manual/rewrite/intro.html.en
+++ b/docs/manual/rewrite/intro.html.en
@@ -141,8 +141,17 @@ 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 
+      <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> or
+      the <em>TestString</em> parameter of a 
+      <code class="directive"><a href="../mod/mod_rewrite.html#rewritecond">RewriteCond</a></code>.</p>
+      <p>  Captures in the <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> patterns are (counterintuitively) available to 
+       all preceding 
+      <code class="directive"><a href="../mod/mod_rewrite.html#rewritecond">RewriteCond</a></code> directives,
+      because the <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code>
+      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