Typos fix

Author: dabrt

docs/discounts/configure_discounts.md

@@ -36,7 +36,7 @@ Discounts feature uses [[= product_name_base =]] Messenger to reindex discounts
 This way changes are processed efficiently without slowing down the system and disrupting the user experience.
 
 When triggered periodically, the `ibexa:discounts:reindex` command identifies discounts that require re-indexing, ensuring catalog prices always remain up-to-date.
-If there are edits to discounts that should result in changed product catalog prices, messages are dispatched to an [[= product_name_base =]] Messenger queue and consumed by a background worker.
+If there are edits to discounts that should result in changed product catalog prices, messages are dispatched to the [[= product_name_base =]] Messenger's queue and consumed by a background worker.
 The worker passes the messages to the handler, which then starts the re-indexing process at the most convenient moment.
 
 To use discount re-indexing in the background:
@@ -49,7 +49,7 @@ To use discount re-indexing in the background:
 php bin/console messenger:consume ibexa.messenger.transport --bus=ibexa.messenger.bus
 ```
 
-3\. Use a scheduler of your choice, to periodically run the following command:
+3\. Use a scheduler of your choice to periodically run the following command:
 
 ``` bash
 php bin/console ibexa:discounts:reindex

docs/discounts/discounts_guide.md

@@ -116,7 +116,7 @@ You can also limit the usage per customer:
 ### Discount re-indexing
 
 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 search results and product listings display the correct price.
+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.
 

docs/infrastructure_and_maintenance/background_tasks.md

@@ -24,7 +24,7 @@ The process works as follows:
 2. The message is wrapped in an envelope, which may contain additional metadata, called stamps, for example, `DeduplicateStamp`.
 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 ontinuously reads messages from the queue, pulls them into the default bus `ibexa.messenger.bus` and assigns them to the right haandler.
+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).
 You can register multiple handlers for different jobs.
 
@@ -54,7 +54,7 @@ ibexa_messenger:
 
 !!! note "Supported transports"
 
-    You can define different transports, such as Redis or PostgeSQL.
+    You can define different transports, such as Redis or 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