From: Rich Bowen <rbowen@apache.org>
Date: Wed, 29 Apr 2026 18:35:54 +0000 (+0000)
Subject: mod_rewrite: Replace 'perl compatible regular expression' with glossary-linked 'regul... 
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=fc810a9885e5afd95af38502f67000e6418292f7;p=thirdparty%2Fapache%2Fhttpd.git

mod_rewrite: Replace 'perl compatible regular expression' with glossary-linked 'regular expression' (Bug 60377)

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

diff --git a/docs/manual/mod/mod_rewrite.xml b/docs/manual/mod/mod_rewrite.xml
index e51fa173e6..327ffa7f15 100644
--- a/docs/manual/mod/mod_rewrite.xml
+++ b/docs/manual/mod/mod_rewrite.xml
@@ -783,7 +783,7 @@ AliasMatch "^/myapp" "/opt/myapp-1.2.3"
       <em>CondPattern</em>.</p>
 
       <p><em>CondPattern</em> is usually a
-      <em>perl compatible regular expression</em>, but there is
+      <glossary ref="regex">regular expression</glossary>, but there is
       additional syntax available to perform other useful tests against
       the <em>Teststring</em>:</p>
 
@@ -1096,8 +1096,8 @@ RewriteRule  "^/$"                 "/homepage.std.html"     [L]
       in which they will be applied at run-time.</p>
 
       <p><a id="patterns" name="patterns"><em>Pattern</em></a> is
-      a perl compatible <a id="regexp" name="regexp">regular
-      expression</a>.  What this pattern is compared against varies depending
+      a <a id="regexp" name="regexp"><glossary ref="regex">regular
+      expression</glossary></a>.  What this pattern is compared against varies depending
       on where the <directive>RewriteRule</directive> directive is defined. </p>
 
 <note><title><a id="what_is_matched" name="what_is_matched">What is matched?</a></title>
@@ -1114,7 +1114,7 @@ RewriteRule  "^/$"                 "/homepage.std.html"     [L]
       or "index.html" depending on where the <directive>RewriteRule</directive> is 
       defined.</p>
 
-      <p>The directory path where the rule is defined is stripped from the currently mapped
+      <p>The directory-path for which 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 filesystem path