Merge pull request #8521 from magento/hg-typos

Address typos

Author: hguthrie

src/cloud/project/user-admin.md

@@ -259,7 +259,7 @@ To enable TFA on your {{site.data.var.ece}} user account:
 
    -  Log in with your username and password.
 
-   -  When prompted, enter the two-factor authentication code for the magento.cloufrom the authenticator application on your mobile device
+   -  When prompted, enter the two-factor authentication code for the `accounts.magento.cloud` entry from the authenticator application on your mobile device.
 
 ### Manage TFA configuration and recovery codes
 

src/guides/v2.3/extension-dev-guide/cache/page-caching/private-content.md

@@ -67,7 +67,7 @@ Customer sections was designed to cache private data in browser storage. This me
 The are some exception cases:
 
 -  Store and website switching, after any of these action customer section `cart` will be updated.
--  Customer cart lifetime option `section_data_lifetime` which is 60 minutes by default. After scheduled time passe section `cart` will be updated.
+-  Customer cart lifetime option `section_data_lifetime` which is 60 minutes by default. After scheduled time passes, section `cart` will be updated.
 
 {: .bs-callout-info }
 Product information will not be simultaneously updated in customer cart (product name, price, product enabled/disabled). Information will be updated after what comes first: `section_data_lifetime` time passed or an action that the update cart triggered.

src/guides/v2.3/extension-dev-guide/message-queues/async-message-queue-config-files.md

@@ -16,20 +16,20 @@ When using the Magento message queue, four configuration files in your module mu
 
 More information can be found in [Configure message queues]({{ page.baseurl }}/extension-dev-guide/message-queues/config-mq.html).
 
-Asynchronous and Bulk APIs are built on top of the usual REST API and use the Magento Message Queue Framework for processing messages. To easy development efforts, the Asynchronous API pre-generates the following configuration files:
+Asynchronous and Bulk APIs are built on top of the usual REST API and use the Magento Message Queue Framework for processing messages. To ease development efforts, the Asynchronous API pre-generates the following configuration files:
 
 *  communication.xml
 *  queue_publisher.xml
 
-and provides the `queue_topology.xml` and `queue_consumer.xml` file within the `Magento/WebapiAsync` module.
+and provides the `queue_topology.xml` and `queue_consumer.xml` files within the `Magento/WebapiAsync` module.
 
 ### communication.xml
 
 Information about the auto-generation of `communication.xml` can be found in [Topics in Asynchronous API]({{ page.baseurl }}/extension-dev-guide/message-queues/async-topics.html)
 
 ### queue_publisher.xml
 
-`queue_publisher.xml` is generated by the `\Magento\WebapiAsync\Code\Generator\Config\RemoteServiceReader\Publisher` class, which implements `\Magento\Framework\Config\ReaderInterface` and is injected into the `\Magento\Framework\MessageQueue\Publisher\Config\CompositeReader` constructor argument in the main `di.xml` file.
+The `queue_publisher.xml` file is generated by the `\Magento\WebapiAsync\Code\Generator\Config\RemoteServiceReader\Publisher` class, which implements `\Magento\Framework\Config\ReaderInterface` and is injected into the `\Magento\Framework\MessageQueue\Publisher\Config\CompositeReader` constructor argument in the main `di.xml` file.
 
 ```xml
 <type name="Magento\Framework\MessageQueue\Publisher\Config\CompositeReader">
@@ -57,7 +57,7 @@ The asynchronous/bulk API has one defined consumer which processes all asynchron
 
 ### queue_topology.xml
 
-The nessage queue topology configuration links all auto-generated topic names with prefix `async.` to the `magento` exchange and defines the queue named `async.operations.all` as the destination for all messages.
+The message queue topology configuration links all auto-generated topic names with prefix `async.` to the `magento` exchange and defines the queue named `async.operations.all` as the destination for all messages.
 
 ```xml
 <exchange name="magento" type="topic" connection="amqp">