From 8b82c9bab94434e58b88cc1d5571fc5a7dc4fa22 Mon Sep 17 00:00:00 2001
From: Eric Covener <covener@apache.org>
Date: Sun, 1 Sep 2019 18:10:34 +0000
Subject: [PATCH] PR63715: s/can/came and add a caution about
 REDIRECT_-prefixed envvars

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1866243 13f79535-47bb-0310-9956-ffa450edef68
---
 docs/manual/rewrite/advanced.xml | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/docs/manual/rewrite/advanced.xml b/docs/manual/rewrite/advanced.xml
index 8abba8e109c..495522a1dce 100644
--- a/docs/manual/rewrite/advanced.xml
+++ b/docs/manual/rewrite/advanced.xml
@@ -318,10 +318,10 @@ RewriteRule   "^foo\.html$"             "foo.night.html"
     <dt>Description:</dt>
 
     <dd>
-      <p>At time, we want to maintain some kind of status when we
+      <p>At times, we want to maintain some kind of status when we
       perform a rewrite. For example, you want to make a note that
       you've done that rewrite, so that you can check later to see if a
-      request can via that rewrite. One way to do this is by setting an
+      request came via that rewrite. One way to do this is by setting an
       environment variable.</p>
     </dd>
 
@@ -344,7 +344,10 @@ RewriteCond "%{ENV:rewritten}"  =1
 
     <p>Note that environment variables do not survive an external
     redirect. You might consider using the [CO] flag to set a
-    cookie.</p>
+    cookie. For per-directory and htaccess rewrites, where the final
+    substitution is processed as an internal redirect, environment
+    variables from the previous round of rewriting are prefixed with
+    "REDIRECT_". </p>
 
     </dd>
   </dl>
-- 
2.47.3