Author: mturk
Date: Wed Oct 8 03:54:34 2008
New Revision: 702805
URL: http://svn.apache.org/viewvc?rev=702805&view=rev
Log:
Run trough spell checker - English (British)
Modified:
tomcat/connectors/trunk/jk/xdocs/generic_howto/loadbalancers.xml
tomcat/connectors/trunk/jk/xdocs/generic_howto/quick.xml
tomcat/connectors/trunk/jk/xdocs/generic_howto/timeouts.xml
tomcat/connectors/trunk/jk/xdocs/generic_howto/workers.xml
Modified: tomcat/connectors/trunk/jk/xdocs/generic_howto/loadbalancers.xml
URL:
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk/xdocs/generic_howto/loadbalancers.xml?rev=702805&r1=702804&r2=702805&view=diff
==============================================================================
--- tomcat/connectors/trunk/jk/xdocs/generic_howto/loadbalancers.xml (original)
+++ tomcat/connectors/trunk/jk/xdocs/generic_howto/loadbalancers.xml Wed Oct 8
03:54:34 2008
@@ -68,7 +68,7 @@
The overall result is that workers managed by the same lb worker are
load-balanced (based on their lbfactor and current user session) and also
fall-backed so a single Tomcat process death will not "kill" the entire site.
</p>
<warn>
-If you want to use session stickyness, you must set different jvmRoute
attributes
+If you want to use session stickiness, you must set different jvmRoute
attributes
in the Engine element in Tomcat's server.xml. Furthermore the names of the
workers
which are managed by the balancer have to be equal to the jvmRoute of the
Tomcat
instance they connect with.
@@ -115,7 +115,7 @@
worker.worker1.host=node1.domain.org
worker.worker1.type=ajp13
worker.worker1.lbfactor=1
- # Define prefered failover node for worker1
+ # Define preferred failover node for worker1
worker.worker1.redirect=worker2
# Define another worker using ajp13
Modified: tomcat/connectors/trunk/jk/xdocs/generic_howto/quick.xml
URL:
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk/xdocs/generic_howto/quick.xml?rev=702805&r1=702804&r2=702805&view=diff
==============================================================================
--- tomcat/connectors/trunk/jk/xdocs/generic_howto/quick.xml (original)
+++ tomcat/connectors/trunk/jk/xdocs/generic_howto/quick.xml Wed Oct 8
03:54:34 2008
@@ -30,7 +30,7 @@
<section name="Introduction">
<p>
This document describes the configuration files used by JK on the
- Web Server side for the 'impatients':
+ Web Server side for the 'impatient':
<ul>
<li>
<b>workers.properties</b> is a mandatory file used by the webserver and
which
@@ -68,7 +68,7 @@
<section name="Minimum Apache web server configuration">
<p>
- Here is a minimun informations about Apache configuration, a
+ Here is a minimum information about Apache configuration, a
complete documentation is available in <a href="apache.html">Apache
HowTo</a>.
</p>
<p>
@@ -146,7 +146,7 @@
A complete documentation is available in <a href="iis.html">IIS
HowTo</a>.
</p>
<todo>
-More informations to be added!
+More information to be added!
</todo>
</section>
@@ -154,7 +154,7 @@
<p>
A complete documentation is available in <a
href="nes.html">Netscape/iPlanet HowTo</a>.
<todo>
-More informations to be added?
+More information to be added?
</todo>
</p>
</section>
Modified: tomcat/connectors/trunk/jk/xdocs/generic_howto/timeouts.xml
URL:
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk/xdocs/generic_howto/timeouts.xml?rev=702805&r1=702804&r2=702805&view=diff
==============================================================================
--- tomcat/connectors/trunk/jk/xdocs/generic_howto/timeouts.xml (original)
+++ tomcat/connectors/trunk/jk/xdocs/generic_howto/timeouts.xml Wed Oct 8
03:54:34 2008
@@ -30,7 +30,7 @@
<section name="Introduction">
<br/>
<p>Setting communication timeouts is very important to improve the
-communication process. They help to detect problems and stabilize
+communication process. They help to detect problems and stabilise
a distributed system. JK can use several different timeout types, which
can be individually configured. For historical reasons, all of them are
disabled by default. This HowTo explains their use and gives
@@ -48,7 +48,7 @@
</warn>
<warn>
Long Garbage Collection pauses on the backend do not make a good
-fit with some timeouts. Try to optimize your Java memory and GC settings.
+fit with some timeouts. Try to optimise your Java memory and GC settings.
</warn>
</section>
@@ -66,7 +66,7 @@
needed processing resources. A positive answer tells us, that the backend can
be reached
and is actively processing requests. It does not detect, if some context is
deployed
and working. The benefit of CPing/CPong is a fast detection of a communication
-problem with the backend. The downside is a slightly increased laterncy.
+problem with the backend. The downside is a slightly increased latency.
</p>
<p>
The worker attribute <b>connect_timeout</b> sets the wait timeout for CPong
during
@@ -90,7 +90,7 @@
<subsection name="Low-Level TCP Timeouts">
<p>
Some platforms allow to set timeouts for all operations on TCP sockets.
-This is available for Linux and Windows, other patforms do not support this,
+This is available for Linux and Windows, other platforms do not support this,
e.g. Solaris. If your platform supports TCP send and receive timeouts,
you can set them using the worker attribute <b>socket_timeout</b>.
You can not set the two timeouts to different values.
@@ -155,7 +155,7 @@
Until version 1.2.26, the maintenance task only runs, if requests get
processed. So if your web server has processes that do not receive any
requests for a long time, there is no way to close the idle connections
-in its pool. Starting with version 1.2.27 you can configure an independant
+in its pool. Starting with version 1.2.27 you can configure an independent
watchdog thread when using Apache 2.x with threaded APR or IIS.
</p>
<p>
@@ -176,7 +176,7 @@
</p>
<p>
The JK attribute <b>connection_pool_minsize</b> defines,
-how many idle connections remain when the pool gets shrinked.
+how many idle connections remain when the pool gets shrunken.
By default this is half of the maximum pool size.
</p>
</subsection>
@@ -238,16 +238,16 @@
reply timeout, because downloads could last for many minutes.
Most applications though have limited processing time before starting
to return the response. For those applications you could set an explicit
-reply timeout. Applications that do not harmonize with reply timeouts
+reply timeout. Applications that do not harmonise with reply timeouts
are batch type applications, data warehouse and reporting applications
which are expected to observe long processing times.
</p>
<warn>
If JK aborts waiting for a response, because a reply timeout fired,
there is no way to stop processing on the backend. Although you free
-processing ressources in your web server, the request
+processing resources in your web server, the request
will continue to run on the backend - without any way to send back a
-result once the reply timout fired.
+result once the reply timeout fired.
</warn>
<p>
JK uses the worker attribute <b>reply_timeout</b> to set reply timeouts.
Modified: tomcat/connectors/trunk/jk/xdocs/generic_howto/workers.xml
URL:
http://svn.apache.org/viewvc/tomcat/connectors/trunk/jk/xdocs/generic_howto/workers.xml?rev=702805&r1=702804&r2=702805&view=diff
==============================================================================
--- tomcat/connectors/trunk/jk/xdocs/generic_howto/workers.xml (original)
+++ tomcat/connectors/trunk/jk/xdocs/generic_howto/workers.xml Wed Oct 8
03:54:34 2008
@@ -25,7 +25,7 @@
<title>Workers HowTo</title>
<author email="[EMAIL PROTECTED]">Henri Gomez</author>
<author email="[EMAIL PROTECTED]">Gal Shachor</author>
-<author email="[EMAIL PROTECTED]">Mladen Tur</author>
+<author email="[EMAIL PROTECTED]">Mladen Turk</author>
<date>$Date$</date>
</properties>
<body>
@@ -64,7 +64,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>
</section>
@@ -308,7 +308,7 @@
<p>
You can define "macros" in the property files.
These macros let you define properties and later on use them while
-constructing other properties and it's very usefull when you want to
+constructing other properties and it's very useful when you want to
change your Java Home, Tomcat Home or OS path separator
</p>
@@ -330,7 +330,7 @@
Workers can reference configurations of other workers.
If worker "x" references worker "y", then it inherits all
configuration parameters from "y", except for the ones
-that have explicitely been set for "x".
+that have explicitly been set for "x".
</p>
<source>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
