From 1b863129229b0d41c04c8aa681aeba55b1c3eace Mon Sep 17 00:00:00 2001
From: Oleg Zhurakousky <ozhurakousky@vmware.com>
Date: Fri, 29 Apr 2011 17:03:24 -0400
Subject: [PATCH] INT-1875 polishing

---
 docs/src/reference/docbook/jms.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/src/reference/docbook/jms.xml b/docs/src/reference/docbook/jms.xml
index 0d21a93002..c3f9860347 100644
--- a/docs/src/reference/docbook/jms.xml
+++ b/docs/src/reference/docbook/jms.xml
@@ -211,7 +211,7 @@
     The JMS API headers are passed to the appropriate setter methods (e.g. setJMSReplyTo) whereas other headers will 
     be copied to the general properties of the JMS Message.
 
-    JMS Outbound Gateway is bootstrapped with the default implementation of JmsHeaderMapper which will map 
+    JMS Outbound Gateway is bootstrapped with the default implementation of <classname>JmsHeaderMapper</classname> which will map 
     standard JMS API Headers as well as primitive/String Message Headers. Custom  header mapper could also be
     provided via <code>header-mapper</code> attribute of inbound and outbound gateways.
     </para>