[jboss-remoting-commits] JBoss Remoting SVN: r6230 - remoting2/branches/2.x/docs/guide/en.

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

Author: ron.sigal at jboss.com
Date: 2011-01-28 19:47:50 -0500 (Fri, 28 Jan 2011)
New Revision: 6230

Modified:
   remoting2/branches/2.x/docs/guide/en/chap9.xml
Log:
JBREM-1271: Corrected misspellings.

Modified: remoting2/branches/2.x/docs/guide/en/chap9.xml
===================================================================
--- remoting2/branches/2.x/docs/guide/en/chap9.xml	2011-01-29 00:47:20 UTC (rev 6229)
+++ remoting2/branches/2.x/docs/guide/en/chap9.xml	2011-01-29 00:47:50 UTC (rev 6230)
@@ -2,7 +2,7 @@
 <chapter id="chapter-connection-failure" xreflabel="Network Connection Monitoring">
   <title>Network Connection Monitoring</title>
   
-  <para>Remoting has two mechanisms for monitoring the health of estabilished
+  <para>Remoting has two mechanisms for monitoring the health of established
   connections, which inform listeners on the client and server sides when a
   possible connection failure has been detected.</para>
   
@@ -103,12 +103,12 @@
     <title>Server side monitoring</title>
   
     <para>A remoting server also has the capability to detect when a client is
-    no longer available. This is done by estabilishing a lease with the remoting
+    no longer available. This is done by establishing a lease with the remoting
     clients that connect to a server. On the client side, an
     <classname>org.jboss.remoting.LeasePinger</classname> periodically sends
     PING messages to the server, and on the server side an
     <classname>org.jboss.remoting.Lease</classname> informs registered listeners
-    if the PING doesn't arrive withing the specified timeout period.</para>
+    if the PING doesn't arrive within the specified timeout period.</para>
   
     <para><emphasis role="bold">Server side activation.</emphasis> To turn on
     server side connection failure detection of remoting clients, it is