Author: fschumacher
Date: Sun Aug 9 11:57:49 2015
New Revision: 1694872
URL: http://svn.apache.org/r1694872
Log:
Correct double "the"s in the documentation.
Modified:
tomcat/trunk/webapps/docs/config/context.xml
tomcat/trunk/webapps/docs/config/listeners.xml
tomcat/trunk/webapps/docs/config/valve.xml
tomcat/trunk/webapps/docs/funcspecs/fs-default.xml
tomcat/trunk/webapps/docs/funcspecs/fs-jdbc-realm.xml
tomcat/trunk/webapps/docs/funcspecs/fs-jndi-realm.xml
tomcat/trunk/webapps/docs/funcspecs/fs-memory-realm.xml
tomcat/trunk/webapps/docs/manager-howto.xml
tomcat/trunk/webapps/docs/tribes/introduction.xml
Modified: tomcat/trunk/webapps/docs/config/context.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/config/context.xml?rev=1694872&r1=1694871&r2=1694872&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/config/context.xml (original)
+++ tomcat/trunk/webapps/docs/config/context.xml Sun Aug 9 11:57:49 2015
@@ -628,7 +628,7 @@
<p>If <code>true</code> and an <code>sun.net.www.http.HttpClient</code>
keep-alive timer thread has been started by this web application and is
still running, Tomcat will change the context class loader for that
- thread from the web application class loader to the the parent of the
web
+ thread from the web application class loader to the parent of the web
application class loader to prevent a memory leak. Note that the
keep-alive timer thread will stop on its own once the keep-alives all
expire however, on a busy system that might not happen for some time.
If
Modified: tomcat/trunk/webapps/docs/config/listeners.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/config/listeners.xml?rev=1694872&r1=1694871&r2=1694872&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/config/listeners.xml (original)
+++ tomcat/trunk/webapps/docs/config/listeners.xml Sun Aug 9 11:57:49 2015
@@ -192,7 +192,7 @@
<attribute name="driverManagerProtection" required="false">
<p>The first use of <code>java.sql.DriverManager</code> will trigger
the
- loading of JDBC Driver in the the current class loader. The web
+ loading of JDBC Driver in the current class loader. The web
application level memory leak protection can take care of this in most
cases but triggering the loading here has fewer side-effects. The
default is <code>true</code>.</p>
@@ -501,7 +501,7 @@
<attribute name="useLocalPorts" required="false">
<p>Should any clients using these ports be forced to use local ports to
- connect to the the JMX/RMI server. This is useful when tunnelling
+ connect to the JMX/RMI server. This is useful when tunnelling
connections over SSH or similar. Defaults to <code>false</code>.</p>
</attribute>
Modified: tomcat/trunk/webapps/docs/config/valve.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/config/valve.xml?rev=1694872&r1=1694871&r2=1694872&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/config/valve.xml (original)
+++ tomcat/trunk/webapps/docs/config/valve.xml Sun Aug 9 11:57:49 2015
@@ -368,7 +368,7 @@
implements many of the same file handling attributes. The main
difference to the standard <code>AccessLogValve</code> is that
<code>ExtendedAccessLogValve</code> creates log files which
- conform to the the Working Draft for the
+ conform to the Working Draft for the
<a href="http://www.w3.org/TR/WD-logfile.html";>Extended Log File Format</a>
defined by the W3C.</p>
Modified: tomcat/trunk/webapps/docs/funcspecs/fs-default.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/funcspecs/fs-default.xml?rev=1694872&r1=1694871&r2=1694872&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/funcspecs/fs-default.xml (original)
+++ tomcat/trunk/webapps/docs/funcspecs/fs-default.xml Sun Aug 9 11:57:49 2015
@@ -248,7 +248,7 @@
<section name="Testable Assertions">
- <p>In addition the the assertions implied by the functionality requirements
+ <p>In addition to the assertions implied by the functionality requirements
listed above, the following additional assertions shall be tested to
validate the behavior of the default servlet:</p>
<ul>
Modified: tomcat/trunk/webapps/docs/funcspecs/fs-jdbc-realm.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/funcspecs/fs-jdbc-realm.xml?rev=1694872&r1=1694871&r2=1694872&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/funcspecs/fs-jdbc-realm.xml (original)
+++ tomcat/trunk/webapps/docs/funcspecs/fs-jdbc-realm.xml Sun Aug 9 11:57:49
2015
@@ -252,7 +252,7 @@
<section name="Testable Assertions">
- <p>In addition the the assertions implied by the functionality requirements
+ <p>In addition to the assertions implied by the functionality requirements
listed above, the following additional assertions shall be tested to
validate the behavior of <code>JDBCRealm</code>:</p>
<ul>
Modified: tomcat/trunk/webapps/docs/funcspecs/fs-jndi-realm.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/funcspecs/fs-jndi-realm.xml?rev=1694872&r1=1694871&r2=1694872&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/funcspecs/fs-jndi-realm.xml (original)
+++ tomcat/trunk/webapps/docs/funcspecs/fs-jndi-realm.xml Sun Aug 9 11:57:49
2015
@@ -403,7 +403,7 @@
<section name="Testable Assertions">
- <p>In addition the the assertions implied by the functionality requirements
+ <p>In addition to the assertions implied by the functionality requirements
listed above, the following additional assertions shall be tested to
validate the behavior of <code>JNDIRealm</code>:</p>
<ul>
Modified: tomcat/trunk/webapps/docs/funcspecs/fs-memory-realm.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/funcspecs/fs-memory-realm.xml?rev=1694872&r1=1694871&r2=1694872&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/funcspecs/fs-memory-realm.xml (original)
+++ tomcat/trunk/webapps/docs/funcspecs/fs-memory-realm.xml Sun Aug 9 11:57:49
2015
@@ -239,7 +239,7 @@
<section name="Testable Assertions">
- <p>In addition the the assertions implied by the functionality requirements
+ <p>In addition to the assertions implied by the functionality requirements
listed above, the following additional assertions shall be tested to
validate the behavior of <code>MemoryRealm</code>:</p>
<ul>
Modified: tomcat/trunk/webapps/docs/manager-howto.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/manager-howto.xml?rev=1694872&r1=1694871&r2=1694872&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/manager-howto.xml (original)
+++ tomcat/trunk/webapps/docs/manager-howto.xml Sun Aug 9 11:57:49 2015
@@ -781,7 +781,7 @@ error message. Possible causes for prob
<p><strong><span style="color: red;">WARNING</span> - This command will delete
any web
application artifacts that exist within <code>appBase</code> directory
(typically "webapps") for this virtual host</strong>.
-This will delete the the application .WAR, if present,
+This will delete the application .WAR, if present,
the application directory resulting either from a deploy in unpacked form
or from .WAR expansion as well as the XML Context definition from
<code>$CATALINA_BASE/conf/[enginename]/[hostname]/</code> directory.
Modified: tomcat/trunk/webapps/docs/tribes/introduction.xml
URL:
http://svn.apache.org/viewvc/tomcat/trunk/webapps/docs/tribes/introduction.xml?rev=1694872&r1=1694871&r2=1694872&view=diff
==============================================================================
--- tomcat/trunk/webapps/docs/tribes/introduction.xml (original)
+++ tomcat/trunk/webapps/docs/tribes/introduction.xml Sun Aug 9 11:57:49 2015
@@ -198,7 +198,7 @@ myChannel.send(group,myMsg,Channel.SEND_
message basis. Meaning, that your messages are not delivered based on some
static configuration
that remains fixed after the message framework has been started.<br/>
To give you an example of how powerful this feature is, I'll try to
illustrate it with a simple example.
- Imagine you need to send 10 different messages, you could send the the
following way:
+ Imagine you need to send 10 different messages, you could send them the
following way:
</p>
<source><