cvs commit: httpd-docs-1.3/htdocs/manual/mod mod_log_forensic.html.en

[pe...@apache.org]

pepper      2004/02/24 10:37:24

  Modified:    htdocs/manual/mod mod_log_forensic.html.en
  Log:
  	Various language nits picked.
  	Downcased a tag.
  	ID consistently uppercased.
  
  Revision  Changes    Path
  1.2       +14 -14    httpd-docs-1.3/htdocs/manual/mod/mod_log_forensic.html.en
  
  Index: mod_log_forensic.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-docs-1.3/htdocs/manual/mod/mod_log_forensic.html.en,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- mod_log_forensic.html.en	21 Feb 2004 23:36:42 -0000	1.1
  +++ mod_log_forensic.html.en	24 Feb 2004 18:37:24 -0000	1.2
  @@ -12,7 +12,7 @@
     vlink="#000080" alink="#FF0000">
       <!--#include virtual="header.html" -->
   
  -    <h1 align="CENTER">Module mod_log_forensic</h1>
  +    <h1 align="center">Module mod_log_forensic</h1>
   
       <p>This module provides for forensic logging of the requests made to the
       server</p>
  @@ -34,20 +34,20 @@
       <p>This module provides for forensic logging of client
       requests. Logging is done before and after processing a request, so the
       forensic log contains two log lines for each request.
  -    The forensic logger works very strict, which means:</p>
  +    The forensic logger is very strict, which means:</p>
   
       <ul>
       <li>The format is fixed. You cannot modify the logging format at
       runtime.</li>
  -    <li>If it cannot write its data, the particular child process
  -    exits immediately and possibly dumps core (depends on your
  +    <li>If it cannot write its data, the child process exits immediately
  +    and may dump core (depends on your
       <code><a href="core.html#coredumpdirectory">CoreDumpDirectory</a></code>
       configuration).</li>
       </ul>
   
  -    <p>In order to evaluate the log output there's a script
  -    <code>check_forensic</code>, which can be found in the support directory
  -    of the distribution.</p>
  +    <p>The <code>check_forensic</code> script, which can be found in the
  +    distribution's support directory, may be helpful in evaluating the
  +    forensic log output.</p>
   
       <p>See also: <a href="../logs.html">Apache Log Files</a>.</p>
   
  @@ -65,9 +65,9 @@
       where normal logging occurs.</p>
   
       <p>In order to identify each request, a unique request ID is assigned.
  -    This forensic id can be cross logged in the normal transfer log using the
  +    This forensic ID can be cross logged in the normal transfer log using the
       <code>%{forensic-id}n</code> format string. If you're using
  -    <code><a href="mod_unique_id.html">mod_unique_id</a></code> its generated
  +    <code><a href="mod_unique_id.html">mod_unique_id</a></code>, its generated
       ID will be used.</p>
   
       <p>The first line logs the forensic ID, the request line and all received
  @@ -89,7 +89,7 @@
         -yQtJf8CoAB4AAFNXBIEAAAAA
       </code></p>
   
  -    <p>The <code>check_forensic</code> script gets as its argument the name
  +    <p>The <code>check_forensic</code> script takes as its argument the name
       of the logfile. It looks for those <code>+</code>/<code>-</code> ID pairs
       and complains if a request was not completed.</p>
   
  @@ -119,11 +119,11 @@
       in Version 1.3.30 and above</p>
   
       <p>The <code>ForensicLog</code> directive is used to
  -    log requests to the server for a forensic analysis. Each log entry
  -    gets assigned unique id which can be associated with the request
  +    log requests to the server for forensic analysis. Each log entry
  +    is assigned unique ID which can be associated with the request
       using the normal <code><a href="mod_log_config.html#customlog">CustomLog</a></code>
  -    directive. <code>mod_log_forensic</code> leaves a note called
  -    <code>forensic-id</code> which can be added to the transfer log by
  +    directive. <code>mod_log_forensic</code> creates a token called
  +    <code>forensic-id</code>, which can be added to the transfer log
       using the <code>%{forensic-id}n</code> format string.</p>
   
       <p>The argument, which specifies the location to which