Author: mturk
Date: Wed Oct 8 04:05:32 2008
New Revision: 702807
URL: http://svn.apache.org/viewvc?rev=702807&view=rev
Log:
Spell checking ...
Modified:
tomcat/connectors/trunk/jk/xdocs/webserver_howto/apache.xml
tomcat/connectors/trunk/jk/xdocs/webserver_howto/iis.xml
Modified: tomcat/connectors/trunk/jk/xdocs/webserver_howto/apache.xml
URL:
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk/xdocs/webserver_howto/apache.xml?rev=702807&r1=702806&r2=702807&view=diff
==============================================================================
--- tomcat/connectors/trunk/jk/xdocs/webserver_howto/apache.xml (original)
+++ tomcat/connectors/trunk/jk/xdocs/webserver_howto/apache.xml Wed Oct 8
04:05:32 2008
@@ -55,7 +55,7 @@
<p>
This document was originally part of <b>Tomcat: A Minimalistic User's
Guide</b> written by Gal Shachor,
-but has been split off for organizational reasons.
+but has been split off for organisational reasons.
</p>
<subsection name="Document Conventions and Assumptions">
@@ -141,22 +141,22 @@
</p>
<p>
-Adding a servlet container may somewhat change this behavior.
+Adding a servlet container may somewhat change this behaviour.
Now the web server needs also to perform the following:
</p>
<ul>
<li>
-Load the servlet container adapter library and initialize it (prior to serving
requests).
+Load the servlet container adaptor library and initialise it (prior to serving
requests).
</li>
<li>
When a request arrives, it needs to check and see if a certain request belongs
to a servlet,
-if so it needs to let the adapter take the request and handle it.
+if so it needs to let the adaptor take the request and handle it.
</li>
</ul>
<p>
-The adapter on the other hand needs to know what requests it is going to serve,
+The adaptor on the other hand needs to know what requests it is going to serve,
usually based on some pattern in the request URL, and to where to direct these
requests.
</p>
@@ -300,7 +300,7 @@
ie when you have an Apache in front of a Tomcat Farm.
</li>
<li>
-Another case for custom configuration is when your Apache is in front of many
differents Tomcat engines,
+Another case for custom configuration is when your Apache is in front of many
different Tomcat engines,
each one having it's own configuration, a general case in ISP hosting
</li>
<li>
@@ -389,7 +389,7 @@
<b>error</b> log will contains also error reports.
</li>
<li>
-<b>debug</b> log will contains all informations on mod_jk activity
+<b>debug</b> log will contains all information on mod_jk activity
</li>
</ul>
@@ -421,7 +421,7 @@
<b>JkRequestLogFormat</b> will configure the format of mod_jk individual
request logging.
Request logging is configured and enabled on a per virtual host basis.
To enable request logging for a virtual host just add a JkRequestLogFormat
config.
-The syntax of the format string is similiar to the Apache LogFormat command,
+The syntax of the format string is similar to the Apache LogFormat command,
here is a list of the available request log format options:
</p>
@@ -557,7 +557,7 @@
is not set.
</p>
<p>
-You can also realize such a check with mod_rewrite, which is more powerful
+You can also realise such a check with mod_rewrite, which is more powerful
but also slightly more complicated.
<source>
@@ -707,7 +707,7 @@
The directive <b>JkEnvVar</b> allows you to forward environment variables
from Apache server to Tomcat engine.
You can add a default value as a second parameter to the directive.
-If the default value is not given explicitely, the variable
+If the default value is not given explicitly, the variable
will only be send, if it is set during runtime.
<br/>
The variables can be retrieved on the Tomcat side as request attributes
@@ -931,7 +931,7 @@
<tr valign="top">
<td>--with-apxs[=FILE]</td>
<td>FILE is the location of the apxs tool. Default is finding apxs in PATH.
-It builds a shared Apache module. It detects automaticly the Apache version.
+It builds a shared Apache module. It detects automatically the Apache version.
(2.0/2.2 and 1.3)</td>
</tr>
<tr valign="top"><td>--with-apache=DIR</td>
@@ -948,11 +948,11 @@
<tr valign="top"><td>--enable-prefork</td>
<td>
In case you build mod_jk for a multi-threaded Apache httpd 2.0/2.2 MPM
(Multi-Processing Module),
-some areas of mod_jk code need to be synchronized to make it thread-safe.
+some areas of mod_jk code need to be synchronised to make it thread-safe.
Because configure can not easily detect, whether your are using a
multi-threaded MPM,
mod_jk by default is always build thread-safe for Apache httpd 2.0/2.2.
If you are sure, that your MPM is not multi-threaded, you can use
"--enable-prefork"
-to force the removal of the synchronization code (thus increasing performance
a bit).
+to force the removal of the synchronisation code (thus increasing performance
a bit).
For instance, the prefork MPM is not multi-threaded. For Apache httpd 1.3
this flag will be set automatically.</td>
</tr>
@@ -988,7 +988,7 @@
<tr valign="top"><th>JNI related parameters</th><th></th></tr>
<tr valign="top"><td>--enable-jni</td>
<td>Build the JNI worker and so the build process will require
-some informations about your Java Environment</td>
+some information about your Java Environment</td>
</tr>
<tr valign="top"><td>--with-java-home=DIR</td>
<td>DIR is the patch to the JDK root directory. Something like:
/opt/java/jdk12</td>
@@ -999,7 +999,7 @@
<tr valign="top"><td>--with-arch-type=SUBDIR</td><td>SUBDIR is the arch
subdirectory,
configure should guess it correctly.</td>
</tr>
- <tr valign="top"><td>--with-java-platform=VAL</td><td>VAL is the Java
platform 1 is 1.1.x and 2 is for 1.2 anf higher,
+ <tr valign="top"><td>--with-java-platform=VAL</td><td>VAL is the Java
platform 1 is 1.1.x and 2 is for 1.2 and higher,
configure should guess it correctly.</td>
</tr>
</table>
Modified: tomcat/connectors/trunk/jk/xdocs/webserver_howto/iis.xml
URL:
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk/xdocs/webserver_howto/iis.xml?rev=702807&r1=702806&r2=702807&view=diff
==============================================================================
--- tomcat/connectors/trunk/jk/xdocs/webserver_howto/iis.xml (original)
+++ tomcat/connectors/trunk/jk/xdocs/webserver_howto/iis.xml Wed Oct 8
04:05:32 2008
@@ -324,7 +324,7 @@
<p>
Each context also has a commented out setting to have Tomcat handle all
requests to the context.
You can rename this file (so it won't be overwritten the next time Tomcat is
started) and
-uncomment this setting or make other customizations.
+uncomment this setting or make other customisations.
</p>
<p>
You may also use this file as is in your worker_mount_file setting.
@@ -376,7 +376,7 @@
As you can see the second configuration is more explicit, it actually instruct
the redirector
to redirect only requests to resources under /examples/servlet/ and resources
under /examples/
whose name ends with .jsp.
-This is similar to what is automically written to the
uriworkermap.properties-auto file for each context.
+This is similar to what is automatically written to the
uriworkermap.properties-auto file for each context.
</p>
<p>
@@ -447,7 +447,7 @@
</p>
<p>
-More informations on using and configuring workers in the <a
href="../generic_howto/workers.html">Workers HowTo</a>
+More information on using and configuring workers in the <a
href="../generic_howto/workers.html">Workers HowTo</a>
and in the <a href="../reference/workers.html">worker.properties configuration
reference</a>.
</p>
@@ -509,7 +509,7 @@
<b>uriworkermap.properties</b> file.<br/>
Results may be misleading if <b>worker_mount_file</b> points to a modified
<b>uriworkermap.properties</b>
or the <b>uriworkermap.properties-auto</b> file.<br/>
-It is also assumed that the <b>"/examples" context</b> works correcly if you
access Tomcat directly.
+It is also assumed that the <b>"/examples" context</b> works correctly if you
access Tomcat directly.
</p>
<subsection name="Win98">
@@ -548,7 +548,7 @@
GET "/examples/jsp/index.html HTTP/1.1" 404
</source>
<p>
-then the ISAPI redirector is not recognizing that it should be handling
requests for the "/examples" context.
+then the ISAPI redirector is not recognising that it should be handling
requests for the "/examples" context.
Check the following:
</p>
<ul>
@@ -561,7 +561,7 @@
<li>
Check the worker_mount_file setting typos, name and data.
</li>
-If these are set correctly, the ISAPI redirector should recognize that it
should handle requests for the "/examples" context.
+If these are set correctly, the ISAPI redirector should recognise that it
should handle requests for the "/examples" context.
</ul>
<p>If the last line contains something like:
@@ -572,7 +572,7 @@
</source>
<p>
-then the ISAPI redirector is recognizing that it should handle the request,
+then the ISAPI redirector is recognising that it should handle the request,
but is not successful at getting Tomcat to service the request.
</p>
@@ -675,7 +675,7 @@
<p>
The last line should contain something like: GET "/jakarta/isapi_redirect.dll
HTTP1.1",
-which indicates the ISAPI redirector is recognizing that it should handle the
request.
+which indicates the ISAPI redirector is recognising that it should handle the
request.
</p>
<p>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
