more PR60024 feedback re: consistent terminology.

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

diff --git a/docs/manual/mod/mod_rewrite.xml b/docs/manual/mod/mod_rewrite.xml
index 4bd90ba6a1e2af263f4c8ae3b110c9bce78bf8df..c1cbae7b454d83b631ea7f50fa9e95d76dc9ac87 100644 (file)
--- a/docs/manual/mod/mod_rewrite.xml
+++ b/docs/manual/mod/mod_rewrite.xml
@@ -1057,18 +1057,17 @@ RewriteRule  "^/$"                 "/homepage.std.html"     [L]
       URL after the hostname and port, and before the query string (e.g. "/app1/index.html").
       This is the (%-decoded) <a href="directive-dict.html#Syntax">URL-path</a>.</p></li>
 
-      <li><p>In <directive module="core">Directory</directive> and htaccess context,
+      <li><p>In per-directory context (<directive module="core">Directory</directive> and .htaccess),
       the <em>Pattern</em> is matched against only a partial path, for example a request
       of "/app1/index.html" may result in comparison against "app1/index.html" 
       or "index.html" depending on where the <directive>RewriteRule</directive> is 
       defined.</p>
 
-      <p>In this context, only the trailing portion of the currently mapped
-      filesystem is compared against. The directory path where the rule is defined
-      is stripped before comparison (up to and including a trailing slash). 
+      <p>The directory path where the rule is defined is stripped from the currently mapped
+      filesystem path before comparison (up to and including a trailing slash). 
       The net result of this per-directory prefix stripping is that rules in
-      this context only match against the portion of the currently mapped path 
-      "below" where they are defined.</p>
+      this context only match against the portion of the currently mapped filesystem path 
+      "below" where the rule is defined.</p>
 
       <p>Directives such as <directive
       >DocumentRoot</directive> and <directive>Alias</directive>, or even the