Typos

Author: dabrt

docs/discounts/configure_discounts.md

@@ -41,7 +41,7 @@ The worker passes the messages to the handler, which then starts the re-indexing
 
 To use discount re-indexing in the background:
 
-1\. Make sure that the transport layer is [defined properly](background_tasks.md#configure-package) in Messenger configuration.
+1\. Make sure that the transport layer is [defined properly](background_tasks.md#configure-package) in [[= product_name_base =]] Messenger configuration.
 
 2\. Make sure that the worker starts together with the application to watch the transport bus:
 

docs/discounts/discounts_guide.md

@@ -118,9 +118,9 @@ You can also limit the usage per customer:
 Discounts affect the prices shown in the product catalog.
 When a discount is created, updated, or expires, the product catalog must be re-indexed to ensure that the search results and product listings display correct prices.
 
-To prevent performance disruptions which could occur if re-indexing occurred immediately, [[= product_name =]] uses the [Ibexa Messenger](background_tasks.md)'s background queue to process re-indexing tasks in the background.
+To prevent performance disruptions which could occur if re-indexing occurred immediately, [[= product_name =]] uses the [[= product_name_base =]] Messenger's [background queue](background_tasks.md) to process re-indexing tasks in the background.
 
-By [configuring the process](configure_discounts.md#discount-re-indexing), you can decide when is the most convenient time to perform re-indexing and improve your application's overall stability.
+By [configuring the process](configure_discounts.md#discount-re-indexing), you ensure that re-indexing is performed at the most convenient time to maintain your application's overall stability.
 
 ## Capabilities
 

docs/infrastructure_and_maintenance/background_tasks.md

@@ -25,7 +25,7 @@ The process works as follows:
 3. The message is placed in the transport queue.
 It can be a Doctrine table, a Redis queue, and so on.
 4. A worker process continuously reads messages from the queue, pulls them into the default bus `ibexa.messenger.bus` and assigns them to the right handler.
-5. Handler service processes the message (executes the command).
+5. A handler service processes the message (executes the command).
 You can register multiple handlers for different jobs.
 
 Here is an example of how you can extend your code and use [[= product_name_base =]] Messenger to process your tasks:
@@ -54,7 +54,7 @@ ibexa_messenger:
 
 !!! note "Supported transports"
 
-    You can define different transports, such as Redis or PostgreSQL.
+    You can define different transports: [[= product_name_base =]] Messenger has been tested to work with Redis, MySQL, PostgreSQL.
     For more information, see [Symfony Messenger documentation](https://symfony.com/doc/current/messenger.html#transports-async-queued-messages) or [Symfony Messenger tutorial](https://symfonycasts.com/screencast/messenger/install#installing-messenger).
 
 ### Start worker