Consistent use of per-directory, rather than .htaccess, where appropriate

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

diff --git a/docs/manual/rewrite/htaccess.xml b/docs/manual/rewrite/htaccess.xml
index 6d5d0b61c2f66d397b1dfe8258eb2a397328c4ff..bd71c0e0481662cbaf2ab85e28a5795a892e9991 100644 (file)
--- a/docs/manual/rewrite/htaccess.xml
+++ b/docs/manual/rewrite/htaccess.xml
@@ -23,7 +23,7 @@
 <manualpage metafile="htaccess.xml.meta">
   <parentdocument href="./">Rewrite</parentdocument>
 
-<title>mod_rewrite and .htaccess files</title>
+<title>Per-directory Rewrites</title>
 
 <summary>
 

diff --git a/docs/manual/rewrite/index.xml b/docs/manual/rewrite/index.xml
index e59a5e057d6c3f359af7bce7e96d3014cbcb9571..337f080efa5548d972ac23f53ca0f015546dce45 100644 (file)
--- a/docs/manual/rewrite/index.xml
+++ b/docs/manual/rewrite/index.xml
@@ -42,10 +42,11 @@
 RewriteCond basics, and how mod_rewrite fits into the request
 processing lifecycle.</dd>
 
-<dt><a href="htaccess.html">Per-directory Rewrites (.htaccess)</a></dt>
+<dt><a href="htaccess.html">Per-directory Rewrites</a></dt>
 <dd>The key differences between using rewrite rules in server
-configuration versus <code>.htaccess</code> files, including path
-stripping, RewriteBase, and the looping behavior of the [L] flag.</dd>
+configuration versus <glossary ref="perdirectory">per-directory</glossary> 
+context, including path stripping, RewriteBase, and the looping behavior 
+of the [L] flag.</dd>
 
 <dt><a href="flags.html">RewriteRule Flags</a></dt>
 <dd>A complete reference for all flags that can modify the behavior of