[hornetq-commits] JBoss hornetq SVN: r9860 - trunk/docs/user-manual/en.

[do-not-reply at jboss.org]

Author: clebert.suconic at jboss.com
Date: 2010-11-09 17:59:00 -0500 (Tue, 09 Nov 2010)
New Revision: 9860

Modified:
   trunk/docs/user-manual/en/configuring-transports.xml
   trunk/docs/user-manual/en/using-core.xml
Log:
HORNETQ-565 - fixing typos on the documentation

Modified: trunk/docs/user-manual/en/configuring-transports.xml
===================================================================
--- trunk/docs/user-manual/en/configuring-transports.xml	2010-11-09 19:42:52 UTC (rev 9859)
+++ trunk/docs/user-manual/en/configuring-transports.xml	2010-11-09 22:59:00 UTC (rev 9860)
@@ -96,7 +96,7 @@
                         <literal>HornetQConnectionFactory</literal> it needs to know what server
                     that connection factory will create connections to.</para>
                 <para>That's defined by the <literal>connector-ref</literal> element in the <literal
-                        >hornetq-jms.xml</literal>file on the server side. Let's take a look at a
+                        >hornetq-jms.xml</literal> file on the server side. Let's take a look at a
                     snipped from a <literal>hornetq-jms.xml</literal> file that shows a JMS
                     connection factory that references our netty connector defined in our <literal
                         >hornetq-configuration.xml</literal> file:</para>

Modified: trunk/docs/user-manual/en/using-core.xml
===================================================================
--- trunk/docs/user-manual/en/using-core.xml	2010-11-09 19:42:52 UTC (rev 9859)
+++ trunk/docs/user-manual/en/using-core.xml	2010-11-09 22:59:00 UTC (rev 9860)
@@ -94,7 +94,7 @@
                 <para>In core, there is no concept of a Topic, Topic is a JMS only term. Instead, in
                     core, we just deal with <emphasis>addresses</emphasis> and
                         <emphasis>queues</emphasis>.</para>
-                <para>For example, a JMS topic would implemented by a single address to which many
+                <para>For example, a JMS topic would be implemented by a single address to which many
                     queues are bound. Each queue represents a subscription of the topic. A JMS Queue
                     would be implemented as a single address to which one queue is bound - that
                     queue represents the JMS queue.</para>