[jboss-cvs] JBossRemoting/docs/guide/en ...

[Ron Sigal]

  User: rsigal  
  Date: 06/08/01 19:23:14

  Modified:    docs/guide/en  chap3.xml
  Log:
  JBREM-559:  Fixed some typos.
  
  Revision  Changes    Path
  1.3       +4 -5      JBossRemoting/docs/guide/en/chap3.xml
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: chap3.xml
  ===================================================================
  RCS file: /cvsroot/jboss/JBossRemoting/docs/guide/en/chap3.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -b -r1.2 -r1.3
  --- chap3.xml	31 Jul 2006 05:03:42 -0000	1.2
  +++ chap3.xml	1 Aug 2006 23:23:14 -0000	1.3
  @@ -123,7 +123,7 @@
     to see if a system property for 'jboss.identity' has been set already. If it
     has, will use that one. If not, will get the value for the 'ServerDataDir'
     attribute of the 'jboss.system:type=ServerConfig' mbean. If can retrieve
  -  this value, will just this as the directory to write out the
  +  this value, will use this as the directory to write out the
     'jboss.identity' file. If not, will look to see if a system property has
     been set for 'jboss.identity.dir'. If it has, will use this as the directory
     to write the 'jboss.identity' file to, otherwise, will default to '.'. If
  @@ -177,8 +177,8 @@
       client instance will receive these detection messages and update a local
       registry, called the network registry, with this information. The client
       detector will also monitor the remoting servers it has discovered in case
  -    one where to fail, in which case, will notify the network registry of the
  -    failure The network registry will then fire events to registered listenes
  +    one were to fail, in which case, will notify the network registry of the
  +    failure The network registry will then fire events to registered listeners
       (via JMX notifications), to include events such as new server added or
       server failure.</para>
   
  @@ -214,8 +214,7 @@
       respectively. The package under which the TransportClientFactory and
       TransportServerFactory will always start with
       <code>org.jboss.test.remoting.transport</code>, then the transport
  -    protocol type. For example, the 'socket' transport factories can be found
  -    under
  +    protocol type. For example, the 'socket' transport factories are
       <code>org.jboss.remoting.transport.socket.TransportClientFactory</code>
       and
       <code>org.jboss.remoting.transport.socket.TransportServerFactory</code>.