summaryrefslogtreecommitdiff
path: root/docs/manual/rewrite
diff options
context:
space:
mode:
authorVincent Bray <noodl@apache.org>2008-04-03 22:57:36 +0000
committerVincent Bray <noodl@apache.org>2008-04-03 22:57:36 +0000
commit29954b8668d2a5e26189effa0d7113a035894469 (patch)
treece0ba86c9cceb8c5aa5ad9a9a465cd43073549f4 /docs/manual/rewrite
parenta0769626097732113f482358d0e08167a5c7f424 (diff)
downloadhttpd-29954b8668d2a5e26189effa0d7113a035894469.tar.gz
Typo fixes courtesy of the French translation crew
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@644549 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'docs/manual/rewrite')
-rw-r--r--docs/manual/rewrite/rewrite_flags.html.en6
-rw-r--r--docs/manual/rewrite/rewrite_flags.xml6
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 034c3b8804..dda320cc87 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 7ab1067e1a..9befdede1b 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>