Merge pull request #77858 from v-stadam/update_IoT_toolkit_UI_0523

GitHubber17 · web-flow · commit 01138e7acb4a · 2019-05-24T12:00:49.000-07:00
Update content for UI changes
diff --git a/articles/iot-edge/how-to-visual-studio-develop-module.md b/articles/iot-edge/how-to-visual-studio-develop-module.md
@@ -233,9 +233,9 @@ In the quickstart article that you used to set up your IoT Edge device, you depl
 
 ## View generated data
 
-1. To monitor the D2C message for a specific device, select the device in the list and then click **Start Monitoring D2C Messages** in the **Action** window.
+1. To monitor the D2C message for a specific device, select the device in the list and then click **Start Monitoring Built-in Event Endpoint** in the **Action** window.
 
-1. To stop monitoring data, select the device in the list and then select **Stop Monitoring D2C Messages** in the **Action** window.
+1. To stop monitoring data, select the device in the list and then select **Stop Monitoring Built-in Event Endpoint** in the **Action** window.
 
 ## Next steps
 
diff --git a/articles/iot-edge/media/tutorial-c-module/view-d2c-message.png b/articles/iot-edge/media/tutorial-c-module/view-d2c-message.png
diff --git a/articles/iot-edge/media/tutorial-csharp-module/view-d2c-message.png b/articles/iot-edge/media/tutorial-csharp-module/view-d2c-message.png
diff --git a/articles/iot-edge/tutorial-c-module-windows.md b/articles/iot-edge/tutorial-c-module-windows.md
@@ -327,7 +327,7 @@ You can use the IoT Edge Tools extension to view messages as they arrive at your
 
 1. In the Visual Studio cloud explorer, select the name of your IoT Edge device. 
 
-2. In the **Actions** list, select **Start Monitoring D2C Message**. 
+2. In the **Actions** list, select **Start Monitoring Built-in Event Endpoint**. 
 
 3. View the messages arriving at your IoT Hub. It may take a while for the messages to arrive, because the IoT Edge device has to receive its new deployment and start all the modules. Then, the changes we made to the CModule code wait until the machine temperature reaches 25 degrees before sending messages. It also adds the message type **Alert** to any messages that reach that temperature threshold. 
 
diff --git a/articles/iot-edge/tutorial-c-module.md b/articles/iot-edge/tutorial-c-module.md
@@ -312,7 +312,7 @@ Once you apply the deployment manifest to your IoT Edge device, the IoT Edge run
 
 You can view the status of your IoT Edge device using the **Azure IoT Hub Devices** section of the Visual Studio Code explorer. Expand the details of your device to see a list of deployed and running modules.
 
-1. In the Visual Studio Code explorer, right-click the name of your IoT Edge device and select **Start Monitoring D2C Messages**.
+1. In the Visual Studio Code explorer, right-click the name of your IoT Edge device and select **Start Monitoring Built-in Event Endpoint**.
 
 2. View the messages arriving at your IoT Hub. It may take a while for the messages to arrive, because the IoT Edge device has to receive its new deployment and start all the modules. Then, the changes we made to the CModule code wait until the machine temperature reaches 25 degrees before sending messages. It also adds the message type **Alert** to any messages that reach that temperature threshold. 
 
diff --git a/articles/iot-edge/tutorial-csharp-module-windows.md b/articles/iot-edge/tutorial-csharp-module-windows.md
@@ -320,7 +320,7 @@ You can use the IoT Edge Tools extension to view messages as they arrive at your
 
 1. In the Visual Studio cloud explorer, select the name of your IoT Edge device. 
 
-2. In the **Actions** list, select **Start Monitoring D2C Message**. 
+2. In the **Actions** list, select **Start Monitoring Built-in Event Endpoint**. 
 
 3. View the messages arriving at your IoT Hub. It may take a while for the messages to arrive, because the changes we made to the CSharpModule code wait until the machine temperature reaches 25 degrees before sending messages. It also adds the message type **Alert** to any messages that reach that temperature threshold. 
 
diff --git a/articles/iot-edge/tutorial-csharp-module.md b/articles/iot-edge/tutorial-csharp-module.md
@@ -48,7 +48,7 @@ Before beginning this tutorial, you should have gone through the previous tutori
 * A free or standard-tier [IoT Hub](../iot-hub/iot-hub-create-through-portal.md) in Azure.
 * A [Linux device running Azure IoT Edge](quickstart-linux.md).
 * A container registry, like [Azure Container Registry](https://docs.microsoft.com/azure/container-registry/).
-* [Visual Studio Code](https://code.visualstudio.com/) configured with the [Azure IoT Tools](https://marketplace.visualstudio.com/items?itemName=vsciot-vscode.azure-iot-tools) extension.
+* [Visual Studio Code](https://code.visualstudio.com/) configured with the [Azure IoT Tools](https://marketplace.visualstudio.com/items?itemName=vsciot-vscode.azure-iot-tools).
 * [Docker CE](https://docs.docker.com/install/) configured to run Linux containers.
 
 To complete these tutorials, prepare the following additional prerequisites on your development machine: 
@@ -296,7 +296,7 @@ Once you apply the deployment manifest to your IoT Edge device, the IoT Edge run
 
 You can view the status of your IoT Edge device using the **Azure IoT Hub Devices** section of the Visual Studio Code explorer. Expand the details of your device to see a list of deployed and running modules.
 
-1. In the Visual Studio Code explorer, right-click the name of your IoT Edge device and select **Start Monitoring D2C Messages**.
+1. In the Visual Studio Code explorer, right-click the name of your IoT Edge device and select **Start Monitoring Built-in Event Endpoint**.
 
 2. View the messages arriving at your IoT Hub. It may take a while for the messages to arrive, because the IoT Edge device has to receive its new deployment and start all the modules. Then, the changes we made to the CModule code wait until the machine temperature reaches 25 degrees before sending messages. It also adds the message type **Alert** to any messages that reach that temperature threshold. 
 
diff --git a/articles/iot-edge/tutorial-deploy-custom-vision.md b/articles/iot-edge/tutorial-deploy-custom-vision.md
@@ -434,7 +434,7 @@ From your device, view the logs of the cameraCapture module to see the messages
    iotedge logs cameraCapture
    ```
 
-From Visual Studio Code, right-click on the name of your IoT Edge device and select **Start monitoring D2C message**. 
+From Visual Studio Code, right-click on the name of your IoT Edge device and select **Start Monitoring Built-in Event Endpoint**. 
 
 The results from the Custom Vision module, which are sent as messages from the cameraCapture module, include the probability that the image is of either a hemlock or cherry tree. Since the image is hemlock, you should see the probability as 1.0. 
 
diff --git a/articles/iot-edge/tutorial-deploy-function.md b/articles/iot-edge/tutorial-deploy-function.md
@@ -218,12 +218,11 @@ You can use the Azure portal to deploy your function module to an IoT Edge devic
 
 ## View generated data
 
-You can see all of the messages that arrive at your IoT hub by running **Azure IoT Hub: Start Monitoring D2C Message** in the command palette.
+You can see all of the messages that arrive at your IoT hub by running **Azure IoT Hub: Start Monitoring Built-in Event Endpoint** in the command palette.
 
-You can also filter the view to see all of the messages that arrive at your IoT hub from a specific device. Right-click the device in the **Azure IoT Hub Devices** section and select **Start Monitoring D2C Messages**.
-
-To stop monitoring messages, run the command **Azure IoT Hub: Stop monitoring D2C message** in the command palette. 
+You can also filter the view to see all of the messages that arrive at your IoT hub from a specific device. Right-click the device in the **Azure IoT Hub Devices** section and select **Start Monitoring Built-in Event Endpoint**.
 
+To stop monitoring messages, run the command **Azure IoT Hub: Stop Monitoring Built-in Event Endpoint** in the command palette. 
 
 ## Clean up resources
 
@@ -241,4 +240,3 @@ Continue on to the next tutorials to learn other ways that Azure IoT Edge can he
 
 > [!div class="nextstepaction"]
 > [Find averages by using a floating window in Azure Stream Analytics](tutorial-deploy-stream-analytics.md)
-
diff --git a/articles/iot-edge/tutorial-deploy-machine-learning.md b/articles/iot-edge/tutorial-deploy-machine-learning.md
@@ -140,7 +140,7 @@ The following steps show you how to set up Visual Studio Code to monitor device-
 
 3. In the text box that opens at the top of the page, enter the iothubowner connection string for your IoT Hub. Your IoT Edge device should appear in the IoT Hub Devices list.
 
-4. Select **...** again then select **Start monitoring D2C message**.
+4. Select **...** again then select **Start Monitoring Built-in Event Endpoint**.
 
 5. Observe the messages coming from tempSensor every five seconds. The message body contains a property called **anomaly**, which the machinelearningmodule provides with a true or false value. The **AzureMLResponse** property contains the value "OK" if the model ran successfully.
 
diff --git a/articles/iot-edge/tutorial-develop-for-linux.md b/articles/iot-edge/tutorial-develop-for-linux.md
@@ -279,7 +279,7 @@ You verified that the built container images are stored in your container regist
 
 The SampleModule code receives messages through its input queue and passes them along through its output queue. The deployment manifest declared routes that passed messages to SampleModule from tempSensor, and then forwarded messages from SampleModule to IoT Hub. The Azure IoT tools for Visual Studio Code allow you to see messages as they arrive at IoT Hub from your individual devices. 
 
-1. In the Visual Studio Code explorer, right-click the IoT Edge device that you want to monitor, then select **Start Monitoring D2C Message**. 
+1. In the Visual Studio Code explorer, right-click the IoT Edge device that you want to monitor, then select **Start Monitoring Built-in Event Endpoint**. 
 
 2. Watch the output window in Visual Studio Code to see messages arriving at your IoT hub. 
 
diff --git a/articles/iot-edge/tutorial-develop-for-windows.md b/articles/iot-edge/tutorial-develop-for-windows.md
@@ -293,7 +293,7 @@ The IotEdgeModule1 code receives messages through its input queue and passes the
 
 1. In the Visual Studio cloud explorer, select the name of the IoT Edge device that you deployed to. 
 
-2. In the **Actions** menu, select **Start Monitoring D2C Message**.
+2. In the **Actions** menu, select **Start Monitoring Built-in Event Endpoint**.
 
 3. Watch the **Output** section in Visual Studio to see messages arriving at your IoT hub. 
 
diff --git a/articles/iot-edge/tutorial-java-module.md b/articles/iot-edge/tutorial-java-module.md
@@ -256,7 +256,7 @@ Once you apply the deployment manifest to your IoT Edge device, the IoT Edge run
 
 You can view the status of your IoT Edge device using the **Azure IoT Hub Devices** section of the Visual Studio Code explorer. Expand the details of your device to see a list of deployed and running modules.
 
-1. In the Visual Studio Code explorer, right-click the name of your IoT Edge device and select **Start Monitoring D2C Messages**.
+1. In the Visual Studio Code explorer, right-click the name of your IoT Edge device and select **Start Monitoring Built-in Event Endpoint**.
 
 2. View the messages arriving at your IoT Hub. It may take a while for the messages to arrive, because the IoT Edge device has to receive its new deployment and start all the modules. Then, the changes we made to the JavaModule code wait until the machine temperature reaches 25 degrees before sending messages. It also adds the message type **Alert** to any messages that reach that temperature threshold. 
 
@@ -274,8 +274,8 @@ We used the JavaModule module twin in the deployment manifest to set the tempera
 
 5. Right-click anywhere in the module twin editing pane and select **Update module twin**. 
 
-5. Monitor the incoming device-to-cloud messages. You should see the messages stop until the new temperature threshold is reached. 
- 
+6. Monitor the incoming device-to-cloud messages. You should see the messages stop until the new temperature threshold is reached. 
+
 ## Clean up resources 
 
 If you plan to continue to the next recommended article, you can keep the resources and configurations that you created and reuse them. You can also keep using the same IoT Edge device as a test device. 
diff --git a/articles/iot-edge/tutorial-node-module.md b/articles/iot-edge/tutorial-node-module.md
@@ -217,11 +217,10 @@ Once you apply the deployment manifest to your IoT Edge device, the IoT Edge run
 
 You can view the status of your IoT Edge device using the **Azure IoT Hub Devices** section of the Visual Studio Code explorer. Expand the details of your device to see a list of deployed and running modules.
 
-1. In the Visual Studio Code explorer, right-click the name of your IoT Edge device and select **Start Monitoring D2C Messages**.
+1. In the Visual Studio Code explorer, right-click the name of your IoT Edge device and select **Start Monitoring Built-in Event Endpoint**.
 
 2. View the messages arriving at your IoT Hub. It may take a while for the messages to arrive, because the IoT Edge device has to receive its new deployment and start all the modules. Then, the changes we made to the NodeModule code wait until the machine temperature reaches 25 degrees before sending messages. It also adds the message type **Alert** to any messages that reach that temperature threshold. 
 
-
 ## Edit the module twin
 
 We used the NodeModule module twin in the deployment manifest to set the temperature threshold at 25 degrees. You can use the module twin to change the functionality without having to update the module code.
@@ -236,7 +235,7 @@ We used the NodeModule module twin in the deployment manifest to set the tempera
 
 5. Right-click anywhere in the module twin editing pane and select **Update module twin**. 
 
-5. Monitor the incoming device-to-cloud messages. You should see the messages stop until the new temperature threshold is reached. 
+6. Monitor the incoming device-to-cloud messages. You should see the messages stop until the new temperature threshold is reached. 
 
 ## Clean up resources 
 
@@ -246,7 +245,6 @@ Otherwise, you can delete the local configurations and the Azure resources that
 
 [!INCLUDE [iot-edge-clean-up-cloud-resources](../../includes/iot-edge-clean-up-cloud-resources.md)]
 
-
 ## Next steps
 
 In this tutorial, you created an IoT Edge module that contains code to filter raw data generated by your IoT Edge device. When you're ready to build your own modules, you can learn more about [developing your own IoT Edge modules](module-development.md) or how to [develop modules with Visual Studio Code](how-to-vs-code-develop-module.md). You can continue on to the next tutorials to learn how Azure IoT Edge can help you deploy Azure cloud services to process and analyze data at the edge.
diff --git a/articles/iot-edge/tutorial-python-module.md b/articles/iot-edge/tutorial-python-module.md
@@ -238,7 +238,7 @@ Once you apply the deployment manifest to your IoT Edge device, the IoT Edge run
 
 You can view the status of your IoT Edge device using the **Azure IoT Hub Devices** section of the Visual Studio Code explorer. Expand the details of your device to see a list of deployed and running modules.
 
-1. In the Visual Studio Code explorer, right-click the name of your IoT Edge device and select **Start Monitoring D2C Messages**.
+1. In the Visual Studio Code explorer, right-click the name of your IoT Edge device and select **Start Monitoring Built-in Event Endpoint**.
 
 2. View the messages arriving at your IoT Hub. It may take a while for the messages to arrive, because the IoT Edge device has to receive its new deployment and start all the modules. Then, the changes we made to the PythonModule code wait until the machine temperature reaches 25 degrees before sending messages. It also adds the message type **Alert** to any messages that reach that temperature threshold. 
 
@@ -256,7 +256,7 @@ We used the PythonModule module twin in the deployment manifest to set the tempe
 
 5. Right-click anywhere in the module twin editing pane and select **Update module twin**. 
 
-5. Monitor the incoming device-to-cloud messages. You should see the messages stop until the new temperature threshold is reached. 
+6. Monitor the incoming device-to-cloud messages. You should see the messages stop until the new temperature threshold is reached. 
 
 ## Clean up resources 
 
@@ -266,7 +266,6 @@ Otherwise, you can delete the local configurations and the Azure resources that
 
 [!INCLUDE [iot-edge-clean-up-cloud-resources](../../includes/iot-edge-clean-up-cloud-resources.md)]
 
-
 ## Next steps
 
 In this tutorial, you created an IoT Edge module that contains code to filter raw data generated by your IoT Edge device. When you're ready to build your own modules, you can learn more about [developing your own IoT Edge modules](module-development.md) or how to [develop modules with Visual Studio Code](how-to-vs-code-develop-module.md). You can continue on to the next tutorials to learn how Azure IoT Edge can help you deploy Azure cloud services to process and analyze data at the edge.
