From d01a324d617c5ac00eb2f1e9c32a1505740e86d3 Mon Sep 17 00:00:00 2001
From: Mark Fisher <markfisher@vmware.com>
Date: Tue, 26 May 2009 14:59:45 +0000
Subject: [PATCH] INT-660 mentions default TaskScheduler (and provides link)
 instead of MessageBus

---
 spring-integration-reference/src/endpoint.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/spring-integration-reference/src/endpoint.xml b/spring-integration-reference/src/endpoint.xml
index 54aa8fcba9..036047bbaa 100644
--- a/spring-integration-reference/src/endpoint.xml
+++ b/spring-integration-reference/src/endpoint.xml
@@ -216,9 +216,9 @@ consumer.setTransactionManager(txManager);</programlisting>
                             queue-capacity="20"
                             keep-alive-seconds="120"/>]]></programlisting>
       If no 'task-executor' is provided, the consumer's handler will be invoked in the caller's thread. Note that the
-      "caller" is usually the MessageBus' task scheduler. Also, keep in mind that the 'task-executor' attribute can
+      "caller" is usually the default <interfacename>TaskScheduler</interfacename> (see <xref linkend="namespace-taskscheduler"/>). Also, keep in mind that the 'task-executor' attribute can
       provide a reference to any implementation of Spring's <interfacename>TaskExecutor</interfacename> interface by
-      specifying the bean name. The thread pool elements is simply provided for convenience.
+      specifying the bean name. The thread pool element is simply provided for convenience.
     </para>
   </section>
 </chapter>
\ No newline at end of file