Changelog and some other documentation fixes.

Author: Anton Vorontsov

docs/changelog.md

@@ -2,11 +2,12 @@
 
 All notable changes to this library will be documented in this file.
 
-## [4.2.0] - will be drafted
+## [4.2.0] - 2020-10-01
 
 ### Added
 
 - Options that can allow configuring behaviour of re-queueing messages. New properties `RequeueTimeoutMilliseconds` and `RequeueAttempts` added to `RabbitMqExchangeOptions`.
+- `MessageHandlingPeriod` property for batch message handlers. That feature allows you to execute even unfilled batches each time period expires.
 
 ### Changed
 

docs/message-consumption.md

@@ -317,7 +317,7 @@ The message handling process organized as follows:
 There are also a feature that you can use in case of necessity of handling messages in batches.
 First of all you have to create a class that inherits a `BatchMessageHandler` class.
 You have to set up values for `QueueName` and `PrefetchCount` properties. These values are responsible for the queue that will be read by the message handler, and the size of batches of messages. You can also set a `MessageHandlingPeriod` property value and the method `HandleMessage` will be executed repeatedly so messages in unfilled batches could be processed too, but keep in mind that this property is optional.
-Be aware that batch message handlers *do not declare queues*, so if it does not exist an exception will be thrown. Either declare manually or using RabbitMqClient configuration features.
+Be aware that batch message handlers **do not declare queues**, so if it does not exist an exception will be thrown. Either declare manually or using RabbitMqClient configuration features.
 
 ```c#
 public class CustomBatchMessageHandler : BatchMessageHandler

docs/message-production.md

@@ -118,7 +118,7 @@ The image below shows a model of the whole process of passing the message from t
 
 **Prerequisites.** Let's say that producer want to send a message to the exchange **"Exchange B"** with a routing key **"routing.key"**, and a delay in **30 milliseconds**.
  - Message goes to the exchange **"Exchange A"** whose responsibility is to manage delaying (storing) the message.
- - After that a queue with a compound name and special arguments is being created. Name consists of three parts: the routing key of the sent message, a word "delayed", and a number of delay milliseconds .
+ - After that a queue with a compound name and special arguments will be created. Name consists of three parts: the routing key of the message that has been sent, a word "delayed", and a number of delay milliseconds.
 Queue arguments are as follows.
 ```
 x-dead-letter-exchange : Exchange В

docs/rabbit-configuration.md

@@ -224,7 +224,7 @@ Map that configuration using standard `GetSection` method.
 var rabbitMqConfiguration = Configuration.GetSection("RabbitMq");
 ```
 
-And pass it to the `AddRabbitMqClient` extension method as always.
+Pass it to the `AddRabbitMqClient` extension method as always.
 
 ```c#
 services.AddRabbitMqClient(rabbitMqConfiguration);

src/RabbitMQ.Client.Core.DependencyInjection/RabbitMQ.Client.Core.DependencyInjection.csproj

@@ -3,7 +3,7 @@
   <PropertyGroup>
     <TargetFramework>netstandard2.1</TargetFramework>
     <LangVersion>latest</LangVersion>
-    <Version>4.1.1</Version>
+    <Version>4.2.0</Version>
     <PackageTags>RabbitMQ</PackageTags>
     <RepositoryUrl>https://github.com/AntonyVorontsov/RabbitMQ.Client.Core.DependencyInjection</RepositoryUrl>
     <RepositoryType>GIT</RepositoryType>