I found a few typo while I was translating
new_features_1_3.html

apache -> Apache
cpu -> CPU
and a real bug fix <Limit> -> &lt;Limit&gt;

Index: new_features_1_3.html
===================================================================
RCS file: /home/cvspublic/httpd-docs-1.3/htdocs/manual/new_features_1_3.html,v
retrieving revision 1.81
diff -u -r1.81 new_features_1_3.html
--- new_features_1_3.html       2000/01/18 19:32:42     1.81
+++ new_features_1_3.html       2000/11/17 10:57:54
@@ -98,7 +98,7 @@
      spawning children at faster rates.
  <LI>The code which dispatches modules was optimized to avoid
      repeatedly skipping over modules that don't implement certain
-     phases of the API.  (This skipping showed up as 5% of the cpu
+     phases of the API.  (This skipping showed up as 5% of the CPU
      time on profiles of a server with the default module mix.)
  <LI>Revamp of the Unix scoreboard management code so that less
      time is spent counting children in various states.  Previously
@@ -172,7 +172,7 @@
  
 <DT><A HREF="install.html#install"><STRONG>Default Apache directory 
     path changed to <CODE>/usr/local/apache/</CODE></STRONG></A><BR>
-<DD>The default directory for the apache ServerRoot changed from the
+<DD>The default directory for the Apache ServerRoot changed from the
     NCSA-compatible <CODE>/usr/local/etc/httpd/</CODE> to
     <CODE>/usr/local/apache/</CODE>.  This change covers only the
     default setting (and the documentation); it is of course possible
@@ -207,7 +207,7 @@
 <DD><A HREF="mod/core.html#limitexcept">&lt;LimitExcept&gt; and
     &lt;/LimitExcept&gt;</A> are used to enclose a group of access control
     directives which will then apply to any HTTP access method not listed in
-    the arguments; i.e., it is the opposite of a <Limit> section and can be
+    the arguments; i.e., it is the opposite of a &lt;Limit&gt; section and can 
be
     used to control both standard and nonstandard/unrecognized methods.
 </DL>
 
@@ -258,7 +258,7 @@
 <UL>
 <LI>Easier and safer authentification for ftp proxy logins:
     When no ftp user name and/or password is specified in the
-    URL, but the destination ftp server requires one, apache now
+    URL, but the destination ftp server requires one, Apache now
     returns a "[401] Authorization Required" status. This status code
     usually makes the client browser pop up an "Enter user name and
     password" dialog, and the request is retried with the given user
@@ -450,7 +450,7 @@
     as segfaults and kill -9).  The <CODE>child_init</CODE> and
     <CODE>child_exit</CODE> functions are passed a pool whose lifetime is
     the same as the lifetime of the child (modulo completely fatal
-    events in which apache has no hope of recovering).  In contrast,
+    events in which Apache has no hope of recovering).  In contrast,
     the module <CODE>init</CODE> function is passed a pool whose lifetime
     ends when the parent exits or restarts.
 
@@ -681,7 +681,7 @@
 <DT><STRONG>Support for Netscape style SHA1 encrypted passwords</STRONG><BR>
 <DD>To facilitate migration or integration of BasicAuth password
     schemes where the password is encrypted using SHA1 (as opposed
-    to apache's build in MD5 and/or the OS specific crypt(3) function
+    to Apache's built in MD5 and/or the OS specific crypt(3) function
     ) passwords prefixed with with <CODE>{SHA1}</CODE> are taken
     as Base64 encoded SHA1 passwords. More information and
     some utilities to convert Netscape ldap/ldif entries can be


-- 
Yoshiki Hayashi

Reply via email to