edit pass: digital-twins-tutorials

Author: ShawnJackson

articles/digital-twins/tutorial-facilities-analyze.md

@@ -56,7 +56,7 @@ You can use the [Event Hubs](../event-hubs/event-hubs-about.md) service to creat
 
 1. Enter a **Name** for your event hub, and select **Create**. 
 
-   After the event hub is deployed, it will appear in the **Event Hubs** pane of the Event Hubs namespace with an **Active** status. Select this event hub to open its **Overview** pane.
+   After the event hub is deployed, it appears in the **Event Hubs** pane of the Event Hubs namespace with an **Active** status. Select this event hub to open its **Overview** pane.
 
 1. Select the **Consumer group** button at the top, and enter a name such as **tsievents** for the consumer group. Select **Create**.
     ![Event Hub consumer group](./media/tutorial-facilities-analyze/event-hub-consumer-group.png)
@@ -161,7 +161,7 @@ If you want to stop exploring Azure Digital Twins beyond this point, feel free t
 
 ## Next steps
 
-Proceed to the next article to learn more about spatial intelligence graphs and object models in Azure Digital Twins. 
+Go to the next article to learn more about spatial intelligence graphs and object models in Azure Digital Twins. 
 > [!div class="nextstepaction"]
 > [Understanding Digital Twins object models and spatial intelligence graph](concepts-objectmodel-spatialgraph.md)
 

articles/digital-twins/tutorial-facilities-events.md

@@ -14,7 +14,9 @@ ms.author: dkshir
 
 After you deploy your Azure Digital Twins instance, provision your spaces, and implement custom functions to monitor specific conditions, you can notify your office admin via email when the monitored conditions occur. 
 
-In [the first tutorial](tutorial-facilities-setup.md), you configured the spatial graph of an imaginary building. A room in the building contains sensors for motion, carbon dioxide, and temperature. In [the second tutorial](tutorial-facilities-udf.md), you provisioned your graph and a user-defined function to monitor these sensor values and trigger notifications when the room is empty, and the temperature and carbon dioxide are in a comfortable range. This tutorial shows how you can integrate these notifications with Azure Logic Apps to send emails when such a room is available. An office administrator can use this information to help the employees book the most productive meeting room. 
+In [the first tutorial](tutorial-facilities-setup.md), you configured the spatial graph of an imaginary building. A room in the building contains sensors for motion, carbon dioxide, and temperature. In [the second tutorial](tutorial-facilities-udf.md), you provisioned your graph and a user-defined function to monitor these sensor values and trigger notifications when the room is empty, and the temperature and carbon dioxide are in a comfortable range. 
+
+This tutorial shows how you can integrate these notifications with Azure Logic Apps to send emails when such a room is available. An office administrator can use this information to help the employees book the most productive meeting room. 
 
 In this tutorial, you learn how to:
 
@@ -32,10 +34,10 @@ This tutorial assumes that you have [configured](tutorial-facilities-setup.md) a
 - An Office 365 account to send notification e-mails.
 
 ## Integrate events with Event Grid 
-In this section, you set up [Event Grid](../event-grid/overview.md) to collect events from your Digital Twins instance, and redirect them to an [event handler](../event-grid/event-handlers.md) such as Logic Apps.
+In this section, you set up [Event Grid](../event-grid/overview.md) to collect events from your Azure Digital Twins instance, and redirect them to an [event handler](../event-grid/event-handlers.md) such as Logic Apps.
 
-### Create an Event Grid topic
-An [Event Grid topic](../event-grid/concepts.md#topics) provides an interface to route the events generated by the user-defined function. 
+### Create an event grid topic
+An [event grid topic](../event-grid/concepts.md#topics) provides an interface to route the events generated by the user-defined function. 
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 
@@ -45,15 +47,15 @@ An [Event Grid topic](../event-grid/concepts.md#topics) provides an interface to
 
 1. Enter a **Name** for your event grid topic, and choose the **Subscription**. Select the **Resource group** that you used or created for your Digital Twins instance, and the **Location**. Select **Create**. 
 
-    ![Create an Event Grid topic](./media/tutorial-facilities-events/create-event-grid-topic.png)
+    ![Create an event grid topic](./media/tutorial-facilities-events/create-event-grid-topic.png)
 
-1. Browse to the Event Grid topic from your resource group, select **Overview**, and copy the value for **Topic Endpoint** to a temporary file. You'll need this URL in the next section. 
+1. Browse to the event grid topic from your resource group, select **Overview**, and copy the value for **Topic Endpoint** to a temporary file. You'll need this URL in the next section. 
 
 1. Select **Access keys**, and copy **Key 1** and **Key 2** to a temporary file. You'll need these values to create the endpoint in the next section.
 
     ![Event Grid keys](./media/tutorial-facilities-events/event-grid-keys.png)
 
-### Create an endpoint for the Event Grid topic
+### Create an endpoint for the event grid topic
 
 1. In the command window, make sure you're in the **occupancy-quickstart\src** folder of the Digital Twins sample.
 
@@ -75,7 +77,7 @@ An [Event Grid topic](../event-grid/concepts.md#topics) provides an interface to
 
 1. Replace the placeholder `Secondary_connection_string_for_your_Event_Grid` with the value of **Key2**.
 
-1. Replace the placeholder `Event_Grid_Topic_Path` with the path of the Event Grid topic. Get this path by removing **https://** and the trailing resource paths from the **Topic Endpoint** URL. It should look similar to this format: *yourEventGridName.yourLocation.eventgrid.azure.net*. 
+1. Replace the placeholder `Event_Grid_Topic_Path` with the path of the event grid topic. Get this path by removing **https://** and the trailing resource paths from the **Topic Endpoint** URL. It should look similar to this format: *yourEventGridName.yourLocation.eventgrid.azure.net*. 
 
     > [!IMPORTANT]
     > Enter all values without any quotes. Make sure there's at least one space character after the colons in the YAML file. You can also validate your YAML file contents by using any online YAML validator such as [this tool](https://onlineyamltools.com/validate-yaml).
@@ -92,7 +94,7 @@ An [Event Grid topic](../event-grid/concepts.md#topics) provides an interface to
 
 
 ## Notify events with Logic Apps
-You can use the [Azure Logic Apps](../logic-apps/logic-apps-overview.md) service to create automated tasks for events received from other services. In this section, you set up Logic Apps to create email notifications for events routed from your spatial sensors, with the help of an [Event Grid topic](../event-grid/overview.md).
+You can use the [Azure Logic Apps](../logic-apps/logic-apps-overview.md) service to create automated tasks for events received from other services. In this section, you set up Logic Apps to create email notifications for events routed from your spatial sensors, with the help of an [event grid topic](../event-grid/overview.md).
 
 1. In the left pane of the [Azure portal](https://portal.azure.com), select **Create a resource**.
 
@@ -104,11 +106,11 @@ You can use the [Azure Logic Apps](../logic-apps/logic-apps-overview.md) service
 
 1. Open your Logic Apps resource when it's deployed, and then open the **Logic App Designer** pane. 
 
-1. Select the **When an Event Grid event occurs** trigger. Sign in to your tenant with your Azure account when prompted. Select **Allow access** to your Event Grid when prompted. Select **Continue**.
+1. Select the **When an Event Grid event occurs** trigger. Sign in to your tenant with your Azure account when prompted. Select **Allow access** for your Event Grid resource when prompted. Select **Continue**.
 
 1. In the **When a resource event occurs (Preview)** window: 
 
-   a. Select the **Subscription** that you used to create the Event Grid topic.
+   a. Select the **Subscription** that you used to create the event grid topic.
 
    b. Select **Microsoft.EventGrid.Topics** for **Resource Type**.
 
@@ -193,7 +195,7 @@ If you want to stop exploring Azure Digital Twins at this point, feel free to de
 
 ## Next steps
 
-To learn how to visualize your sensor data, analyze trends, and spot anomalies, proceed to the next tutorial: 
+To learn how to visualize your sensor data, analyze trends, and spot anomalies, go to the next tutorial: 
 > [!div class="nextstepaction"]
 > [Tutorial: Visualize and analyze events from your Azure Digital Twins spaces using Time Series Insights](tutorial-facilities-analyze.md)
 

articles/digital-twins/tutorial-facilities-setup.md

@@ -19,7 +19,7 @@ These tutorials will walk you through a .NET console application to build a scen
 
 You'll learn how to replicate the physical areas and entities in the building as digital objects by using the Azure Digital Twins service. You'll simulate device events by using another console application. Then, you'll learn how to monitor the events that come from these physical areas and entities in near real time. 
 
-An office administrator can use this information to help an employee working in this building to book meeting rooms with optimal conditions. An office facilities manager can use your setup to find out usage trends of the rooms, as well as monitor working conditions for maintenance purposes.
+An office administrator can use this information to help an employee working in this building to book meeting rooms with optimal conditions. An office facilities manager can use your setup to get usage trends of the rooms, and to monitor working conditions for maintenance purposes.
 
 In the first tutorial of this series, you learn how to:
 
@@ -37,7 +37,7 @@ These tutorials use and modify the same samples that the [quickstart to find ava
 
 - An Azure subscription. If you don’t have an Azure account, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 
-- The right SDK. The Azure Digital Twins samples used in these tutorials are written in C#. Make sure to install [.NET Core SDK version 2.1.403 or later](https://www.microsoft.com/net/download) on your development machine to build and run the sample. Check if the right version is installed on your machine by running `dotnet --version` in a command window.
+- The right SDK. The Azure Digital Twins samples used in these tutorials are written in C#. Make sure to install [.NET Core SDK version 2.1.403 or later](https://www.microsoft.com/net/download) on your development machine to build and run the sample. Check that the right version is installed on your machine by running `dotnet --version` in a command window.
 
 - [Visual Studio Code](https://code.visualstudio.com/) to explore the sample code. 
 
@@ -76,13 +76,13 @@ In the extracted sample folder, open the file **digital-twins-samples-csharp\dig
 
 * You can use the provisioning sample **occupancy-quickstart** to configure and provision a [spatial intelligence graph](concepts-objectmodel-spatialgraph.md#graph). This graph is the digitized image of your physical spaces and the resources in them. It uses an [object model](concepts-objectmodel-spatialgraph.md#model), which defines objects for a smart building. For a complete list of Digital Twins objects and REST APIs, visit [this REST API documentation](https://docs.westcentralus.azuresmartspaces.net/management/swagger) or the Management API URL that was created for [your instance](#deploy).
 
-   To explore the sample to see how it communicates with your Digital Twins instance, you can start with the **src\actions** folder. The files in this folder implement the commands that you will use in these tutorials:
+   To explore the sample to see how it communicates with your Digital Twins instance, you can start with the **src\actions** folder. The files in this folder implement the commands that you'll use in these tutorials:
     - The **provisionSample.cs** file shows how to provision your spatial graph.
     - The **getSpaces.cs** file gets information about the provisioned spaces.
     - The **getAvailableAndFreshSpaces.cs** file gets the results of a custom function called a user-defined function.
     - The **createEndpoints.cs** file creates endpoints to interact with other services.
 
-* The simulation sample **device-connectivity** simulates sensor data and sends it to the IoT hub that's provisioned for your Digital Twins instance. You'll use this sample in [the next tutorial after you have provisioned your spatial graph](tutorial-facilities-udf.md#simulate). The sensor and device identifiers that you use to configure this sample should be the same as what you'll use to provision your graph.
+* The simulation sample **device-connectivity** simulates sensor data and sends it to the IoT hub that's provisioned for your Digital Twins instance. You'll use this sample in [the next tutorial after you provision your spatial graph](tutorial-facilities-udf.md#simulate). The sensor and device identifiers that you use to configure this sample should be the same as what you'll use to provision your graph.
 
 ### Configure the provisioning sample
 1. Open a command window and go to the downloaded sample. Run the following command:
@@ -100,7 +100,7 @@ In the extracted sample folder, open the file **digital-twins-samples-csharp\dig
 1. In Visual Studio Code, open the **appSettings.json** file in the **occupancy-quickstart** project. Update the following values:
    * **ClientId**: Enter the application ID of your Azure AD app registration. You noted this ID in the section where you [set app permissions](#permissions).
    * **Tenant**: Enter the directory ID of your [Azure AD tenant](https://docs.microsoft.com/azure/active-directory/develop/quickstart-create-new-tenant). You also noted this ID in the section where you [set app permissions](#permissions).
-   * **BaseUrl**: Enter the URL of your Digital Twins instance. To get this URL, replace the placeholders in this URL with values for your instance: **_https://yourDigitalTwinsName.yourLocation.azuresmartspaces.net/management/api/v1.0/_**. You can also get this URL by modifying the Management API URL from [the deployment section](#deploy). Replace **swagger/** with **api/v1.0/**.
+   * **BaseUrl**: Enter the URL of your Digital Twins instance. To get this URL, replace the placeholders in this URL with values for your instance: _https://yourDigitalTwinsName.yourLocation.azuresmartspaces.net/management/api/v1.0/_. You can also get this URL by modifying the Management API URL from [the deployment section](#deploy). Replace **swagger/** with **api/v1.0/**.
 
 1. See a list of Digital Twins features that you can explore by using the sample. Run the following command:
 
@@ -150,14 +150,14 @@ The **provisionSample.yaml** file contains the following nodes:
 
 - **devices**: Spaces can contain `devices`, which are physical or virtual entities that manage a number of sensors. For example, a device might be a user’s phone, a Raspberry Pi sensor pod, or a gateway. In the imaginary building in your sample, note how the room named **Focus Room** contains a **Raspberry Pi 3 A1** device. Each device node is identified by a unique `hardwareId`, which is hardcoded in the sample. To configure this sample for an actual production, replace these with values from your setup.  
 
-- **sensors**: A device can contain multiple `sensors`. They can detect and record physical changes like temperature, motion, and battery level. Each sensor node is uniquely identified by a `hardwareId`, hardcoded here. For an actual application, replace these by using the unique identifiers of the sensors in your setup. The provisionSample.yaml file has two sensors to record *Motion* and *CarbonDioxide*. Add another sensor to record *Temperature*, by adding the following lines, below the lines for the CarbonDioxide sensor. Note that these are provided in provisionSample.yaml as commented-out lines. You can simply uncomment them by removing the `#` character in the front of each line. 
+- **sensors**: A device can contain multiple `sensors`. They can detect and record physical changes like temperature, motion, and battery level. Each sensor node is uniquely identified by a `hardwareId`, hardcoded here. For an actual application, replace these by using the unique identifiers of the sensors in your setup. The provisionSample.yaml file has two sensors to record *Motion* and *CarbonDioxide*. Add another sensor to record *Temperature*, by adding the following lines, below the lines for the CarbonDioxide sensor. Note that these are provided in provisionSample.yaml as commented-out lines. You can uncomment them by removing the `#` character in the front of each line. 
 
     ```yaml
             - dataType: Temperature
               hardwareId: SAMPLE_SENSOR_TEMPERATURE
     ```
     > [!NOTE]
-    > Make sure the alignment of the `dataType` and `hardwareId` keys align with the statements above this snippet. Also make sure that your editor does not replace spaces with tabs. 
+    > Make sure the `dataType` and `hardwareId` keys align with the statements above this snippet. Also make sure that your editor does not replace spaces with tabs. 
 
 Save and close the provisionSample.yaml file. In the next tutorial, you'll add more information to this file, and then provision your Azure Digital Twins sample building.
 
@@ -172,7 +172,7 @@ If you want to stop exploring Azure Digital Twins at this point, feel free to de
 
 ## Next steps
 
-To learn how to implement a custom logic to monitor conditions in your sample building, proceed to the next tutorial in the series: 
+To learn how to implement a custom logic to monitor conditions in your sample building, go to the next tutorial in the series: 
 > [!div class="nextstepaction"]
 > [Tutorial: Provision your building and monitor working conditions](tutorial-facilities-udf.md)