From 2127a1f94e19aa0649de86d210f43f6f5edbf4ca Mon Sep 17 00:00:00 2001
From: Vincent Bray
Date: Sun, 16 Mar 2008 23:08:00 +0000
Subject: [PATCH] One typo, one logic error.
Submitted by: Lucien Gentis
Reviewed by: noodl
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@637682 13f79535-47bb-0310-9956-ffa450edef68
---
docs/manual/rewrite/rewrite_intro.xml | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/manual/rewrite/rewrite_intro.xml b/docs/manual/rewrite/rewrite_intro.xml
index 1b5f7ded8a..f1454a008b 100644
--- a/docs/manual/rewrite/rewrite_intro.xml
+++ b/docs/manual/rewrite/rewrite_intro.xml
@@ -211,7 +211,7 @@ RewriteRule ^/product/(.*)/view$ /var/web/productdb/$1
was matched by the expression inside the parenthesis in
the Pattern. For example, a request
for http://example.com/product/r14df/view
will be mapped
-to the path /var/web/productdbr14df
.
+to the path /var/web/productdb/r14df
.
If there is more than one expression in parenthesis, they are
available in order in the
@@ -224,7 +224,7 @@ on.
Rewrite Flags
The behavior of a RewriteRule can be modified by the
-application of one more flags to the end of the rule. For example, the
+application of one or more flags to the end of the rule. For example, the
matching behavior of a rule can be made case-insensitive by the
application of the [NC]
flag:
@@ -305,7 +305,7 @@ sections or .htaccess
files at the expense of some additional complexity. This technique
is called per-directory rewrites.
-The main difference with per-directory rewrites is that the path
+
The main difference with per-server rewrites is that the path
prefix of the directory containing the .htaccess
file is
stripped before matching in
the RewriteRule. In addition, the RewriteBase should be used to assure the request is properly mapped.
--
2.40.0