Feedback

Author: baanders

articles/digital-twins/how-to-manage-routes.md

@@ -28,7 +28,7 @@ In Azure Digital Twins, you can route [event notifications](concepts-event-notif
     - Instance name
     - Resource group
 
-You can find these details in the [Azure portal](https://portal.azure.com) after setting up your instance. Log into the portal and search for the name of your instance in the portal search bar.
+You can find these details in the [Azure portal](https://portal.azure.com) after setting up your instance. Log in to the portal and search for the name of your instance in the portal search bar.
 
 :::image type="content" source="media/how-to-manage-routes/search-field-portal.png" alt-text="Screenshot of Azure portal search bar." lightbox="media/how-to-manage-routes/search-field-portal.png":::
 
@@ -99,7 +99,7 @@ If the endpoint creation fails, observe the error message and retry after a few
 
 You can also view the endpoint that was created back on the **Endpoints** page for your Azure Digital Twins instance.
 
-Now the event grid, event hub, or Service Bus topic is available as an endpoint in Azure Digital Twins, under the name you chose for the endpoint. You'll typically use that name as the target of an event route, which you'll create [later in this article](#create-an-event-route).
+Now the Event Grid topic, event hub, or Service Bus topic is available as an endpoint in Azure Digital Twins, under the name you chose for the endpoint. You'll typically use that name as the target of an event route, which you'll create [later in this article](#create-an-event-route).
 
 # [CLI](#tab/cli) 
 
@@ -121,7 +121,7 @@ To create a Service Bus topic endpoint (key-based authentication):
 az dt endpoint create servicebus --endpoint-name <Service-Bus-endpoint-name> --servicebus-resource-group <Service-Bus-resource-group-name> --servicebus-namespace <Service-Bus-namespace> --servicebus-topic <Service-Bus-topic-name> --servicebus-policy <Service-Bus-topic-policy> --dt-name <your-Azure-Digital-Twins-instance-name>
 ```
 
-After successfully running these commands, the event grid, event hub, or Service Bus topic will be available as an endpoint in Azure Digital Twins, under the name you supplied with the `--endpoint-name` argument. You'll typically use that name as the target of an event route, which you'll create [later in this article](#create-an-event-route).
+After successfully running these commands, the Event Grid topic, event hub, or Service Bus topic will be available as an endpoint in Azure Digital Twins, under the name you supplied with the `--endpoint-name` argument. You'll typically use that name as the target of an event route, which you'll create [later in this article](#create-an-event-route).
 
 #### Create an endpoint with identity-based authentication
 
@@ -206,7 +206,7 @@ For instructions on how to create this type of endpoint with the Azure CLI, swit
 
 To create an endpoint that has dead-lettering enabled, add the `--deadletter-sas-uri` parameter to the [az dt endpoint create](/cli/azure/dt/endpoint/create) command that [creates an endpoint](#create-the-endpoint).
 
-The value for the parameter is the dead letter SAS URI made up of the storage account name, container name, and SAS token that you gathered in the [previous section](#set-up-storage-resources). This parameter creates the endpoint with key-based authentication. Here is what the parameter looks like:
+The value for the parameter is the dead letter SAS URI made up of the storage account name, container name, and SAS token that you gathered in the [previous section](#set-up-storage-resources). This parameter creates the endpoint with key-based authentication. Here's what the parameter looks like:
 
 ```azurecli
 --deadletter-sas-uri https://<storage-account-name>.blob.core.windows.net/<container-name>?<SAS-token>
@@ -323,7 +323,7 @@ The following sample method shows how to create, list, and delete an event route
 
 As described above, routes have a filter field. If the filter value on your route is `false`, no events will be sent to your endpoint. 
 
-After enabling the minimal filter of `true`, endpoints will receive different kinds of events from Azure Digital Twins:
+After you've enabled a minimal filter of `true`, endpoints will receive different kinds of events from Azure Digital Twins:
 * Telemetry fired by [digital twins](concepts-twins-graph.md) using the Azure Digital Twins service API
 * Twin property change notifications, fired on property changes for any twin in the Azure Digital Twins instance
 * Life-cycle events, fired when twins or relationships are created or deleted

articles/digital-twins/how-to-use-azure-digital-twins-explorer.md

@@ -141,7 +141,7 @@ There are two possible error scenarios that each give their own error message:
 
 Both of these error messages are shown in the screenshot below:
 
-:::image type="content" source="media/how-to-use-azure-digital-twins-explorer/properties-errors.png" alt-text="Screenshot of Azure Digital Twins Explorer Twin Properties panel, showing two error messages. One error indicates that models are missing, and the other indicates that properties are missing a model. " lightbox="media/how-to-use-azure-digital-twins-explorer/properties-errors-large.png":::
+:::image type="content" source="media/how-to-use-azure-digital-twins-explorer/properties-errors.png" alt-text="Screenshot of Azure Digital Twins Explorer Twin Properties panel, showing two error messages. One error indicates that models are missing, and the other indicates that properties are missing a model." lightbox="media/how-to-use-azure-digital-twins-explorer/properties-errors-large.png":::
 
 #### View a twin's relationships