metadata added and merged

Author: KingdomOfEnds

articles/digital-twins/media/tutorial-facilities-events/logic-app-send-email.png

@@ -8,6 +8,7 @@ ms.service: digital-twins
 ms.topic: tutorial 
 ms.date: 09/17/2019
 ms.author: alinast
+#Customer intent: As an Azure IoT developer, I want to walk through a sample application to learn how to analyze events from an Azure Digital Twins instance. 
 ---
 
 # Tutorial: Visualize and analyze events from your Azure Digital Twins spaces by using Time Series Insights

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

@@ -8,6 +8,7 @@ ms.service: digital-twins
 ms.topic: tutorial 
 ms.date: 09/17/2019
 ms.author: alinast
+#Customer intent: As an Azure IoT developer, I want to walk through a sample application to learn how to capture events from a Azure Digital Twins space. 
 ---
 
 # Tutorial: Receive notifications from your Azure Digital Twins spaces by using Logic Apps

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

@@ -6,8 +6,9 @@ author: alinamstanciu
 ms.custom: seodec18
 ms.service: digital-twins
 ms.topic: tutorial 
-ms.date: 09/17/2019
+ms.date: 09/20/2019
 ms.author: alinast
+#Customer intent: As an Azure IoT developer, I want to walk through a sample application to monitor a space using Azure Digital Twins. 
 ---
 
 # Tutorial: Provision your building and monitor working conditions with Azure Digital Twins Preview
@@ -51,17 +52,17 @@ This matcher will track the `SAMPLE_SENSOR_TEMPERATURE` sensor that you added in
 
 You can use user-defined functions to customize the processing of your sensor data. They're custom JavaScript code that can run within your Azure Digital Twins instance, when specific conditions as described by the matchers occur. You can create matchers and user-defined functions for each sensor that you want to monitor. For more information, read [Data processing and user-defined functions](concepts-user-defined-functions.md). 
 
-In the sample `provisionSample.yaml` file, look for a section that begins with the type **userdefinedfunctions**. This section provisions a user-defined function with a given **Name**. This UDF acts on the list of matchers under **matcherNames**. Notice how you can provide your own JavaScript file for the UDF as the **script**.
+In the sample *provisionSample.yaml* file, look for a section that begins with the type **userdefinedfunctions**. This section provisions a user-defined function with a given **Name**. This UDF acts on the list of matchers under **matcherNames**. Notice how you can provide your own JavaScript file for the UDF as the **script**.
 
 Also note the section named **roleassignments**. It assigns the Space Administrator role to the user-defined function. This role allows it to access the events that come from any of the provisioned spaces. 
 
-1. Configure the UDF to include the temperature matcher by adding or uncommenting the following line in the `matcherNames` node of the `provisionSample.yaml` file:
+1. Configure the UDF to include the temperature matcher by adding or uncommenting the following line in the `matcherNames` node of the *provisionSample.yaml* file:
 
     ```yaml
             - Matcher Temperature
     ```
 
-1. Open the file **src\actions\userDefinedFunctions\availability.js** in your editor. This is the file referenced in the **script** element of `provisionSample.yaml`. The user-defined function in this file looks for conditions when no motion is detected in the room and carbon dioxide levels are below 1,000 ppm. 
+1. Open the file **src\actions\userDefinedFunctions\availability.js** in your editor. This is the file referenced in the **script** element of *provisionSample.yaml*. The user-defined function in this file looks for conditions when no motion is detected in the room and carbon dioxide levels are below 1,000 ppm. 
 
    Modify the JavaScript file to monitor temperature and other conditions. Add the following lines of code to look for conditions when no motion is detected in the room, carbon dioxide levels are below 1,000 ppm, and temperature is below 78 degrees Fahrenheit.
 
@@ -172,7 +173,7 @@ Also note the section named **roleassignments**. It assigns the Space Administra
    > [!IMPORTANT]
    > To prevent unauthorized access to your Digital Twins Management API, the **occupancy-quickstart** application requires you to sign in with your Azure account credentials. It saves your credentials for a brief period, so you might not need to sign in every time you run it. The first time this program runs, and when your saved credentials expire after that, the application directs you to a sign-in page and gives a session-specific code to enter on that page. Follow the prompts to sign in with your Azure account.
 
-1. After your account is authenticated, the application starts creating a sample spatial graph as configured in `provisionSample.yaml`. Wait until the provisioning finishes. It will take a few minutes. After that, observe the messages in the command window and notice how your spatial graph is created. Notice how the application creates an IoT hub at the root node or the `Venue`.
+1. After your account is authenticated, the application starts creating a sample spatial graph as configured in *provisionSample.yaml*. Wait until the provisioning finishes. It will take a few minutes. After that, observe the messages in the command window and notice how your spatial graph is created. Notice how the application creates an IoT hub at the root node or the `Venue`.
 
 1. From the output in the command window, copy the value of `ConnectionString`, under the `Devices` section, to your clipboard. You'll need this value to simulate the device connection in the next section.
 
@@ -197,9 +198,9 @@ In this section, you'll use the project named *device-connectivity* in the sampl
 
    a. **DeviceConnectionString**: Assign the value of `ConnectionString` in the output window from the previous section. Copy this string completely, within the quotes, so the simulator can connect properly with the IoT hub.
 
-   b. **HardwareId** within the **Sensors** array: Because you're simulating events from sensors provisioned to your Azure Digital Twins instance, the hardware ID and the names of the sensors in this file should match the `sensors` node of the `provisionSample.yaml` file.
+   b. **HardwareId** within the **Sensors** array: Because you're simulating events from sensors provisioned to your Azure Digital Twins instance, the hardware ID and the names of the sensors in this file should match the `sensors` node of the *provisionSample.yaml* file.
 
-      Add a new entry for the temperature sensor. The **Sensors** node in `appsettings.json` should look like the following:
+      Add a new entry for the temperature sensor. The **Sensors** node in *appsettings.json* should look like the following:
 
       ```JSON
       "Sensors": [{