Grammar/Style fixes.

Submitted by:	Chris Pepper <pepper@mail.reppep.com>

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@86850 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/docs/manual/misc/compat_notes.html b/docs/manual/misc/compat_notes.html
index 719ee93ea9a45f2db18d16bffbbb77d3343ba1f7..a8301b68e3000509e408792e0678ec7c46fd165d 100644 (file)
--- a/docs/manual/misc/compat_notes.html
+++ b/docs/manual/misc/compat_notes.html
@@ -22,7 +22,7 @@ httpd, there are a couple gotcha's to watch out for.  These are mostly
 due to the fact that the parser for config and access control files
 was rewritten from scratch, so certain liberties the earlier servers
 took may not be available here.  These are all easily fixable.  If you
-know of other non-fatal problems that belong here, <A
+know of other problems that belong here, <A
 HREF="http://www.apache.org/bug_report.html">let us know.</A>
 
 <P>Please also check the <A HREF="known_client_problems.html">known
@@ -43,7 +43,7 @@ client problems</A> page.
 <P>
 <LI>If you follow the NCSA guidelines for setting up access
     restrictions based on client domain, you may well have added
-    entries for, <CODE>AuthType, AuthName, AuthUserFile</CODE> or
+    entries for <CODE>AuthType, AuthName, AuthUserFile</CODE> or
     <CODE>AuthGroupFile</CODE>.  <STRONG>None</STRONG> of these are
     needed (or appropriate) for restricting access based on client
     domain.  When Apache sees <CODE>AuthType</CODE> it (reasonably)
@@ -57,7 +57,7 @@ client problems</A> page.
 <P>
 <LI><CODE>exec cgi=""</CODE> produces reasonable <STRONG>malformed
   header</STRONG> responses when used to invoke non-CGI scripts.<BR>
-  The NCSA code ignores the missing header. (bad idea)
+  The NCSA code ignores the missing header (bad idea).
   <BR>Solution: write CGI to the CGI spec and use
   <CODE>include&nbsp;virtual</CODE>, or use <CODE>exec cmd=""</CODE> instead.
 
@@ -90,7 +90,7 @@ client problems</A> page.
     booting unless an added <CODE>optional</CODE> keyword is included.
 
 <P>
-<LI>Apache does not implement <CODE>OnDeny</CODE> use
+<LI>Apache does not implement <CODE>OnDeny</CODE>; use
     <A HREF="../mod/core.html#errordocument"><CODE>ErrorDocument</CODE></A>
     instead.
 
@@ -115,7 +115,7 @@ client problems</A> page.
 <LI>Apache does not allow ServerRoot settings inside a VirtualHost
     container.  There is only one global ServerRoot in Apache; any desired
     changes in paths for virtual hosts need to be made with the explicit
-    directives, eg. DocumentRoot, TransferLog, <EM>etc.</EM>
+    directives, <em>e.g.</em>, DocumentRoot, TransferLog, <EM>etc.</EM>
 
 </OL>
 

diff --git a/docs/manual/misc/howto.html b/docs/manual/misc/howto.html
index 9ce92a41baf2d47c991a523434467216c714206c..57c9f2dfa81e7ca2a2b8dee959afd4c6ca4859f7 100644 (file)
--- a/docs/manual/misc/howto.html
+++ b/docs/manual/misc/howto.html
@@ -57,11 +57,11 @@ If that module is compiled in, the following lines
 RewriteRule /.* http://www.apache.org/ [R]
 </PRE></BLOCKQUOTE>
 
-This will send an HTTP 302 Redirect back to the client, and no matter
+will send an HTTP 302 Redirect back to the client, and no matter
 what they gave in the original URL, they'll be sent to
-"http://www.apache.org".
+"http://www.apache.org/".
 
-The second option is to set up a <CODE>ScriptAlias</CODE> pointing to
+<p>The second option is to set up a <CODE>ScriptAlias</CODE> pointing to
 a <STRONG>CGI script</STRONG> which outputs a 301 or 302 status and the
 location
 of the other server.</P>
@@ -89,7 +89,7 @@ print "Status: 302 Moved Temporarily\r\n" .
       "Location: http://www.some.where.else.com/\r\n" .
       "\r\n";
 
-</PRE></BLOCKQUOTE></P>
+</PRE></BLOCKQUOTE>
 
 <HR>
 
@@ -118,7 +118,6 @@ it to reopen the logfiles.</P>
 mv access_log access_log.old<BR>
 kill -1 `cat httpd.pid`
 </CODE></BLOCKQUOTE>
-</P>
 
 <P>Note: <CODE>httpd.pid</CODE> is a file containing the
 <STRONG>p</STRONG>rocess <STRONG>id</STRONG>
@@ -135,7 +134,7 @@ nightly or weekly basis.</P>
 <CODE>robots.txt</CODE> which you don't have, and never did have?</P>
 
 <P>These clients are called <STRONG>robots</STRONG> (also known as crawlers,
-spiders and other cute name) - special automated clients which
+spiders and other cute names) - special automated clients which
 wander around the web looking for interesting resources.</P>
 
 <P>Most robots are used to generate some kind of <EM>web index</EM> which
@@ -155,7 +154,7 @@ will want to stop.</P>
 
 <P>Another reason some webmasters want to block access to robots, is to
 stop them indexing dynamic information. Many search engines will use the
-data collected from your pages for months to come - not much use if your
+data collected from your pages for months to come - not much use if you're
 serving stock quotes, news, weather reports or anything else that will be
 stale by the time people find it in a search engine.</P>
 
@@ -194,7 +193,7 @@ to set the directive ProxyRemote differently. Here are my settings:
 </PRE>
 <P>
 Requests on port 80 of my proxy <SAMP>nicklas</SAMP> are forwarded to
-proxy<SAMP>.mayn.franken.de:8080</SAMP>, while requests on port 443 are
+<SAMP>proxy.mayn.franken.de:8080</SAMP>, while requests on port 443 are
 forwarded to <SAMP>proxy.mayn.franken.de:443</SAMP>.
 If the remote proxy is not set up to
 handle port 443, then the last directive can be left out. SSL requests