Improvements

majek · majek · commit b45ca3b2e003 · 2010-10-06T16:27:35.000+01:00
diff --git a/python/tutorial-one.mdx b/python/tutorial-one.mdx
@@ -262,6 +262,17 @@ in our previous code. We could have avoided that if we always run the
 program to run as first. In such case it's a good practice to repeat
 declaring the queue in both programs.
 
+> #### Listing queues
+>
+> Sometimes you may want to see what queues does RabbitMQ store and how many
+> messages are in them. You can do it using the `rabbitmqctl` tool:
+>
+>     $ sudo rabbitmqctl list_queues
+>     Listing queues ...
+>     test    0
+>     ...done.
+
+
 
 Receiving messages from the queue is a bit more complex. Whenever we receive
 a message, a `callback` function is called. In our case
diff --git a/python/tutorial-two.mdx b/python/tutorial-two.mdx
@@ -17,7 +17,7 @@ digraph G {
 
 
 In the first part of this tutorial we've learned how to send messages
-to and receive from a named queue. In this part we'll try to create a
+to and receive from a named queue. In this part we'll create a
 _Task Queue_ to distribute time-consuming work across multiple
 workers.
 
