Author: kkolinko
Date: Wed Jun 17 11:47:55 2009
New Revision: 785562
URL: http://svn.apache.org/viewvc?rev=785562&view=rev
Log:
trivial: corrected spelling errors in docs
Modified:
tomcat/container/tc5.5.x/webapps/docs/appdev/installation.xml
tomcat/container/tc5.5.x/webapps/docs/appdev/introduction.xml
tomcat/container/tc5.5.x/webapps/docs/apr.xml
tomcat/container/tc5.5.x/webapps/docs/architecture/overview.xml
tomcat/container/tc5.5.x/webapps/docs/architecture/requestProcess.xml
tomcat/container/tc5.5.x/webapps/docs/balancer-howto.xml
tomcat/container/tc5.5.x/webapps/docs/class-loader-howto.xml
tomcat/container/tc5.5.x/webapps/docs/cluster-howto.xml
tomcat/container/tc5.5.x/webapps/docs/config/ajp.xml
tomcat/container/tc5.5.x/webapps/docs/config/context.xml
tomcat/container/tc5.5.x/webapps/docs/config/engine.xml
tomcat/container/tc5.5.x/webapps/docs/config/globalresources.xml
tomcat/container/tc5.5.x/webapps/docs/config/host.xml
tomcat/container/tc5.5.x/webapps/docs/config/http.xml
tomcat/container/tc5.5.x/webapps/docs/config/index.xml
tomcat/container/tc5.5.x/webapps/docs/config/loader.xml
tomcat/container/tc5.5.x/webapps/docs/config/manager.xml
tomcat/container/tc5.5.x/webapps/docs/config/resources.xml
tomcat/container/tc5.5.x/webapps/docs/config/systemprops.xml
tomcat/container/tc5.5.x/webapps/docs/config/valve.xml
tomcat/container/tc5.5.x/webapps/docs/default-servlet.xml
tomcat/container/tc5.5.x/webapps/docs/deployer-howto.xml
tomcat/container/tc5.5.x/webapps/docs/funcspecs/fs-admin-apps.xml
tomcat/container/tc5.5.x/webapps/docs/funcspecs/fs-admin-objects.xml
tomcat/container/tc5.5.x/webapps/docs/funcspecs/fs-default.xml
tomcat/container/tc5.5.x/webapps/docs/funcspecs/index.xml
tomcat/container/tc5.5.x/webapps/docs/html-manager-howto.xml
tomcat/container/tc5.5.x/webapps/docs/jasper-howto.xml
tomcat/container/tc5.5.x/webapps/docs/jndi-datasource-examples-howto.xml
tomcat/container/tc5.5.x/webapps/docs/logging.xml
tomcat/container/tc5.5.x/webapps/docs/manager-howto.xml
tomcat/container/tc5.5.x/webapps/docs/monitoring.xml
tomcat/container/tc5.5.x/webapps/docs/realm-howto.xml
tomcat/container/tc5.5.x/webapps/docs/ssi-howto.xml
tomcat/container/tc5.5.x/webapps/docs/ssl-howto.xml
tomcat/container/tc5.5.x/webapps/docs/windows-service-howto.xml
Modified: tomcat/container/tc5.5.x/webapps/docs/appdev/installation.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/appdev/installation.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/appdev/installation.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/appdev/installation.xml Wed Jun 17
11:47:55 2009
@@ -40,7 +40,7 @@
<subsection name="JDK">
<p>Tomcat 5.5 was designed to run on J2SE 5.0, but it can run on JDK 1.4
-as well, using the compatability package as detailed in the Tomcat
+as well, using the compatibility package as detailed in the Tomcat
installation instructions.
</p>
Modified: tomcat/container/tc5.5.x/webapps/docs/appdev/introduction.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/appdev/introduction.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/appdev/introduction.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/appdev/introduction.xml Wed Jun 17
11:47:55 2009
@@ -63,7 +63,7 @@
web applications with Tomcat.</p>
<ul>
<li><a
href="http://java.sun.com/products/jsp/download.html";>http://java.sun.com/products/jsp/download.html</a>
-
- <i>JavaServer Pages (JSP) Specfication, Version 2.0</i>. Describes
+ <i>JavaServer Pages (JSP) Specification, Version 2.0</i>. Describes
the programming environment provided by standard implementations
of the JavaServer Pages (JSP) technology. In conjunction with
the Servlet API Specification (see below), this document describes
Modified: tomcat/container/tc5.5.x/webapps/docs/apr.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/apr.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/apr.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/apr.xml Wed Jun 17 11:47:55 2009
@@ -237,7 +237,7 @@
</attribute>
<attribute name="SSLPassword" required="false">
<p>
- Pass phrase for the encrypted private key. If "SSLPassword" is not
provided, the callback fonction
+ Pass phrase for the encrypted private key. If "SSLPassword" is not
provided, the callback function
should prompt for the pass phrase.
</p>
</attribute>
Modified: tomcat/container/tc5.5.x/webapps/docs/architecture/overview.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/architecture/overview.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/architecture/overview.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/architecture/overview.xml Wed Jun 17
11:47:55 2009
@@ -96,7 +96,7 @@
<a href="../config/coyote.html">Coyote connector</a> which is used for
most HTTP traffic, especially when running Tomcat as a standalone server,
and the <a href="../config/jk2.html">JK2 connector</a> which implements
-the AJP procotol used when connecting Tomcat to an Apache HTTPD server.
+the AJP protocol used when connecting Tomcat to an Apache HTTPD server.
Creating a customized connector is a significant effort.
</p>
</subsection>
@@ -127,9 +127,9 @@
</p>
<p>
In recent releases of Tomcat, mostly starting with Tomcat 5,
-we have begun effots to make more aspects of Tomcat managable via
+we have begun efforts to make more aspects of Tomcat manageable via
JMX. In addition, the Manager and Admin webapps have been greatly
-enhanced and improved. Managability is a primary area of concern
+enhanced and improved. Manageability is a primary area of concern
for us as the product matures and the specification becomes more
stable.
</p>
Modified: tomcat/container/tc5.5.x/webapps/docs/architecture/requestProcess.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/architecture/requestProcess.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/architecture/requestProcess.xml
(original)
+++ tomcat/container/tc5.5.x/webapps/docs/architecture/requestProcess.xml Wed
Jun 17 11:47:55 2009
@@ -55,7 +55,7 @@
<subsection name="comments">
<p>
The Servlet Specification provides many opportunities for
-listening in (using Listeners) or modiying (using Filters)
+listening in (using Listeners) or modifying (using Filters)
the request handling process even before the request arrives
at the servlet that will handle it.
</p>
Modified: tomcat/container/tc5.5.x/webapps/docs/balancer-howto.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/balancer-howto.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/balancer-howto.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/balancer-howto.xml Wed Jun 17
11:47:55 2009
@@ -50,7 +50,7 @@
<section name="Using Apache HTTP Server 2.x with mod_proxy">
Please refer to the mod_proxy documentation for Apache HTTP Server 2.2. This
supports either
-HTTP or AJP load balancing. This new version of mod_proxy is also useable with
+HTTP or AJP load balancing. This new version of mod_proxy is also usable with
Apache HTTP Server 2.0, but mod_proxy will have to be compiled separately
using the code
from Apache HTTP Server 2.2.
@@ -62,7 +62,7 @@
<p>
Tomcat 5.0.15 and later ships with a webapp named balancer. This is
-a simple implemention of a rules-based load balancer. It was not designed
+a simple implementation of a rules-based load balancer. It was not designed
as a replacement for other load-balancing mechanisms used for high traffic
environments. Rather, it is a simple, pure Java, easily extensible, and fast
way to direct traffic among multiple servers.
Modified: tomcat/container/tc5.5.x/webapps/docs/class-loader-howto.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/class-loader-howto.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/class-loader-howto.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/class-loader-howto.xml Wed Jun 17
11:47:55 2009
@@ -229,7 +229,7 @@
loading looks in the following repositories, in this order:</p>
<ul>
<li>Bootstrap classes of your JVM</li>
-<li>System class loader classses (described above)</li>
+<li>System class loader classes (described above)</li>
<li><em>/WEB-INF/classes</em> of your web application</li>
<li><em>/WEB-INF/lib/*.jar</em> of your web application</li>
<li><em>$CATALINA_HOME/common/classes</em></li>
Modified: tomcat/container/tc5.5.x/webapps/docs/cluster-howto.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/cluster-howto.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/cluster-howto.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/cluster-howto.xml Wed Jun 17 11:47:55
2009
@@ -87,7 +87,7 @@
</source>
<p>What is important to mention here, is that session replication is only the
beginning of clustering.
- Another popular concept used to implement clusters is farming, ie, you
deploy your apps only to one
+ Another popular concept used to implement clusters is farming, i.e., you
deploy your apps only to one
server, and the cluster will distribute the deployments across the entire
cluster.
This is all capabilities that can go into with the FarmWarDeployer (s.
cluster example at <code>server.xml</code>)</p>
<p>In the next section will go deeper into how session replication works and
how to configure it.</p>
@@ -95,7 +95,7 @@
</section>
<section name="How it Works">
-<p>To make it easy to understand how clustering works, We are gonna take you
through a series of scenarios.
+<p>To make it easy to understand how clustering works, We are going to take
you through a series of scenarios.
In the scenario we only plan to use two tomcat instances
<code>TomcatA</code> and <code>TomcatB</code>.
We will cover the following sequence of events:</p>
@@ -111,7 +111,7 @@
<li><code>TomcatA</code> The session <code>S2</code> expires due to
inactivity.</li>
</ol>
-<p>Ok, now that we have a good sequence, we will take you through exactly what
happens in the session repliction code</p>
+<p>Ok, now that we have a good sequence, we will take you through exactly what
happens in the session replication code</p>
<ol>
<li><b><code>TomcatA</code> starts up</b>
@@ -143,7 +143,7 @@
The request coming in to TomcatA is treated exactly the same way as
without session replication.
The action happens when the request is completed, the
<code>ReplicationValve</code> will intercept
the request before the response is returned to the user.
- At this point it finds that the session has been modified, and it uses
TCP to replicata the
+ At this point it finds that the session has been modified, and it uses
TCP to replicate the
session to TomcatB. Once the serialized data has been handed off to
the operating systems TCP logic,
the request returns to the user, back through the valve pipeline.
For each request the entire session is replicated, this allows code
that modifies attributes
@@ -190,7 +190,7 @@
<li><code>TomcatA</code> The session <code>S2</code> expires due to inactivity.
<p>The invalidate is call is intercepted the same was as when a session is
invalidated by the user,
and the session is queued with invalidated sessions.
- At this point, the invalidet session will not be replicated across until
+ At this point, the invalidated session will not be replicated across
until
another request comes through the system and checks the invalid queue.
</p><p></p>
</li>
@@ -220,7 +220,7 @@
Tomcat does not keep session instances in sync across the cluster.
The implementation of such logic would be to much overhead and cause all
kinds of problems. If your client accesses the same session
- simultanously using multiple requests, then the last request
+ simultaneously using multiple requests, then the last request
will override the other sessions in the cluster.
</p>
@@ -314,7 +314,7 @@
mode. In a synchronous replication mode the request doesn't return until
the replicated session has been
sent over the wire and reinstantiated on all the other cluster nodes.
There are two settings for synchronous replication. Pooled or not pooled.
- Not pooled (ie replicationMode="fastasnycqueue" or
"synchronous") means that all the replication request are sent over a
single
+ Not pooled (i.e. replicationMode="fastasnycqueue" or
"synchronous") means that all the replication request are sent over a
single
socket.
Using synchronous mode can potentially becomes a bottleneck when a lot of
messages generated,
You can overcome this bottleneck by setting
replicationMode="pooled" but then you worker threads blocks with
replication .
@@ -452,7 +452,7 @@
<section name="Complex Cluster Configuration">
<p>
<br/><b>Example</b> Configure cluster with complete sub elements. Activate
this node
-as master farm delopyer. Message receiver is NIO based
<em>ReplicationListener</em> with six parallel
+as master farm deployer. Message receiver is NIO based
<em>ReplicationListener</em> with six parallel
worker threads.
<br/>
<source>
Modified: tomcat/container/tc5.5.x/webapps/docs/config/ajp.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/config/ajp.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/config/ajp.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/config/ajp.xml Wed Jun 17 11:47:55
2009
@@ -174,7 +174,7 @@
<p>This specifies if the encoding specified in contentType should be used
for URI query parameters, instead of using the URIEncoding. This
setting is present for compatibility with Tomcat 4.1.x, where the
- encoding specified in the contentType, or explicitely set using
+ encoding specified in the contentType, or explicitly set using
Request.setCharacterEncoding method was also used for the parameters from
the URL. The default value is <code>false</code>.
</p>
@@ -188,7 +188,7 @@
<attribute name="xpoweredBy" required="false">
<p>Set this attribute to <code>true</code> to cause Tomcat to advertise
- support for the Srevlet specification using the header recommended in the
+ support for the Servlet specification using the header recommended in the
specification. The default value is <code>false</code>.</p>
</attribute>
@@ -239,7 +239,7 @@
<attribute name="minProcessors" required="false">
<strong>deprecated</strong>
<p>The minimum number of processors to start at initialization time.
- If not specified, this atttribute is set to 5.</p>
+ If not specified, this attribute is set to 5.</p>
</attribute>
<attribute name="maxProcessors" required="false">
@@ -252,7 +252,7 @@
value of Apache's <code>maxClients</code> directive.</p>
<p>A <code>maxProcessors</code> value of zero (0) signifies that
the number of processors is unlimited. If not specified, this
- atttribute defaults to 20.</p>
+ attribute defaults to 20.</p>
</attribute>
<attribute name="maxSpareThreads" required="false">
@@ -298,7 +298,7 @@
</attribute>
<attribute name="request.shutdownEnabled" required="false">
- <p>If true and a secret has been configured, a correctly fomatted AJP
+ <p>If true and a secret has been configured, a correctly formatted AJP
request (that includes the secret) will shutdown the Tomcat instance
associated with this connector. This is set to <code>false</code> by
default.</p>
@@ -318,7 +318,7 @@
</attribute>
<attribute name="tomcatAuthentication" required="false">
- <p>If set to <code>true</code>, the authetication will be done in
Tomcat.
+ <p>If set to <code>true</code>, the authentication will be done in
Tomcat.
Otherwise, the authenticated principal will be propagated from the native
webserver and used for authorization in Tomcat.
The default value is <code>true</code>.</p>
Modified: tomcat/container/tc5.5.x/webapps/docs/config/context.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/config/context.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/config/context.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/config/context.xml Wed Jun 17
11:47:55 2009
@@ -61,7 +61,7 @@
<p><b>For Tomcat 5, unlike Tomcat 4.x, it is NOT recommended to place
<Context> elements directly in the server.xml file.</b> This
- is because it makes modifing the <strong>Context</strong> configuration
+ is because it makes modifying the <strong>Context</strong> configuration
more invasive since the main <code>conf/server.xml</code> file cannot be
reloaded without restarting Tomcat.</p>
@@ -176,7 +176,7 @@
owning <a href="host.html">Host</a>.</p>
<p>If a symbolic link is used for docBase then changes to the
symbolic link will only be effective after a Tomcat restart or
- by undeploying and redeploying the conext. A context reload is not
+ by undeploying and redeploying the context. A context reload is not
sufficient.</p>
<p>Do not choose a docBase that starts with your Host's appBase string.
The default appBase is "webapps" so do not choose a docBase like
Modified: tomcat/container/tc5.5.x/webapps/docs/config/engine.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/config/engine.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/config/engine.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/config/engine.xml Wed Jun 17 11:47:55
2009
@@ -94,7 +94,7 @@
<attribute name="name" required="true">
<p>Logical name of this Engine, used in log and error messages.
<em>When
- using muliple <a href="service.html">Service</a> elements in the same
+ using multiple <a href="service.html">Service</a> elements in the same
<a href="server.html">Server</a>, each Engine MUST be assigned a unique
name.</em></p>
</attribute>
@@ -196,7 +196,7 @@
nesting a <strong>Listener</strong> element inside this element. The
class name you specify must implement the
<code>org.apache.catalina.LifecycleListener</code> interface, and
- it will be notified about the occurrence of the coresponding
+ it will be notified about the occurrence of the corresponding
lifecycle events. Configuration of such a listener looks like this:</p>
<source>
Modified: tomcat/container/tc5.5.x/webapps/docs/config/globalresources.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/config/globalresources.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/config/globalresources.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/config/globalresources.xml Wed Jun 17
11:47:55 2009
@@ -179,7 +179,7 @@
<attribute name="auth" required="false">
<p>Specify whether the web Application code signs on to the
- corresponding resource manager programatically, or whether the
+ corresponding resource manager programmatically, or whether the
Container will sign on to the resource manager on behalf of the
application. The value of this attribute must be
<code>Application</code> or <code>Container</code>. This
Modified: tomcat/container/tc5.5.x/webapps/docs/config/host.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/config/host.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/config/host.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/config/host.xml Wed Jun 17 11:47:55
2009
@@ -154,7 +154,7 @@
<attribute name="deployXML" required="false">
<p>Set to <code>false</code> if you want to disable parsing the
context.xml
file embedded inside the application (located at
<code>/META-INF/context.xml</code>).
- Security consious environments should set this to <code>false</code>
to prevent
+ Security conscious environments should set this to <code>false</code>
to prevent
applications from interacting with the container's configuration. The
administrator will then be responsible for providing an external
context
configuration file, and put it in
@@ -164,7 +164,7 @@
<attribute name="errorReportValveClass" required="false">
<p>Java class name of the error reporting valve which will be used
- by this Host. The responsability of this valve is to output error
+ by this Host. The responsibility of this valve is to output error
reports. Setting this property allows to customize the look of the
error pages which will be generated by Tomcat. This class must
implement the
@@ -231,7 +231,7 @@
<p>A host is associated with the
<code>org.apache.catalina.core.ContainerBase.[enginename].[hostname]</code>
- log category. Note that the brackets are actuall part of the name,
+ log category. Note that the brackets are part of the name,
don't omit them.</p>
</subsection>
Modified: tomcat/container/tc5.5.x/webapps/docs/config/http.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/config/http.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/config/http.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/config/http.xml Wed Jun 17 11:47:55
2009
@@ -177,7 +177,7 @@
<p>This specifies if the encoding specified in contentType should be used
for URI query parameters, instead of using the URIEncoding. This
setting is present for compatibility with Tomcat 4.1.x, where the
- encoding specified in the contentType, or explicitely set using
+ encoding specified in the contentType, or explicitly set using
Request.setCharacterEncoding method was also used for the parameters from
the URL. The default value is <code>false</code>.
</p>
@@ -185,7 +185,7 @@
<attribute name="useIPVHosts" required="false">
<p>Set this attribute to <code>true</code> to cause Tomcat to use
- the IP address that the request was recieved on to determine the Host
+ the IP address that the request was received on to determine the Host
to send the request to. The default value is <code>false</code>.</p>
</attribute>
Modified: tomcat/container/tc5.5.x/webapps/docs/config/index.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/config/index.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/config/index.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/config/index.xml Wed Jun 17 11:47:55
2009
@@ -65,7 +65,7 @@
<ul>
<li><strong>Introduction</strong> - Overall description of this particular
component. There will be a corresponding Java <em>interface</em> (in
- the <code>org.apache.catalina</code> pacakge) that is implemented by one
+ the <code>org.apache.catalina</code> package) that is implemented by one
or more standard implementations.</li>
<li><strong>Attributes</strong> - The set of attributes that are legal for
this element. Generally, this will be subdivided into <em>Common</em>
Modified: tomcat/container/tc5.5.x/webapps/docs/config/loader.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/config/loader.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/config/loader.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/config/loader.xml Wed Jun 17 11:47:55
2009
@@ -130,7 +130,7 @@
<attribute name="useSystemClassLoaderAsParent" required="false">
<p>If no parent classloader is specified, should the system
- classloader be used? The default of <code>true</code> mantains
+ classloader be used? The default of <code>true</code> maintains
backwards compatibility with previous releases however most
users will want to set this to <code>false</code> to obtain
the parent classloader from the associated container.</p>
Modified: tomcat/container/tc5.5.x/webapps/docs/config/manager.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/config/manager.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/config/manager.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/config/manager.xml Wed Jun 17
11:47:55 2009
@@ -140,7 +140,7 @@
<attribute name="processExpiresFrequency" required="false">
<p>Frequency of the session expiration, and related manager operations.
Manager operations will be done once for the specified amount of
- backgrondProcess calls (ie, the lower the amount, the more often the
+ backgrondProcess calls (i.e., the lower the amount, the more often the
checks will occur). The minimum value is 1, and the default value is 6.
</p>
</attribute>
@@ -290,7 +290,7 @@
<strong><Store></strong> element inside, which defines the
characteristics of the persistent data storage. Two implementations
of the <code><Store></code> element are currently available,
- with different characteristics, as described belowl</p>
+ with different characteristics, as described below.</p>
<h5>File Based Store</h5>
@@ -451,7 +451,7 @@
<subsection name="Restart Persistence">
- <p>Whenver Catalina is shut down normally and restarted, or when an
+ <p>Whenever Catalina is shut down normally and restarted, or when an
application reload is triggered, the standard Manager implementation
will attempt to serialize all currently active sessions to a disk
file located via the <code>pathname</code> attribute. All such saved
Modified: tomcat/container/tc5.5.x/webapps/docs/config/resources.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/config/resources.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/config/resources.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/config/resources.xml Wed Jun 17
11:47:55 2009
@@ -41,7 +41,7 @@
<p>A unified caching engine is provided for all accesses to the webapp
resources made by the servlet container and web applications which use the
- container provided mechanisms to access such resources, such as class laoder
+ container provided mechanisms to access such resources, such as class loader
access, access through the <code>ServletContext</code> interface, or native
access through the <code>DirectoryContext</code> interface.</p>
Modified: tomcat/container/tc5.5.x/webapps/docs/config/systemprops.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/config/systemprops.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/config/systemprops.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/config/systemprops.xml Wed Jun 17
11:47:55 2009
@@ -39,7 +39,7 @@
<properties>
<property name="org.apache.jasper.compiler.
Parser.STRICT_QUOTE_ESCAPING">
- <p>If <code>false</code> the requirements for escpaing quotes in JSP
+ <p>If <code>false</code> the requirements for escaping quotes in JSP
attributes will be relaxed so that a missing required quote will not
cause an error. If not specified, the specification compliant default of
<code>true</code> will be used.</p>
Modified: tomcat/container/tc5.5.x/webapps/docs/config/valve.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/config/valve.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/config/valve.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/config/valve.xml Wed Jun 17 11:47:55
2009
@@ -122,7 +122,7 @@
</attribute>
<attribute name="rotatable" required="false">
- <p>Deafult true. Flag to determine if log rotation should occur.
+ <p>Default true. Flag to determine if log rotation should occur.
If set to false, then this file is never rotated and
<tt>fileDateFormat</tt> is ignored. Use with caution!
</p>
@@ -333,7 +333,7 @@
subsequent calls to <code>request.setCharacterEncoding()</code> within
the web application will have no effect.</p>
- <p>Note: this Valve is now depracated in favor of the RequestDumperFilter,
+ <p>Note: this Valve is now deprecated in favor of the RequestDumperFilter,
which does the same thing in a portable manner. This Filter is included in
the examples application: see
$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters for the source.</p>
Modified: tomcat/container/tc5.5.x/webapps/docs/default-servlet.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/default-servlet.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/default-servlet.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/default-servlet.xml Wed Jun 17
11:47:55 2009
@@ -124,7 +124,7 @@
<td valign='top'>
If you wish to customize your directory listing, you
can use an XSL transformation. This value is an absolute
- file name which be used for all direcotory listings.
+ file name which be used for all directory listings.
This can be disabled by per webapp by also declaring the
default servlet in your local webapp's web.xml. The format
of the xml is shown below.
@@ -194,7 +194,7 @@
<a name="dir"></a>
<p>You can override DefaultServlet with you own implementation and use that
in your web.xml declaration. If you
-can undertand what was just said, we will assume yo can read the code
+can understand what was just said, we will assume you can read the code
to DefaultServlet servlet and make the appropriate adjustments. (If not,
then that method isn't for you)
</p>
Modified: tomcat/container/tc5.5.x/webapps/docs/deployer-howto.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/deployer-howto.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/deployer-howto.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/deployer-howto.xml Wed Jun 17
11:47:55 2009
@@ -248,7 +248,7 @@
</p>
<p>
- It is assumed the user will be familar with Apache Ant for using
the TCD.
+ It is assumed the user will be familiar with Apache Ant for using
the TCD.
Apache Ant is a scripted build tool. The TCD comes pre-packaged
with a
build script to use. Only a modest understanding of Apache Ant is
required (installation as listed earlier in this page, and
familiarity
@@ -266,8 +266,8 @@
<p>
The TCD uses an exploded web application as input (see the list of
the
- properties used below). A web application that is programatically
- deployed with the deployer may include a Context Desciptor in
+ properties used below). A web application that is programmatically
+ deployed with the deployer may include a Context Descriptor in
<code>/META-INF/context.xml</code>.
</p>
Modified: tomcat/container/tc5.5.x/webapps/docs/funcspecs/fs-admin-apps.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/funcspecs/fs-admin-apps.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/funcspecs/fs-admin-apps.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/funcspecs/fs-admin-apps.xml Wed Jun
17 11:47:55 2009
@@ -125,7 +125,7 @@
<li>It shall be possible to save the configured state of the running
Tomcat container such that this state can be reproduced when the
container is shut down and restarted.</li>
- <li>Adminstrative commands to start up and shut down the overall
+ <li>Administrative commands to start up and shut down the overall
Tomcat container are <strong>out of scope</strong> for the
purposes of these applications. It is assumed that other
(usually platform-specific) mechanisms will be used for container
@@ -272,7 +272,7 @@
described under "External Technologies", above.</li>
<li>Prompts and error messages must be internationalizable to multiple
languages.</li>
- <li>Rendered HTML must be compatible with Netscape Navigator (verson 4.7
+ <li>Rendered HTML must be compatible with Netscape Navigator (version 4.7
or later) and Internet Explorer (version 5.0 or later).</li>
</ul>
Modified: tomcat/container/tc5.5.x/webapps/docs/funcspecs/fs-admin-objects.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/funcspecs/fs-admin-objects.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/funcspecs/fs-admin-objects.xml
(original)
+++ tomcat/container/tc5.5.x/webapps/docs/funcspecs/fs-admin-objects.xml Wed
Jun 17 11:47:55 2009
@@ -226,7 +226,7 @@
<li>An optional <em>Loader</em> representing default configuration
properties for the Loader component of deployed web applications.</li>
<li>An optional <em>Manager</em> representing default configuration
- properties for the Manager component fo deployed web applications.</li>
+ properties for the Manager component of deployed web applications.</li>
</ul>
</section>
Modified: tomcat/container/tc5.5.x/webapps/docs/funcspecs/fs-default.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/funcspecs/fs-default.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/funcspecs/fs-default.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/funcspecs/fs-default.xml Wed Jun 17
11:47:55 2009
@@ -211,7 +211,7 @@
<p>On each HTTP PUT request processed by this servlet, the following
- processing shall be perfomred:</p>
+ processing shall be performed:</p>
<ul>
<li>If modifications to the static resources are not allowed (set by a
configuration parameter), return HTTP status 403 (forbidden).</li>
Modified: tomcat/container/tc5.5.x/webapps/docs/funcspecs/index.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/funcspecs/index.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/funcspecs/index.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/funcspecs/index.xml Wed Jun 17
11:47:55 2009
@@ -55,7 +55,7 @@
<p><em>NOTE</em> - In some cases, the contents of these functional specs has
been "reverse engineered" from existing implementations. This exercise is
-stil useful, because it provides an introduction to <strong>what</strong>
+still useful, because it provides an introduction to <strong>what</strong>
Catalina does, without being as concerned with <strong>how</strong> this is
accomplished.</p>
Modified: tomcat/container/tc5.5.x/webapps/docs/html-manager-howto.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/html-manager-howto.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/html-manager-howto.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/html-manager-howto.xml Wed Jun 17
11:47:55 2009
@@ -85,7 +85,7 @@
applications and provides links for managing them. For each web application
the following is displayed:
<ul>
- <li><strong>Path</strong> - The web applicaton context path.</li>
+ <li><strong>Path</strong> - The web application context path.</li>
<li><strong>Display Name</strong> - The display name for the web application
if it has one configured in its "web.xml" file.</li>
<li><strong>Running</strong> - Whether the web application is running and
Modified: tomcat/container/tc5.5.x/webapps/docs/jasper-howto.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/jasper-howto.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/jasper-howto.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/jasper-howto.xml Wed Jun 17 11:47:55
2009
@@ -47,7 +47,7 @@
specification.</p>
<p>Jasper 2 has been redesigned to significantly improve performance over
-the orignal Jasper. In addition to general code improvements the following
+the original Jasper. In addition to general code improvements the following
changes were made:
<ul>
<li><strong>JSP Custom Tag Pooling</strong> - The java objects instantiated
@@ -57,7 +57,7 @@
a JSP page which had already been compiled Jasper 2 can recompile that
page in the background. The previously compiled JSP page will still be
available to serve requests. Once the new page has been compiled
-successfully it will replace the old page. This helps improve availablity
+successfully it will replace the old page. This helps improve availability
of your JSP pages on a production server.</li>
<li><strong>Recompile JSP when included page changes</strong> - Jasper 2
can now detect when a page included at compile time from a JSP has changed
@@ -128,7 +128,7 @@
<code>clsid:8AD9C840-044E-11D1-B3E9-00805F499D93</code>.</li>
<li><strong>fork</strong> - Have Ant fork JSP page compiles so they are
-performed in a seperate JVM from Tomcat? <code>true</code> or
+performed in a separate JVM from Tomcat? <code>true</code> or
<code>false</code>, default <code>true</code>.</li>
<li><strong>javaEncoding</strong> - Java file encoding to use for generating
Modified:
tomcat/container/tc5.5.x/webapps/docs/jndi-datasource-examples-howto.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/jndi-datasource-examples-howto.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/jndi-datasource-examples-howto.xml
(original)
+++ tomcat/container/tc5.5.x/webapps/docs/jndi-datasource-examples-howto.xml
Wed Jun 17 11:47:55 2009
@@ -50,7 +50,7 @@
shown that specifics for individual configurations can be rather tricky.</p>
<p>Here then are some example configurations that have been posted to
-tomcat-user for popular databases and some general tips for db useage.</p>
+tomcat-user for popular databases and some general tips for db usage.</p>
<p>You should be aware that since these notes are derived from configuration
and/or feedback posted to <code>tomcat-user</code> YMMV :-). Please let us
@@ -110,7 +110,7 @@
<p>
There is one problem with connection pooling. A web application has
-to explicetely close ResultSet's, Statement's, and Connection's.
+to explicitly close ResultSet's, Statement's, and Connection's.
Failure of a web application to close these resources can result in
them never being available again for reuse, a db connection pool "leak".
This can eventually result in your web application db connections failing
@@ -129,7 +129,7 @@
<source>
removeAbandoned="true"
</source>
-When available db connections run low DBCP will recover and recyle
+When available db connections run low DBCP will recover and recycle
any abandoned dB connections it finds. The default is <code>false</code>.
</p>
Modified: tomcat/container/tc5.5.x/webapps/docs/logging.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/logging.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/logging.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/logging.xml Wed Jun 17 11:47:55 2009
@@ -39,7 +39,7 @@
java.util.logging or
<a href="http://logging.apache.org/log4j";>Log4J</a>.
Commons Logging provides Tomcat the ability to log
- hierarchially across various log levels without needing to rely on a
particular
+ hierarchically across various log levels without needing to rely on a
particular
logging implementation.
</p>
<p>
@@ -148,7 +148,7 @@
JDK 5.0 or later, but can be run on JDK 1.4 using a compatibility package.
</p>
<p>
- The default implemenatation of java.util.logging provided in the JDK is
too limited to be
+ The default implementation of java.util.logging provided in the JDK is too
limited to be
useful. A limitation of JDK Logging appears to be the inability to have
per-web application logging,
as the configuration is per-VM. As a result, Tomcat will, in the default
configuration,
replace the default LogManager implementation with a container friendly
implementation
@@ -285,7 +285,7 @@
<section name="Handler Properties">
<p>
- Tomcat's JULI implementation is not intended to be a fully-featured
logging libary, only
+ Tomcat's JULI implementation is not intended to be a fully-featured
logging library, only
a simple bridge to those libraries. However, JULI does provide several
properties
for configuring the its handlers. These are listed below.
</p>
Modified: tomcat/container/tc5.5.x/webapps/docs/manager-howto.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/manager-howto.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/manager-howto.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/manager-howto.xml Wed Jun 17 11:47:55
2009
@@ -250,7 +250,7 @@
absolute path of a web application Context configuration ".xml"
file which contains the Context configuration element.</li>
<li><strong>directory</strong> - The directory name for the web
- applciation context in the Host's application base directory.</li>
+ application context in the Host's application base directory.</li>
<li><strong>webapp.war</strong> - The name of a web application war file
located in the Host's application base directory.</li>
</ul></li>
@@ -258,7 +258,7 @@
<p>Each command will return a response in <code>text/plain</code> format
(i.e. plain ASCII with no HTML markup), making it easy for both humans and
-programs to read). The first line of the response wil begin with either
+programs to read). The first line of the response will begin with either
<code>OK</code> or <code>FAIL</code>, indicating whether the requested
command was successful or not. In the case of failure, the rest of the first
line will contain a description of the problem that was encountered. Some
@@ -649,7 +649,7 @@
JDBC data sources). If you do not specify the <code>type</code> request
parameter, resources of all types will be returned.</p>
-<p>Depending on whether the <code>type</code> request parameter is specfied
+<p>Depending on whether the <code>type</code> request parameter is specified
or not, the first line of a normal response will be:</p>
<pre>
OK - Listed global resources of all types
Modified: tomcat/container/tc5.5.x/webapps/docs/monitoring.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/monitoring.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/monitoring.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/monitoring.xml Wed Jun 17 11:47:55
2009
@@ -34,7 +34,7 @@
<p>Monitoring is a very important question today. Looking inside the running
server, grab some statistic data or reconfigure some aspects are
- daliy adminstration tasks.</p>
+ daily administration tasks.</p>
</section>
@@ -55,7 +55,7 @@
</p>
<p>
<ol>
- <li>When you think authorisation is a good, add and change this :
+ <li>When you think authorization is a good, add and change this :
<source>
-Dcom.sun.management.jmxremote.authenticate=true \
-Dcom.sun.management.jmxremote.password.file=../conf/jmxremote.password \
@@ -73,7 +73,7 @@
monitorRole tomcat
controlRole tomcat
</source>
- <b>Tipp</b>: Password File must be readonly and not accessable from every
+ <b>Tip</b>: Password File must be readonly and not accessible from every
other user! Remove all other users under windows to access this file.
</li>
</ol>
@@ -108,7 +108,7 @@
protocol="AJP/1.3" />
</source>
</p>
- <p><b>Tipp</b>: With <em>${AJP.PORT}=0</em> no ajp connection where
started.
+ <p><b>Tip</b>: With <em>${AJP.PORT}=0</em> no ajp connection where
started.
</p>
<p><b>Note</b>: MX4J JSR 160 RMI Adaptor to support JDK 1.4 currently
not integrated.
</p>
@@ -126,7 +126,7 @@
<section name="Manage Tomcat with JMX remote Ant Tasks">
<p>For simple tomcat ant task usage with ant 1.6.x we have integrate import
and antlib support.</p>
<p><b>antlib support</b>: Copy your catalina-ant.jar from
$CATALINA_HOME/server/lib to $ANT_HOME/lib.</p>
- <p>Following example show the JMX Accessor usage:</p>
+ <p>The following example shows the JMX Accessor usage:</p>
<table border="1">
<tr><td><p><pre>
<project name="Catalina Ant JMX"
@@ -225,7 +225,7 @@
</pre></p>
</td></tr>
</table>
- <p><b>import:</b> Import the JMX Accessor Projekt with
+ <p><b>import:</b> Import the JMX Accessor Project with
<em><import file="${CATALINA.HOME}/bin/jmxaccessor-tasks.xml" /></em>
and
reference the tasks with <em>jmxOpen</em>, <em>jmxSet</em>, <em>jmxGet</em>,
<em>jmxQuery</em>, <em>jmxInvoke</em>,<em>jmxEquals</em> and
<em>jmxCondition</em>. </p>
Modified: tomcat/container/tc5.5.x/webapps/docs/realm-howto.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/realm-howto.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/realm-howto.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/realm-howto.xml Wed Jun 17 11:47:55
2009
@@ -102,7 +102,7 @@
applications to <em>declare</em> their security requirements (in the
<code>web.xml</code> deployment descriptor), there is no portable API
defining the interface between a servlet container and the associated user
-and role information. In many cases, however, it is desireable to "connect"
+and role information. In many cases, however, it is desirable to "connect"
a servlet container to some existing authentication database or mechanism
that already exists in the production environment. Therefore, Tomcat 5
defines a Java interface (<code>org.apache.catalina.Realm</code>) that
@@ -183,7 +183,7 @@
<p>For each of the standard <code>Realm</code> implementations, the
user's password (by default) is stored in clear text. In many
-environments, this is undesireable because casual observers of the
+environments, this is undesirable because casual observers of the
authentication data can collect enough information to log on
successfully, and impersonate other users. To avoid this problem, the
standard implementations support the concept of <em>digesting</em>
@@ -276,7 +276,7 @@
within that application.</p>
<p>For security reasons, no username in the default Realm (i.e. using
-<code>conf/tomcat-users.xml</code> is assigned the "manager" role. Therfore,
+<code>conf/tomcat-users.xml</code> is assigned the "manager" role. Therefore,
no one will be able to utilize the features of this application until the
Tomcat administrator specifically assigns this role to one or more users.</p>
Modified: tomcat/container/tc5.5.x/webapps/docs/ssi-howto.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/ssi-howto.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/ssi-howto.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/ssi-howto.xml Wed Jun 17 11:47:55 2009
@@ -257,7 +257,7 @@
<tr>
<td>HTTP_ACCEPT_LANGUAGE</td>
<td>
- A list of the laguages that the client can accept.</td>
+ A list of the languages that the client can accept.</td>
</tr>
<tr>
<td>HTTP_CONNECTION</td>
Modified: tomcat/container/tc5.5.x/webapps/docs/ssl-howto.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/ssl-howto.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/ssl-howto.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/ssl-howto.xml Wed Jun 17 11:47:55 2009
@@ -199,10 +199,10 @@
</p>
<p>Each entry in a keystore is identified by an alias string. Whilst many
-keystore implmentations treat alaises in a case insensitive manner, case
+keystore implementations treat aliases in a case insensitive manner, case
sensitive implementations are available. The <code>PKCS11</code> specification,
for example, requires that aliases are case sensitive. To avoid issues related
-to the case sensitivity of aliaises, it is not recommended to use aliases that
+to the case sensitivity of aliases, it is not recommended to use aliases that
differ only in case.
</p>
@@ -322,7 +322,7 @@
that SSL is required, as required by the Servlet 2.4 Specification.</p>
</em></blockquote>
-<p>There are addional option used to configure the SSL protocol.
+<p>There are additional option used to configure the SSL protocol.
You may need to add or change the following attribute
values, depending on how you configured your keystore earlier:</p>
Modified: tomcat/container/tc5.5.x/webapps/docs/windows-service-howto.xml
URL:
http://svn.apache.org/viewvc/tomcat/container/tc5.5.x/webapps/docs/windows-service-howto.xml?rev=785562&r1=785561&r2=785562&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/webapps/docs/windows-service-howto.xml (original)
+++ tomcat/container/tc5.5.x/webapps/docs/windows-service-howto.xml Wed Jun 17
11:47:55 2009
@@ -70,7 +70,7 @@
<td>Run the service as console application</td>
<td>This is the default operation. It is called if the no option is
provided. The ServiceName is the name of the executable without
- exe sufix, meaning Tomcat5</td>
+ exe suffix, meaning Tomcat5</td>
</tr>
<tr><th>//RS//</th>
<td>Run the service</td>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
