[jboss-cvs] JBossAS SVN: r81936 - projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US.

[jboss-cvs-commits at lists.jboss.org]

Author: irooskov at redhat.com
Date: 2008-12-02 00:33:17 -0500 (Tue, 02 Dec 2008)
New Revision: 81936

Modified:
   projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Conversations.xml
Log:
updated with sentence fix in conversations.xml via jwulf bugzilla


Modified: projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Conversations.xml
===================================================================
--- projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Conversations.xml	2008-12-02 05:06:55 UTC (rev 81935)
+++ projects/docs/enterprise/4.3.3.1/Seam/Seam_Reference_Guide/en-US/Conversations.xml	2008-12-02 05:33:17 UTC (rev 81936)
@@ -1029,10 +1029,10 @@
         Conversational components don't allow real concurrent access therefore
         Seam queues each request to process them serially.  This allows each
         request to be executed in a deterministic fashion. However, a simple
-        queue isn't that great — firstly, if a method is, for some
-        reason, taking a very long time to complete, running it over and over
-        again whenever the client generates a request is bad idea (potential
-        for Denial of Service attacks), and, secondly, AJAX is often to used
+        queue isn't that great —. Firstly if a method is, for some
+        reason, taking a very long time to complete, then running it over and over
+        again whenever the client generates a request is a bad idea (potential
+        for Denial of Service attacks). Secondly, AJAX is often used
         to provide a quick status update to the user, so continuing to run the
         action after a long time isn't useful. 
       </para>