humbedooh at apache
Apr 29, 2012, 5:22 AM
Post #1 of 1
(28 views)
Permalink
|
|
svn commit: r1331903 - /httpd/httpd/trunk/docs/manual/mod/core.xml
|
|
Author: humbedooh
Date: Sun Apr 29 12:22:47 2012
New Revision: 1331903
URL: http://svn.apache.org/viewvc?rev=1331903&view=rev
Log:
Fix a plethora of typos in core
Some nitpicking on the indenting in some example configs
Modified:
httpd/httpd/trunk/docs/manual/mod/core.xml
Modified: httpd/httpd/trunk/docs/manual/mod/core.xml
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/core.xml?rev=1331903&r1=1331902&r2=1331903&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/mod/core.xml (original)
+++ httpd/httpd/trunk/docs/manual/mod/core.xml Sun Apr 29 12:22:47 2012
@@ -978,13 +978,13 @@ satisfied</description>
<highlight language="config">
<If "-R '10.1.0.0/16'">
-#...
+ #...
</If>
<ElseIf "-R '10.0.0.0/8'">
-#...
+ #...
</ElseIf>
<Else>
-#...
+ #...
</Else>
</highlight>
@@ -1239,7 +1239,7 @@ ErrorDocument 404 /cgi-bin/bad_urls.pl
href="http://support.microsoft.com/default.aspx?scid=kb;en-us;Q294807"
>Q294807</a>.</p>
- <p>Although most error messages can be overriden, there are certain
+ <p>Although most error messages can be overridden, there are certain
circumstances where the internal messages are used regardless of the
setting of <directive module="core">ErrorDocument</directive>. In
particular, if a malformed request is detected, normal request processing
@@ -1339,11 +1339,11 @@ ErrorLogFormat "[%t] [%l] [pid %P] %F: %
example, the Referer header is only present if the log message is
associated to a request and the log message happens at a time when the
Referer header has already been read from the client. If no output is
- produced, the default behavior is to delete everything from the preceeding
+ produced, the default behavior is to delete everything from the preceding
space character to the next space character. This means the log line is
implicitly divided into fields on non-whitespace to whitespace transitions.
If a format string item does not produce output, the whole field is
- ommitted. For example, if the remote address <code>%a</code> in the log
+ omitted. For example, if the remote address <code>%a</code> in the log
format <code>[%t] [%l] [%a] %M </code> is not available, the surrounding
brackets are not logged either. Space characters can be escaped with a
backslash to prevent them from delimiting a field. The combination '% '
@@ -1355,7 +1355,7 @@ ErrorLogFormat "[%t] [%l] [pid %P] %F: %
respective item does not produce any output. In once-per-connection/request
formats, it is also possible to use the <code>+</code> (plus) modifier. If an
item with the plus modifier does not produce any output, the whole line is
- ommitted.</p>
+ omitted.</p>
<p>A number as modifier can be used to assign a log severity level to a
format item. The item will only be logged if the severity of the log
@@ -1500,7 +1500,7 @@ ErrorLogFormat "[%{u}t] [%-m:%l] [pid %P
[Thu May 12 08:28:57.652118 2011] [core:error] [pid 8777:tid 4326490112] [client ::1:58619] File does not exist: /usr/local/apache2/htdocs/favicon.ico
</example>
- <p>Notice that, as discussed above, some fields are ommitted
+ <p>Notice that, as discussed above, some fields are omitted
entirely because they are not defined.</p>
<highlight language="config">
@@ -1773,7 +1773,7 @@ media type in the HTTP Content-Type head
</contextlist>
<usage>
- <p>When the server has been compiled with gprof profiling suppport,
+ <p>When the server has been compiled with gprof profiling support,
<directive>GprofDir</directive> causes <code>gmon.out</code> files to
be written to the specified directory when the process exits. If the
argument ends with a percent symbol ('%'), subdirectories are created
@@ -3694,7 +3694,7 @@ to name-virtual hosts</description>
</highlight>
<p>Name-based virtual hosts for the best-matching set of <directive
- type="section" module="core">virtualhost</directive>s are processsed
+ type="section" module="core">virtualhost</directive>s are processed
in the order they appear in the configuration. The first matching <directive
module="core">ServerName</directive> or <directive module="core"
>ServerAlias</directive> is used, with no different precedence for wildcards
|
