README.md in freddy-jruby-0.4.3 vs README.md in freddy-jruby-0.4.9

@@ -1,8 +1,8 @@
 # Messaging API supporting acknowledgements and request-response
 
-[![Build Status](https://travis-ci.org/salemove/node-freddy.svg?branch=master)](https://travis-ci.org/salemove/node-freddy)
+[![Build Status](https://travis-ci.org/salemove/freddy.svg?branch=master)](https://travis-ci.org/salemove/freddy)
 [![Code Climate](https://codeclimate.com/github/salemove/freddy/badges/gpa.svg)](https://codeclimate.com/github/salemove/freddy)
 
 ## Setup
 
 * Inject the appropriate logger and set up connection parameters:
@@ -10,10 +10,16 @@
 ```ruby
 logger = Logger.new(STDOUT)
 freddy = Freddy.build(logger, host: 'localhost', port: 5672, user: 'guest', pass: 'guest')
 ```
 
+## Supported message queues
+
+These message queues have been tested and are working with Freddy. Other queues can be added easily:
+
+* [RabbitMQ](https://www.rabbitmq.com/)
+
 ## Delivering messages
 
 ### Simple delivery
 
 #### Send and forget
@@ -123,18 +129,11 @@
 
 The following operations are supported:
 
   * stop responding
 ```ruby
-responder_handler.cancel
+responder_handler.shutdown
 ```
-
-  * delete the destination
-```ruby
-responder_handler.destroy_destination
-```
-
-    * Primary use case is in tests to not leave dangling destinations. It deletes the destination even if there are responders for the same destination in other parts of the system. Use with caution in production code.
 
 
 ## Notes about concurrency
 
 The underlying bunny implementation uses 1 responder thread by default. This means that if there is a time-consuming process or a sleep call in a responder then other responders will not receive messages concurrently.