Backport of r583991.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x@584015 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/logs.html.en b/docs/manual/logs.html.en
index 1b81db6946aec6e245744047d5846219c9599b22..68682ed544424c3d988401b57d1615ec8d71ffd0 100644 (file)
--- a/docs/manual/logs.html.en
+++ b/docs/manual/logs.html.en
@@ -74,8 +74,8 @@
     what went wrong and how to fix it.</p>
 
     <p>The error log is usually written to a file (typically
-    <code>error_log</code> on unix systems and
-    <code>error.log</code> on Windows and OS/2). On unix systems it
+    <code>error_log</code> on Unix systems and
+    <code>error.log</code> on Windows and OS/2). On Unix systems it
     is also possible to have the server send errors to
     <code>syslog</code> or <a href="#piped">pipe them to a
     program</a>.</p>
@@ -92,11 +92,11 @@
     </code></p></div>
 
     <p>The first item in the log entry is the date and time of the
-    message. The second entry lists the severity of the error being
+    message. The second item lists the severity of the error being
     reported. The <code class="directive"><a href="./mod/core.html#loglevel">LogLevel</a></code>
     directive is used to control the types of errors that are sent
     to the error log by restricting the severity level. The third
-    entry gives the IP address of the client that generated the
+    item gives the IP address of the client that generated the
     error. Beyond that is the message itself, which in this case
     indicates that the server has been configured to deny the
     client access. The server reports the file-system path (as
@@ -117,7 +117,7 @@
     file.</p>
 
     <p>During testing, it is often useful to continuously monitor
-    the error log for any problems. On unix systems, you can
+    the error log for any problems. On Unix systems, you can
     accomplish this using:</p>
 
     <div class="example"><p><code>

diff --git a/docs/manual/logs.xml b/docs/manual/logs.xml
index 70930e6f573889f64e109b1dcaa51307a0da32df..3f44d2c0ca1ec0c1e3117e47a39f3816d0fc02d5 100644 (file)
--- a/docs/manual/logs.xml
+++ b/docs/manual/logs.xml
@@ -72,8 +72,8 @@
     what went wrong and how to fix it.</p>
 
     <p>The error log is usually written to a file (typically
-    <code>error_log</code> on unix systems and
-    <code>error.log</code> on Windows and OS/2). On unix systems it
+    <code>error_log</code> on Unix systems and
+    <code>error.log</code> on Windows and OS/2). On Unix systems it
     is also possible to have the server send errors to
     <code>syslog</code> or <a href="#piped">pipe them to a
     program</a>.</p>
@@ -90,11 +90,11 @@
     </example>
 
     <p>The first item in the log entry is the date and time of the
-    message. The second entry lists the severity of the error being
+    message. The second item lists the severity of the error being
     reported. The <directive module="core">LogLevel</directive>
     directive is used to control the types of errors that are sent
     to the error log by restricting the severity level. The third
-    entry gives the IP address of the client that generated the
+    item gives the IP address of the client that generated the
     error. Beyond that is the message itself, which in this case
     indicates that the server has been configured to deny the
     client access. The server reports the file-system path (as
@@ -116,7 +116,7 @@
     file.</p>
 
     <p>During testing, it is often useful to continuously monitor
-    the error log for any problems. On unix systems, you can
+    the error log for any problems. On Unix systems, you can
     accomplish this using:</p>
 
     <example>