From 684a543709d53d555e860f6bc8f3e7e33c5bca05 Mon Sep 17 00:00:00 2001
From: Vincent Bray <noodl@apache.org>
Date: Thu, 3 Apr 2008 22:58:59 +0000
Subject: [PATCH] Typo fixes courtesy of the French translation crew

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x@644551 13f79535-47bb-0310-9956-ffa450edef68
---
 docs/manual/rewrite/rewrite_flags.html.en | 6 +++---
 docs/manual/rewrite/rewrite_flags.xml     | 6 +++---
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/manual/rewrite/rewrite_flags.html.en b/docs/manual/rewrite/rewrite_flags.html.en
index b39995102c9..7063cc57307 100644
--- a/docs/manual/rewrite/rewrite_flags.html.en
+++ b/docs/manual/rewrite/rewrite_flags.html.en
@@ -189,7 +189,7 @@ rules, as shown below.</p>
 <p>The example given here will rewrite any request to
 <code>index.php</code>, giving the original request as a query string
 argument to <code>index.php</code>, however, if the request is already
-for <code>index.php</code>, this rull will be skipped.</p>
+for <code>index.php</code>, this rule will be skipped.</p>
 
 <div class="example"><p><code>
 RewriteCond %{REQUEST_URI} !index\.php<br />
@@ -285,7 +285,7 @@ considered.</p>
 
 <p>
 The target (or substitution string) in a RewriteRule is assumed to be a
-file path, by default. The use of the [PT] flag causes it to be trated
+file path, by default. The use of the [PT] flag causes it to be treated
 as a URI instead. That is to say, the
 use of the [PT] flag causes the result of the <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> to be passed back through
 URL mapping, so that location-based mappings, such as <code class="directive"><a href="../mod/mod_alias.html#alias">Alias</a></code>, for example, might have a chance to take
@@ -391,7 +391,7 @@ sent. This has the same effect as the <code class="directive"><a href="../mod/mo
 source code as plain text, if requested in a particular way:</p>
 
 <div class="example"><p><code>
-# Serve .pl files as plan text
+# Serve .pl files as plain text
 RewriteRule \.pl$ - [T=text/plain]
 </code></p></div>
 
diff --git a/docs/manual/rewrite/rewrite_flags.xml b/docs/manual/rewrite/rewrite_flags.xml
index 7ab1067e1a2..9befdede1be 100644
--- a/docs/manual/rewrite/rewrite_flags.xml
+++ b/docs/manual/rewrite/rewrite_flags.xml
@@ -199,7 +199,7 @@ rules, as shown below.</p>
 <p>The example given here will rewrite any request to
 <code>index.php</code>, giving the original request as a query string
 argument to <code>index.php</code>, however, if the request is already
-for <code>index.php</code>, this rull will be skipped.</p>
+for <code>index.php</code>, this rule will be skipped.</p>
 
 <example>
 RewriteCond %{REQUEST_URI} !index\.php<br />
@@ -296,7 +296,7 @@ considered.</p>
 
 <p>
 The target (or substitution string) in a RewriteRule is assumed to be a
-file path, by default. The use of the [PT] flag causes it to be trated
+file path, by default. The use of the [PT] flag causes it to be treated
 as a URI instead. That is to say, the
 use of the [PT] flag causes the result of the <directive
 module="mod_rewrite">RewriteRule</directive> to be passed back through
@@ -408,7 +408,7 @@ module="mod_mime">AddType</directive> directive.</p>
 source code as plain text, if requested in a particular way:</p>
 
 <example>
-# Serve .pl files as plan text
+# Serve .pl files as plain text
 RewriteRule \.pl$ - [T=text/plain]
 </example>
 
-- 
2.47.2