From b043c33cc6f170a0a9d4afaf4e5e048cb1236ce9 Mon Sep 17 00:00:00 2001 From: Emiel Bruijntjes Date: Tue, 15 Apr 2014 14:33:40 +0200 Subject: [PATCH] update documentation --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 44c08d9..ddc6605 100644 --- a/README.md +++ b/README.md @@ -287,8 +287,8 @@ myChannel.onReady([]() { }); ```` -In theory, you should always use the onReady() function before you send any -other instructions over the channel. In practive however, the AMQP library +In theory, you should wait for the onReady() callback to be called before you +send any other instructions over the channel. In practice however, the AMQP library caches all instructions that were sent too early, so that you can use the channel object right after it was constructed. @@ -562,7 +562,7 @@ DeferredConsumer &consume(const std::string &queue, const AMQP::Table &arguments ```` As you can see, the consume method returns a DeferredConsumer. This object is a -regular Deferred, with the some additions. The onSuccess() method of a +regular Deferred, with additions. The onSuccess() method of a DeferredConsumer is slightly different than the onSuccess() method of a regular Deferred object: one extra parameter will be supplied to your callback function with the consumer tag.