diff --git a/src/reference/docbook/changes-2.0-2.1.xml b/src/reference/docbook/changes-2.0-2.1.xml
index 722fc4f981..0a9b3bfff5 100644
--- a/src/reference/docbook/changes-2.0-2.1.xml
+++ b/src/reference/docbook/changes-2.0-2.1.xml
@@ -314,7 +314,7 @@
New Samples
For the 2.1 release of Spring Integration we also expanded the Spring
- Integration Samples project and added many new samples, e.g. sampples
+ Integration Samples project and added many new samples, e.g. samples
covering AMQP support, the new payload enricher, a sample illustrating
techniques for testing Spring Integration flow fragments, as well as
an example for executing Stored Procedures against Oracle. For details
diff --git a/src/reference/docbook/delayer.xml b/src/reference/docbook/delayer.xml
index 9d341a7ba5..df5b56d23a 100644
--- a/src/reference/docbook/delayer.xml
+++ b/src/reference/docbook/delayer.xml
@@ -91,14 +91,14 @@
the ability to not lose Messages on the application shutdown. After application startup, the
DelayHandler reads Messages from its Message Group in the MessageStore
and reschedules them with a delay based on the original arrival time of the Message (if the delay is numeric). For messages
- where the delay header was a Date, that is used when rescheduling.
+ where the delay header was a Date, that is used when rescheduling.
If a delayed Message remained in the MessageStore more
than its 'delay', it will be sent immediately after startup.
The DelayHandler can be exported as a JMX MBean
with managed operations getDelayedMessageCount and reschedulePersistedMessages,
- which allows the rescheduling of delayed persisted Messages at runtime, for example, if the
+ which allows the rescheduling of delayed persisted Messages at runtime, for example, if the
TaskScheduler has previously been stopped. These operations can be invoked via a Control Bus command:
delayerReschedulingMessage = MessageBuilder.withPayload("@'delayer.handler'.reschedulePersistedMessages()").build();