From: markt <markt@13f79535-47bb-0310-9956-ffa450edef68>
Date: Mon, 27 Oct 2008 22:48:21 +0000 (+0000)
Subject: Fix https://issues.apache.org/bugzilla/show_bug.cgi?id=46067
X-Git-Url: https://git.internetallee.de/?a=commitdiff_plain;h=bb68fd2d58e03ac15cd61b8a404221c3a5a82315;p=tomcat7.0

Fix https://issues.apache.org/bugzilla/show_bug.cgi?id=46067
Correct some typos.

git-svn-id: https://svn.apache.org/repos/asf/tomcat/trunk@708365 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/webapps/docs/aio.xml b/webapps/docs/aio.xml
index cc8bd29c5..2026bc228 100644
--- a/webapps/docs/aio.xml
+++ b/webapps/docs/aio.xml
@@ -48,7 +48,7 @@
   <section name="Comet support">
 
   <p>
-    Comet support allows a servlet to process IO aynchronously, recieving
+    Comet support allows a servlet to process IO aynchronously, receiving
     events when data is available for reading on the connection (rather than
     always using a blocking read), and writing data back on connections
     asychnonously (most likely responding to some event raised from some
@@ -155,7 +155,7 @@
   <subsection name="Example code">
   
   <p>
-    The following pseudo code servlet implments asynchronous chat functionality using the API
+    The following pseudo code servlet implements asynchronous chat functionality using the API
     described above:
   </p>
   
@@ -299,7 +299,7 @@ public class ChatServlet
   </subsection>
   <subsection name="Comet timeouts">
     <p>If you are using the NIO connector, you can set individual timeouts for your different comet connections.
-       To set a timeout, simple set a request attribute like the following code shows:
+       To set a timeout, simply set a request attribute like the following code shows:
        <source>CometEvent event.... event.setTimeout(30*1000);</source> or
        <source>event.getHttpServletRequest().setAttribute("org.apache.tomcat.comet.timeout", new Integer(30 * 1000));</source>
        This sets the timeout to 30 seconds.