INT-1552 polished gateway docs, renamed sections in adapter, bridge and router

docs/src/reference/docbook/bridge.xml

@@ -27,7 +27,7 @@
   </section>
 
   <section id="bridge-namespace">
-    <title>The &lt;bridge&gt; Element</title>
+    <title>Configuring Bridge</title>
     <para>
       The &lt;bridge&gt; element is used to create a Messaging Bridge between two Message Channels or Channel Adapters.
       Simply provide the "input-channel" and "output-channel" attributes:

docs/src/reference/docbook/channel-adapter.xml

@@ -12,7 +12,7 @@
   </para>
 
   <section id="channel-adapter-namespace-inbound">
-    <title>The &lt;inbound-channel-adapter&gt; element</title>
+    <title>Configuring Inbound Channel Adapter</title>
     <para>
       An "inbound-channel-adapter" element can invoke any method on a Spring-managed Object and send a non-null return
       value to a <interfacename>MessageChannel</interfacename> after converting it to a <classname>Message</classname>.
@@ -38,7 +38,7 @@
   </section>
 
   <section id="channel-adapter-namespace-outbound">
-    <title>The &lt;outbound-channel-adapter/&gt; element</title>
+    <title>Configuring Outbound Channel Adapter</title>
     <para>
       An "outbound-channel-adapter" element can also connect a <interfacename>MessageChannel</interfacename> to any POJO consumer
       method that should be invoked with the payload of Messages sent to that channel.

docs/src/reference/docbook/gateway.xml

@@ -15,13 +15,13 @@ package org.cafeteria;
 
 public interface Cafe {
 
-	void placeOrder(Order order);
+		void placeOrder(Order order);
 	
 }
 ]]></programlisting>
      
       Namespace support is also
-      provided as demonstrated by the following example.
+      provided which allows you to configure such interface as a service and is demonstrated by the following example.
       <programlisting language="xml"><![CDATA[<gateway id="cafeService"
          service-interface="org.cafeteria.Cafe"
          default-request-channel="requestChannel"

docs/src/reference/docbook/router.xml

@@ -150,7 +150,9 @@
   </section>
 
   <section id="router-namespace">
-    <title>Namespace support for Router - &lt;router&gt; element</title>
+  	<title>Configuring Router</title>
+  	<section>
+    <title>Configuring Router with XML</title>
     <para>
     The "router" element provides a simple way to connect a router to an input channel, and also accepts the
       optional default output channel. The "ref" may provide the bean name of a custom Router implementation
@@ -211,7 +213,7 @@
   </section>
 
   <section id="router-annotation">
-    <title>The @Router Annotation</title>
+    <title>Configuring Router with Annotations</title>
     <para>
       When using the <interfacename>@Router</interfacename> annotation, the annotated method can return either the
       <interfacename>MessageChannel</interfacename> or <classname>String</classname> type. In the case of the latter,
@@ -239,6 +241,10 @@ public List&lt;String&gt; route(Foo payload) {...}</programlisting>
 public List&lt;String&gt; route(@Header("orderStatus") OrderStatus status)</programlisting>
     </para>
   </section>
+  	
+  </section>
+  
+  
   <note>
     For routing of XML-based Messages, including XPath support, see <xref linkend="xml"/>.
   </note>