You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by el...@apache.org on 2016/12/31 09:27:49 UTC
svn commit: r1776711 - /httpd/httpd/branches/2.4.x/docs/manual/mod/core.xml
Author: elukey
Date: Sat Dec 31 09:27:48 2016
New Revision: 1776711
URL: http://svn.apache.org/viewvc?rev=1776711&view=rev
Log:
Fixed some doc typos detected by a user.
S�bastien Santoro (dereckson AT espace-win.org)
sent a bug report about one typo in core.xml
and I executed the aspell tool on the whole file.
Modified:
httpd/httpd/branches/2.4.x/docs/manual/mod/core.xml
Modified: httpd/httpd/branches/2.4.x/docs/manual/mod/core.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/branches/2.4.x/docs/manual/mod/core.xml?rev=1776711&r1=1776710&r2=1776711&view=diff
==============================================================================
--- httpd/httpd/branches/2.4.x/docs/manual/mod/core.xml (original)
+++ httpd/httpd/branches/2.4.x/docs/manual/mod/core.xml Sat Dec 31 09:27:48 2016
@@ -1254,7 +1254,7 @@ EnableSendfile On
(<a href="https://tools.ietf.org/html/rfc7230#section-3.2"
>RFC 7230 §3.2</a>), which are now applied by default or using
the <code>Strict</code> option. Due to legacy modules, applications or
- custom user-agents which must be deperecated the <code>Unsafe</code>
+ custom user-agents which must be deprecated the <code>Unsafe</code>
option has been added to revert to the legacy behaviors. These rules
are applied prior to request processing, so must be configured at the
global or default (first) matching virtual host section, by IP/port
@@ -1271,7 +1271,7 @@ EnableSendfile On
<a href="https://tools.ietf.org/html/rfc7230#section-3.5"
>RFC 7230 §3.5</a> "Message Parsing Robustness" identify the
risks of accepting obscure whitespace and request message formatting.
- As of the introduction of this directive, all grammer rules of the
+ As of the introduction of this directive, all grammar rules of the
specification are enforced in the default <code>Strict</code> operating
mode, and the strict whitespace suggested by section 3.5 is enforced
and cannot be relaxed.</p>
@@ -1304,7 +1304,7 @@ EnableSendfile On
<p><a href="https://tools.ietf.org/html/rfc2616#section-19.6"
>RFC 2616 §19.6</a> "Compatibility With Previous Versions" had
encouraged HTTP servers to support legacy HTTP/0.9 requests. RFC 7230
- superceeds this with "The expectation to support HTTP/0.9 requests has
+ supersedes this with "The expectation to support HTTP/0.9 requests has
been removed" and offers additional comments in
<a href="https://tools.ietf.org/html/rfc7230#appendix-A"
>RFC 7230 Appendix A</a>. The <code>Require1.0</code> option allows
@@ -4848,7 +4848,7 @@ as if 'QualifyRedirectURL ON' was config
<contextlist><context>server config</context></contextlist>
<usage>
-<p>HTTP Methods that are not conforming to the relvant RFCs are normally
+<p>HTTP Methods that are not conforming to the relevant RFCs are normally
rejected by request processing in Apache HTTPD. To avoid this, modules
can register non-standard HTTP methods they support.
The <directive>RegisterHttpMethod</directive> allows to register such