From bf6d58de1bad327299462c7f7bb456d3dbf420d7 Mon Sep 17 00:00:00 2001
From: Oleg Zhurakousky <ozhurakousky@vmware.com>
Date: Wed, 6 Jul 2011 11:26:20 -0400
Subject: [PATCH] INT-1954 fixed Twitter documentation regarding
 'metadataStore' bean name

---
 docs/src/reference/docbook/twitter.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/src/reference/docbook/twitter.xml b/docs/src/reference/docbook/twitter.xml
index d9d3692af7..db08bc93e9 100644
--- a/docs/src/reference/docbook/twitter.xml
+++ b/docs/src/reference/docbook/twitter.xml
@@ -150,8 +150,8 @@ twitter.oauth.accessTokenSecret=AbRxUAvyNCtqQtxFK8w5ZMtMj20KFhB6o]]></programlis
   	That means upon restart you may end up with duplicate entries. If you need to persist metadata between Application Context 
   	restarts, you may use the <classname>PropertiesPersistingMetadataStore</classname> (which is backed by a properties file, and a persister
     strategy), or you may create your own custom implementation of the <classname>MetadataStore</classname> interface (e.g., JdbcMetadatStore)
-    and configure it as bean within the Application Context.
-  	<programlisting language="java"><![CDATA[<bean class="org.springframework.integration.store.PropertiesPersistingMetadataStore"/>
+    and configure it as bean named 'metadataStore' within the Application Context.
+  	<programlisting language="java"><![CDATA[<bean id="metadataStore" class="org.springframework.integration.store.PropertiesPersistingMetadataStore"/>
 ]]></programlisting>
 The Poller that is configured as part of any Inbound Twitter Adapter (see below) will simply poll from this MetadataStore to determine the latest tweet
 received.