README.md in worker_roulette-0.0.7 vs README.md in worker_roulette-0.0.8

@@ -55,21 +55,22 @@
 good_foreman      = WorkerRoulette.foreman('foreman', 'good_channel')
 bad_foreman       = WorkerRoulette.foreman('foreman', 'bad_channel')
 
 publish  = -> do
   good_foreman.enqueue_work_order('some old fashion work')
-  bad_foreman.enqueue_work_order('evil biddings you should not carry out') #channels let us ignore his evil orders
+  bad_foreman.enqueue_work_order('evil biddings you should not carry out')
 end
 
 tradesman.wait_for_work_orders(publish) do |work|
   work.to_s.should match("some old fashion work") #only got the work from the good foreman
+  work.to_s.should_not match("evil")              #channels let us ignore the other's evil orders
   tradesman.unsubscribe
 end
 
 ```
 
 ##Caveat Emptor
-While WorkerRoulette does promise to keep the messages of each consumer processed in order by competing consumers, it does NOT guarantee the order in which the queues themselves will be processed. In general, work is processed in a FIFO order, but for performance reasons this has been left a loose FIFO. For example, if Abdul enqueue_work_orders some ordered messages ('1', '2', and '3') and then so do Mark and Wanda, Mark's messages may be processed first, then it would likely be Abdul's, and then Wanda's. However, even though Mark jumped the line, Abdul's messages will still be processed the order he enqueue_work_orderd them ('1', '2', then '3').
+While WorkerRoulette does promise to keep the messages of each consumer processed in order by competing consumers, it does NOT guarantee the order in which the queues themselves will be processed. In general, work is processed in a FIFO order, but for performance reasons this has been left a loose FIFO. For example, if Abdul enqueues some ordered messages ('1', '2', and '3') and then so do Mark and Wanda, Mark's messages may be processed first, then it would likely be Abdul's, and then Wanda's. However, even though Mark jumped the line, Abdul's messages will still be processed the order he enqueued them ('1', '2', then '3').
 
 ## Installation
 
 Add this line to your application's Gemfile: