Fix typo causing parsing in samples.xml > entity

docs/src/reference/docbook/index.xml

@@ -91,7 +91,7 @@
   <xi:include href="./xml.xml"/>
   <xi:include href="./security.xml"/>
   <xi:include href="./groovy.xml"/>
-  <!--<xi:include href="./samples.xml"/>-->
+  <xi:include href="./samples.xml"/>
   <xi:include href="./configuration.xml"/>
   <xi:include href="./resources.xml"/>
 

docs/src/reference/docbook/samples.xml

@@ -136,7 +136,6 @@ That includes Samples, so if you can't find what you are looking for let us know
    </remark>
    </important>
  </section>
-
   <section id="samples-impl">
     <title>Samples</title>
      <para>
@@ -146,6 +145,7 @@ That includes Samples, so if you can't find what you are looking for let us know
      However, certain samples require a more detailed and some times graphical explanation. In these section you'll
      find details on samples that we believe require special attention.
      </para>
+     <!-- problem exists somewhere between here XXX -->
       <section id="samples-loan-broker">
         <title>Loan Broker</title>
         <para>
@@ -184,6 +184,7 @@ That includes Samples, so if you can't find what you are looking for let us know
             </listitem>
           </itemizedlist>
       </para>
+      <!-- works up until here XXX -->
       <para>
       The details and variations of this use case are very nicely described in Chapter 9 of the EIP Book, but here is the brief summary;
       A Consumer while shopping for the best Loan Quote(s) subscribes to the services of a Loan Broker, which handles details such as:
@@ -247,7 +248,7 @@ That includes Samples, so if you can't find what you are looking for let us know
       <para>
       The <emphasis>Messaging Gateway</emphasis> pattern provides a simple mechanism to access messaging systems, including our Loan Broker.
       In SI you define the <emphasis>Gateway</emphasis> as a Plain Old Java Interface (no need to provide an implementation), configure it via the
-      XML <emphasis>&lt;gateway&gr;</emphasis> element or via annotation and use it as any other Spring bean. SI will take care of
+      XML <emphasis>&lt;gateway&gt;</emphasis> element or via annotation and use it as any other Spring bean. SI will take care of
       delegating and mapping method invocations to the Messaging infrastructure by generating a <emphasis>Message</emphasis> (payload is mapped to an
       input parameter of the method) and sending it to the designated channel.
       <programlisting language="xml"><![CDATA[<gateway id="loanBrokerGateway"
@@ -372,7 +373,7 @@ That includes Samples, so if you can't find what you are looking for let us know
       <para>Conclusion</para>
       <para>
       As you can see a rather complex process was assembled based on POJO (read existing, legacy), light weight, embeddable messaging
-      framework (Sprig Integration) with a loosely coupled programming model intended to simplify integration of heterogeneous systems
+      framework (Spring Integration) with a loosely coupled programming model intended to simplify integration of heterogeneous systems
       without requiring a heavy-weight ESB-like engine or proprietary development and deployment environment, becouse as a developer you
       should not be porting your Swing or console-based application to an ESB-like server or implementing proprietary interfaces just
       because you have an integration concern.
@@ -383,9 +384,7 @@ That includes Samples, so if you can't find what you are looking for let us know
       and should not require change in design, testing and deployment strategy if such applications need to integrate with one another.
       </para>
     </section>
-
-
-
+    <!-- and here XXX -->
 
     <section id="samples-cafe">
       <title>The Cafe Sample</title>
@@ -658,5 +657,4 @@ That includes Samples, so if you can't find what you are looking for let us know
     </section>
   </section>
 
-
 </appendix>