Fix typos and increase readability of Readme (#698)

Author: kniziol

README.md

@@ -10,7 +10,7 @@
 
 ## About ##
 
-The RabbitMqBundle incorporates messaging in your application via [RabbitMQ](http://www.rabbitmq.com/) using the [php-amqplib](http://github.com/php-amqplib/php-amqplib) library.
+The `RabbitMqBundle` incorporates messaging in your application via [RabbitMQ](http://www.rabbitmq.com/) using the [php-amqplib](http://github.com/php-amqplib/php-amqplib) library.
 
 The bundle implements several messaging patterns as seen on the [Thumper](https://github.com/php-amqplib/Thumper) library. Therefore publishing messages to RabbitMQ from a Symfony controller is as easy as:
 
@@ -386,7 +386,7 @@ class OnConsumeEvent extends AMQPEvent
 ```
 
 Let`s say you need to sleep / stop consumer/s on a new application deploy.
-You can listen for OnConsumeEvent (\OldSound\RabbitMqBundle\Event\OnConsumeEvent) and check for new application deploy.
+You can listen for `OldSound\RabbitMqBundle\Event\OnConsumeEvent` and check for new application deploy.
 
 ##### BEFORE PROCESSING MESSAGE #####
 
@@ -407,7 +407,7 @@ class BeforeProcessingMessageEvent extends AMQPEvent
     }
 }
 ``` 
-Event raised before processing a AMQPMessage.
+Event raised before processing a `AMQPMessage`.
 
 ##### AFTER PROCESSING MESSAGE #####
 
@@ -428,7 +428,7 @@ class AfterProcessingMessageEvent extends AMQPEvent
     }
 }
 ``` 
-Event raised after processing a AMQPMessage.
+Event raised after processing a `AMQPMessage`.
 If the process message will throw an Exception the event will not raise.
 
 ##### IDLE MESSAGE #####
@@ -460,7 +460,7 @@ By default process exit on idle timeout, you can prevent it by setting `$event->
 #### Idle timeout ####
 
 If you need to set a timeout when there are no messages from your queue during a period of time, you can set the `idle_timeout` in seconds.
-The `idle_timeout_exit_code` specifies what exit code should be returned by the consumer when the idle timeout occurs. Without specifying it, the consumer will throw an **PhpAmqpLib\Exception\AMQPTimeoutException** exception.
+The `idle_timeout_exit_code` specifies what exit code should be returned by the consumer when the idle timeout occurs. Without specifying it, the consumer will throw an `PhpAmqpLib\Exception\AMQPTimeoutException` exception.
 
 ```yaml
 consumers:
@@ -543,7 +543,7 @@ used for arguments autowiring based on declared type and argument name. This all
 example to:
 
 ```php
-public function indexAction($name, ProducerInteface $uploadPictureProducer)
+public function indexAction($name, ProducerInterface $uploadPictureProducer)
 {
     $msg = array('user_id' => 1235, 'image_path' => '/path/to/new/pic.png');
     $uploadPictureProducer->publish(serialize($msg));
@@ -557,12 +557,12 @@ argument name. `upload_picture_producer` producer key would also be aliased to `
 It is best to avoid names similar in such manner.
 
 All producers are aliased to `OldSound\RabbitMqBundle\RabbitMq\ProducerInterface` and producer class option from 
-configuration. In sandbox mode only ProducerInterface aliases are made. It is highly recommended to use ProducerInterface
+configuration. In sandbox mode only `ProducerInterface` aliases are made. It is highly recommended to use `ProducerInterface`
 class when type hinting arguments for producer injection.
 
-All consumers are aliased to 'OldSound\RabbitMqBundle\RabbitMq\ConsumerInterface' and '%old_sound_rabbit_mq.consumer.class%'
+All consumers are aliased to `OldSound\RabbitMqBundle\RabbitMq\ConsumerInterface` and `%old_sound_rabbit_mq.consumer.class%`
 configuration option value. There is no difference between regular and sandbox mode. It is highly recommended to use
-ConsumerInterface when type hinting arguments for client injection.
+`ConsumerInterface` when type hinting arguments for client injection.
 
 
 ### Callbacks ###
@@ -621,7 +621,7 @@ And that's it!
 ### Audit / Logging ###
 
 This was a requirement to have a traceability of messages received/published.
-In order to enable this you'll need to add "enable_logger" config to consumers or publishers.
+In order to enable this you'll need to add `enable_logger` config to consumers or publishers.
 
 ```yaml
 consumers:
@@ -633,7 +633,7 @@ consumers:
         enable_logger: true
 ```
 
-If you would like you can also treat logging from queues with different handlers in monolog, by referencing channel "phpamqplib"
+If you would like you can also treat logging from queues with different handlers in monolog, by referencing channel `phpamqplib`.
 
 ### RPC or Reply/Response ###
 
@@ -689,7 +689,7 @@ The arguments we are sending are the __min__ and __max__ values for the `rand()`
 
 The final piece is to get the reply. Our PHP script will block till the server returns a value. The __$replies__ variable will be an associative array where each reply from the server will contained in the respective __request\_id__ key.
 
-By default the RPC Client expects the response to be serialized. If the server you are working with returns a non-serialized result then set the RPC client expect_serialized_response option to false. For example, if the integer_store server didn't serialize the result the client would be set as below:
+By default the RPC Client expects the response to be serialized. If the server you are working with returns a non-serialized result then set the RPC client `expect_serialized_response` option to false. For example, if the **integer_store** server didn't serialize the result the client would be set as below:
 
 ```yaml
 rpc_clients:
@@ -719,7 +719,7 @@ As you can guess, we can also make __parallel RPC calls__.
 
 ### Parallel RPC ###
 
-Let's say that for rendering some webpage, you need to perform two database queries, one taking 5 seconds to complete and the other one taking 2 seconds –very expensive queries–. If you execute them sequentially, then your page will be ready to deliver in about 7 seconds. If you run them in parallel then you will have your page served in about 5 seconds. With RabbitMqBundle we can do such parallel calls with ease. Let's define a parallel client in the config and another RPC server:
+Let's say that for rendering some webpage, you need to perform two database queries, one taking 5 seconds to complete and the other one taking 2 seconds –very expensive queries–. If you execute them sequentially, then your page will be ready to deliver in about 7 seconds. If you run them in parallel then you will have your page served in about 5 seconds. With `RabbitMqBundle` we can do such parallel calls with ease. Let's define a parallel client in the config and another RPC server:
 
 ```yaml
 rpc_clients:
@@ -941,7 +941,7 @@ batch_consumers:
 
 *Note*: If the `keep_alive` option is set to `true`, `idle_timeout_exit_code` will be ignored and the consumer process continues.
 
-You can implement a batch consumer that will acknowledge all messages in one return or you can have control on what message to acknoledge.
+You can implement a batch consumer that will acknowledge all messages in one return or you can have control on what message to acknowledge.
 
 ```php
 namespace AppBundle\Service;
@@ -1013,9 +1013,8 @@ How to run the following batch consumer:
     $ ./bin/console rabbitmq:batch:consumer batch_basic_consumer -w
 ```
 
-Important: BatchConsumers will not have the -m|messages option available
-Important: BatchConsumers can also have the -b|batches option available if you want to only consume a specific number of batches and then stop the consumer.
-! Give the number of the batches only if you want the consumer to stop after those batch messages were consumed.! 
+Important: BatchConsumers will not have the `-m|messages` option available
+Important: BatchConsumers can also have the `-b|batches` option available if you want to only consume a specific number of batches and then stop the consumer. Give the number of the batches only if you want the consumer to stop after those batch messages were consumed!
 
 ### STDIN Producer ###