tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From violet...@apache.org
Subject svn commit: r1769798 - in /tomcat/site/trunk: docs/migration-7.html docs/whichversion.html xdocs/migration-7.xml xdocs/whichversion.xml
Date Tue, 15 Nov 2016 12:28:16 GMT
Author: violetagg
Date: Tue Nov 15 12:28:15 2016
New Revision: 1769798

URL: http://svn.apache.org/viewvc?rev=1769798&view=rev
Log:
Fix typos

Modified:
    tomcat/site/trunk/docs/migration-7.html
    tomcat/site/trunk/docs/whichversion.html
    tomcat/site/trunk/xdocs/migration-7.xml
    tomcat/site/trunk/xdocs/whichversion.xml

Modified: tomcat/site/trunk/docs/migration-7.html
URL: http://svn.apache.org/viewvc/tomcat/site/trunk/docs/migration-7.html?rev=1769798&r1=1769797&r2=1769798&view=diff
==============================================================================
--- tomcat/site/trunk/docs/migration-7.html (original)
+++ tomcat/site/trunk/docs/migration-7.html Tue Nov 15 12:28:15 2016
@@ -568,7 +568,7 @@ of Apache Tomcat.</p>
       
 <li>if the Host Manager application is accessed through a browser
           by a user who has <code>admin-script</code> role (e.g. for testing
-          the text interface since this inteface is intended for tools
+          the text interface since this interface is intended for tools
           not humans) then all browser windows
           must be closed afterwards to terminate the session.</li>
     
@@ -993,7 +993,7 @@ of Apache Tomcat.</p>
 <div class="text">
     
 <p>The Tomcat developers aim for each patch release to be fully backwards
-       compatible with the previous release.  Occassionally, it is necessary to
+       compatible with the previous release.  Occasionally, it is necessary to
        break backwards compatibility in order to fix a bug. In most cases, these
        changes will go unnoticed. This section lists changes that are not fully
        backwards compatible and might cause breakage when upgrading.</p>

Modified: tomcat/site/trunk/docs/whichversion.html
URL: http://svn.apache.org/viewvc/tomcat/site/trunk/docs/whichversion.html?rev=1769798&r1=1769797&r2=1769798&view=diff
==============================================================================
--- tomcat/site/trunk/docs/whichversion.html (original)
+++ tomcat/site/trunk/docs/whichversion.html Tue Nov 15 12:28:15 2016
@@ -694,7 +694,7 @@ performance and stability.  The 3.2.1 re
 patch.  Version 3.2.2 fixed a large number of bugs and all known
 specification compliance issues.  Version 3.2.3 was a security update that
 closes a serious security hole.  Version 3.2.4 is a minor bug fix release.
-All users of Apache Tomcat versions prior to 3.2.3 should updgrade as soon as
+All users of Apache Tomcat versions prior to 3.2.3 should upgrade as soon as
 possible.  With the exception of fixes for critical security related bugs,
 development on the Apache Tomcat 3.2.x branch has stopped.</p>
 

Modified: tomcat/site/trunk/xdocs/migration-7.xml
URL: http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/migration-7.xml?rev=1769798&r1=1769797&r2=1769798&view=diff
==============================================================================
--- tomcat/site/trunk/xdocs/migration-7.xml (original)
+++ tomcat/site/trunk/xdocs/migration-7.xml Tue Nov 15 12:28:15 2016
@@ -188,7 +188,7 @@ of Apache Tomcat.</p>
           <code>admin-script</code> role.</li>
       <li>if the Host Manager application is accessed through a browser
           by a user who has <code>admin-script</code> role (e.g. for testing
-          the text interface since this inteface is intended for tools
+          the text interface since this interface is intended for tools
           not humans) then all browser windows
           must be closed afterwards to terminate the session.</li>
     </ul>
@@ -478,7 +478,7 @@ of Apache Tomcat.</p>
 <section name="Upgrading 7.0.x">
   <subsection name="Tomcat 7.0.x noteable changes">
     <p>The Tomcat developers aim for each patch release to be fully backwards
-       compatible with the previous release.  Occassionally, it is necessary to
+       compatible with the previous release.  Occasionally, it is necessary to
        break backwards compatibility in order to fix a bug. In most cases, these
        changes will go unnoticed. This section lists changes that are not fully
        backwards compatible and might cause breakage when upgrading.</p>

Modified: tomcat/site/trunk/xdocs/whichversion.xml
URL: http://svn.apache.org/viewvc/tomcat/site/trunk/xdocs/whichversion.xml?rev=1769798&r1=1769797&r2=1769798&view=diff
==============================================================================
--- tomcat/site/trunk/xdocs/whichversion.xml (original)
+++ tomcat/site/trunk/xdocs/whichversion.xml Tue Nov 15 12:28:15 2016
@@ -361,7 +361,7 @@ performance and stability.  The 3.2.1 re
 patch.  Version 3.2.2 fixed a large number of bugs and all known
 specification compliance issues.  Version 3.2.3 was a security update that
 closes a serious security hole.  Version 3.2.4 is a minor bug fix release.
-All users of Apache Tomcat versions prior to 3.2.3 should updgrade as soon as
+All users of Apache Tomcat versions prior to 3.2.3 should upgrade as soon as
 possible.  With the exception of fixes for critical security related bugs,
 development on the Apache Tomcat 3.2.x branch has stopped.</p>
 



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message