Merge pull request #304 from alexpunct/patch-1

Update async-topics.md

Author: dshevtsov

src/pages/development/components/message-queues/async-topics.md

@@ -36,11 +36,11 @@ Sort order is set to 0 by default. This allows developers to change some aspects
 
 `\Magento\Framework\Communication\Config\CompositeReader::read()` collects configuration records from defined readers and merges these records into a single configurataion.
 
-Because the generation of thge topics configuration is based on schema type, the generated `<topic>` XML is returned with `"sync"=true`. The `response` attribut is based on the service response definition. So the `WebapiAsync` module changes those settings to `"sync"=false` and `response` is set to null. These changes will allow the application to execute topics asynchronously.
+Because the generation of the topics configuration is based on schema type, the generated `<topic>` XML is returned with `"sync"=true`. The `response` attribute is based on the service response definition. So the `WebapiAsync` module changes those settings to `"sync"=false` and `response` is set to null. These changes will allow the application to execute topics asynchronously.
 
 ## Topics generation
 
-Asynchronous and Bulk APIs are built on top of the standard Rest API. Topics for message processing fo asynchronous and bulk APIs are generated automatically, together with the `communication.xml` schema. This is done by `\Magento\WebapiAsync\Model\Config::getServices()`. The current method is responsible for retrieving all service contracts defined in `webapi.xml` files and generates topic names for the corresponding asynchronous requests.
+Asynchronous and Bulk APIs are built on top of the standard Rest API. Topics for message processing for asynchronous and bulk APIs are generated automatically, together with the `communication.xml` schema. This is done by `\Magento\WebapiAsync\Model\Config::getServices()`. The current method is responsible for retrieving all service contracts defined in `webapi.xml` files and generates topic names for the corresponding asynchronous requests.
 
 `generateTopicNameFromService($serviceInterface, $serviceMethod, $httpMethod)` is responsible for generating a topic name based on the service contract interface, the service contract method, and the HTTP method.
 
@@ -66,4 +66,4 @@ It consists of following parts:
 *  lower cased service method
 *  lover cased http method
 
-Unfortunately, there are no easy way to get a list of all generated topic names, but knowing this pattern, developers can find the required topic name and use it for executing service contracts in asynchronously.
+Unfortunately, there is no easy way to get a list of all generated topic names, but knowing this pattern, developers can find the required topic name and use it for executing service contracts in asynchronously.