[jboss-cvs] JBoss Messaging SVN: r6983 - trunk/docs/user-manual/en.

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

Author: ataylor
Date: 2009-05-22 03:26:30 -0400 (Fri, 22 May 2009)
New Revision: 6983

Modified:
   trunk/docs/user-manual/en/command-buffering.xml
Log:
more proof reading updates

Modified: trunk/docs/user-manual/en/command-buffering.xml
===================================================================
--- trunk/docs/user-manual/en/command-buffering.xml	2009-05-22 07:25:11 UTC (rev 6982)
+++ trunk/docs/user-manual/en/command-buffering.xml	2009-05-22 07:26:30 UTC (rev 6983)
@@ -6,7 +6,7 @@
         reconnects to the same server or fails over onto a replica server, as part of the
         reconnection protocol the server informs the client during reconnection with the id of the
         last command it successfully received from that client.</para>
-    <para>If the client has sent more commands than were received befor failover it can replay any
+    <para>If the client has sent more commands than were received before failover it can replay any
         sent commands from its buffer so that the client and server can reconcile their
         states.</para>
     <para>The size of this buffer is configured by the <literal>SendWindowSize</literal> parameter,
@@ -14,14 +14,16 @@
         processed them it will send back a command confirmation to the client, and the client can
         then free up space in the buffer.</para>
     <para>If you are using JMS and you're using the JMS service on the server to load your JMS
-        connection factory instances into JNDI then this parameter can be configured in <literal
-            >jbm-jms.xml</literal> using the element <literal>send-window-size</literal> a. If
-        you're using JMS but not using JNDI then you can set these values directly on the <literal
-            >JBossConnectionFactory</literal> instance using the appropriate setter method.</para>
-    <para>If you're using core you can set these values directly on the <literal
-            >ClientSessionFactory</literal> instance using the appropriate setter method.</para>
-    <para>The send window is specified in bytes, and has a default value of <literal
-        >1MiB</literal>.</para>
+        connection factory instances into JNDI then this parameter can be configured in
+            <literal>jbm-jms.xml</literal> using the element <literal>send-window-size</literal> a.
+        If you're using JMS but not using JNDI then you can set these values directly on the
+            <literal>JBossConnectionFactory</literal> instance using the appropriate setter
+        method.</para>
+    <para>If you're using core you can set these values directly on the
+            <literal>ClientSessionFactory</literal> instance using the appropriate setter
+        method.</para>
+    <para>The send window is specified in bytes, and has a default value of
+        <literal>1MiB</literal>.</para>
     <para>When the send buffer becomes full, any attempts to send more commands from the client will
         block until the client receives a confirmation from the server and clears out the buffer.
         Because of the blocking, the command buffer performs a type of <literal>flow