martin 00/01/07 08:38:10
Modified: htdocs/manual/misc perf-tuning.html htdocs/manual windows.html htdocs/manual/mod mod_imap.html mod_rewrite.html Log: it's -> its Revision Changes Path 1.18 +1 -1 apache-1.3/htdocs/manual/misc/perf-tuning.html Index: perf-tuning.html =================================================================== RCS file: /export/home/cvs/apache-1.3/htdocs/manual/misc/perf-tuning.html,v retrieving revision 1.17 retrieving revision 1.18 diff -u -r1.17 -r1.18 --- perf-tuning.html 1999/04/20 22:19:13 1.17 +++ perf-tuning.html 2000/01/07 16:38:01 1.18 @@ -17,7 +17,7 @@ <H3>Introduction</H3> <P>Apache is a general webserver, which is designed to be correct first, and -fast second. Even so, it's performance is quite satisfactory. Most +fast second. Even so, its performance is quite satisfactory. Most sites have less than 10Mbits of outgoing bandwidth, which Apache can fill using only a low end Pentium-based webserver. In practice sites with more bandwidth require more than one machine to fill the bandwidth 1.31 +2 -2 apache-1.3/htdocs/manual/windows.html Index: windows.html =================================================================== RCS file: /export/home/cvs/apache-1.3/htdocs/manual/windows.html,v retrieving revision 1.30 retrieving revision 1.31 diff -u -r1.30 -r1.31 --- windows.html 1999/07/22 17:50:59 1.30 +++ windows.html 2000/01/07 16:38:06 1.31 @@ -352,7 +352,7 @@ If you don't specify a configuration file name with -f or -n, Apache will use the file name compiled into the server, usually "conf/httpd.conf". Invoking Apache with the -V switch will display this value labeled as SERVER_CONFIG_FILE. -Apache will then determine it's ServerRoot by trying the following, in this order: +Apache will then determine its ServerRoot by trying the following, in this order: <UL> <LI>A ServerRoot directive via a -C switch. @@ -387,7 +387,7 @@ <P> If you did not do a binary install then Apache will in some scenarios complain that about the missing registry key. This -warning can be ignored if it otherwise was able to find it's +warning can be ignored if it otherwise was able to find its configuration files. <P> 1.14 +2 -2 apache-1.3/htdocs/manual/mod/mod_imap.html Index: mod_imap.html =================================================================== RCS file: /export/home/cvs/apache-1.3/htdocs/manual/mod/mod_imap.html,v retrieving revision 1.13 retrieving revision 1.14 diff -u -r1.13 -r1.14 --- mod_imap.html 1999/08/05 18:43:47 1.13 +++ mod_imap.html 2000/01/07 16:38:07 1.14 @@ -141,7 +141,7 @@ The ImapDefault directive sets the default <CODE>default</CODE> used in -the imagemap files. It's value is overridden by a <CODE>default</CODE> +the imagemap files. Its value is overridden by a <CODE>default</CODE> directive within the imagemap file. If not present, the <CODE>default</CODE> action is <CODE>nocontent</CODE>, which means that a <CODE>204 No Content</CODE> is sent to the client. In this @@ -173,7 +173,7 @@ 1.1 and later.<P> The ImapBase directive sets the default <CODE>base</CODE> used in -the imagemap files. It's value is overridden by a <CODE>base</CODE> +the imagemap files. Its value is overridden by a <CODE>base</CODE> directive within the imagemap file. If not present, the <CODE>base</CODE> defaults to <CODE>http://servername/</CODE>. 1.46 +1 -1 apache-1.3/htdocs/manual/mod/mod_rewrite.html Index: mod_rewrite.html =================================================================== RCS file: /export/home/cvs/apache-1.3/htdocs/manual/mod/mod_rewrite.html,v retrieving revision 1.45 retrieving revision 1.46 diff -u -r1.45 -r1.46 --- mod_rewrite.html 1999/10/27 09:14:32 1.45 +++ mod_rewrite.html 2000/01/07 16:38:08 1.46 @@ -87,7 +87,7 @@ <P> But all this functionality and flexibility has its drawback: complexity. So -don't expect to understand this module in it's whole in just one day. +don't expect to understand this module in its whole in just one day. <P> This module was invented and originally written in April 1996<BR>