svn commit: r1933521 - httpd/httpd/branches/2.4.x/docs/manual/mod

[rb...@apache.org]

Author: rbowen
Date: Wed Apr 29 18:35:58 2026
New Revision: 1933521

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

Modified:
   httpd/httpd/branches/2.4.x/docs/manual/mod/mod_rewrite.xml

Modified: httpd/httpd/branches/2.4.x/docs/manual/mod/mod_rewrite.xml
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/mod/mod_rewrite.xml	Wed Apr 29 18:35:54 2026	(r1933520)
+++ httpd/httpd/branches/2.4.x/docs/manual/mod/mod_rewrite.xml	Wed Apr 29 18:35:58 2026	(r1933521)
@@ -776,7 +776,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>
 
@@ -1089,8 +1089,8 @@ RewriteRule  "^/$"                 "/hom
       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>
@@ -1107,7 +1107,7 @@ RewriteRule  "^/$"                 "/hom
       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