Merge pull request #78860 from itechedit/six-iot-hub-quickstarts-2

edit pass: six IoT Hub quickstarts

Author: ShawnJackson

articles/iot-hub/quickstart-device-streams-echo-c.md

@@ -1,6 +1,6 @@
 ---
 title: Communicate to a device app in C via Azure IoT Hub device streams (preview) | Microsoft Docs
-description: In this quickstart, you will run a C service-side application that communicates with an IoT device via a device stream.
+description: In this quickstart, you run a C device-side application that communicates with an IoT device via a device stream.
 author: rezasherafat
 manager: briz
 ms.service: iot-hub
@@ -16,69 +16,66 @@ ms.author: rezas
 
 [!INCLUDE [iot-hub-quickstarts-3-selector](../../includes/iot-hub-quickstarts-3-selector.md)]
 
-Microsoft Azure IoT Hub currently supports device streams as a [preview feature](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
+Azure IoT Hub currently supports device streams as a [preview feature](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
 
-[IoT Hub device streams](iot-hub-device-streams-overview.md) allow service and device applications to communicate in a secure and firewall-friendly manner. During public preview, the C SDK only supports device streams on the device side. As a result, this quickstart only covers instructions to run the device-side application. You should run an accompanying service-side application, which is available in the following quickstarts:
+[IoT Hub device streams](iot-hub-device-streams-overview.md) allow service and device applications to communicate in a secure and firewall-friendly manner. During public preview, the C SDK supports device streams on the device side only. As a result, this quickstart covers instructions to run only the device-side application. To run an accompanying service-side application, see:
 
-   * [Communicating to device apps in C# via IoT Hub device streams](./quickstart-device-streams-echo-csharp.md)
-
-   * [Communicating to device apps in Nodejs via IoT Hub device streams](./quickstart-device-streams-echo-nodejs.md).
+   * [Communicate to device apps in C# via IoT Hub device streams](./quickstart-device-streams-echo-csharp.md)
+   * [Communicate to device apps in Node.js via IoT Hub device streams](./quickstart-device-streams-echo-nodejs.md)
 
 The device-side C application in this quickstart has the following functionality:
 
 * Establish a device stream to an IoT device.
+* Receive data that's sent from the service-side application and echo it back.
 
-* Receive data sent from the service-side and echo it back.
-
-The code will demonstrate the initiation process of a device stream, as well as how to use it to send and receive data.
+The code demonstrates the initiation process of a device stream, as well as how to use it to send and receive data.
 
 [!INCLUDE [cloud-shell-try-it.md](../../includes/cloud-shell-try-it.md)]
 
 If you don’t have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
 
 ## Prerequisites
 
-* The preview of device streams is currently only supported for IoT Hubs created in the following regions:
-
-  * **Central US**
+* The preview of device streams is currently supported only for IoT hubs that are created in the following regions:
 
-  * **Central US EUAP**
+  * Central US
+  * Central US EUAP
 
-* Install [Visual Studio 2017](https://www.visualstudio.com/vs/) with the ['Desktop development with C++'](https://www.visualstudio.com/vs/support/selecting-workloads-visual-studio-2017/) workload enabled.
+* Install [Visual Studio 2017](https://www.visualstudio.com/vs/) with the [Desktop development with C++](https://www.visualstudio.com/vs/support/selecting-workloads-visual-studio-2017/) workload enabled.
 
 * Install the latest version of [Git](https://git-scm.com/download/).
 
-* Run the following command to add the Microsoft Azure IoT Extension for Azure CLI to your Cloud Shell instance. The IOT Extension adds IoT Hub, IoT Edge, and IoT Device Provisioning Service (DPS) specific commands to Azure CLI.
+* Run the following command to add the Azure IoT Extension for Azure CLI to your Cloud Shell instance. The IOT Extension adds IoT Hub, IoT Edge, and IoT Device Provisioning Service (DPS)-specific commands to the Azure CLI.
 
    ```azurecli-interactive
    az extension add --name azure-cli-iot-ext
    ```
 
 ## Prepare the development environment
 
-For this quickstart, you will be using the [Azure IoT device SDK for C](iot-hub-device-sdk-c-intro.md). You will prepare a development environment used to clone and build the [Azure IoT C SDK](https://github.com/Azure/azure-iot-sdk-c) from GitHub. The SDK on GitHub includes the sample code used in this quickstart.
+For this quickstart, you use the [Azure IoT device SDK for C](iot-hub-device-sdk-c-intro.md). You prepare a development environment used to clone and build the [Azure IoT C SDK](https://github.com/Azure/azure-iot-sdk-c) from GitHub. The SDK on GitHub includes the sample code that's used in this quickstart.
 
 1. Download the [CMake build system](https://cmake.org/download/).
 
-    It is important that the Visual Studio prerequisites (Visual Studio and the 'Desktop development with C++' workload) are installed on your machine, **before** starting the `CMake` installation. Once the prerequisites are in place, and the download is verified, install the CMake build system.
+    Before you start the CMake installation, it's important that the Visual Studio prerequisites (Visual Studio and the *Desktop development with C++* workload) are installed on your machine. After the prerequisites are in place and you've verified the download, you can install the CMake build system.
 
 2. Open a command prompt or Git Bash shell. Execute the following command to clone the [Azure IoT C SDK](https://github.com/Azure/azure-iot-sdk-c) GitHub repository:
 
     ```
     git clone https://github.com/Azure/azure-iot-sdk-c.git --recursive -b public-preview
     ```
 
-    You should expect this operation to take a few minutes.
+    This operation should take a few minutes.
 
-3. Create a `cmake` subdirectory in the root directory of the git repository, and navigate to that folder.
+3. Create a *cmake* subdirectory in the root directory of the Git repository, as shown in the following command, and then go to that folder.
 
     ```
     cd azure-iot-sdk-c
     mkdir cmake
     cd cmake
     ```
 
-4. Run the following commands from the `cmake` directory to build a version of the SDK specific to your development client platform.
+4. Run the following commands from the *cmake* directory to build a version of the SDK that's specific to your development client platform.
 
    * In Linux:
 
@@ -87,7 +84,7 @@ For this quickstart, you will be using the [Azure IoT device SDK for C](iot-hub-
       make -j
       ```
 
-   * In Windows, run the following commands in Developer Command Prompt for Visual Studio 2015 or 2017. A Visual Studio solution for the simulated device will be generated in the `cmake` directory.
+   * In Windows, run the following commands in Developer Command Prompt for Visual Studio 2015 or 2017. A Visual Studio solution for the simulated device will be generated in the *cmake* directory.
 
       ```cmd
       rem For VS2015
@@ -106,41 +103,40 @@ For this quickstart, you will be using the [Azure IoT device SDK for C](iot-hub-
 
 ## Register a device
 
-A device must be registered with your IoT hub before it can connect. In this section, you will use the Azure Cloud Shell with the [IoT extension](https://docs.microsoft.com/cli/azure/ext/azure-cli-iot-ext/iot?view=azure-cli-latest) to register a simulated device.
+You must register a device with your IoT hub before it can connect. In this section, you use Azure Cloud Shell with the [IoT Extension](https://docs.microsoft.com/cli/azure/ext/azure-cli-iot-ext/iot?view=azure-cli-latest) to register a simulated device.
 
-1. Run the following command in Azure Cloud Shell to create the device identity.
+1. To create the device identity, run the following command in Cloud Shell:
 
-   **YourIoTHubName**: Replace this placeholder below with the name you choose for your IoT hub.
-
-   **MyDevice**: This is the name given for the registered device. Use MyDevice as shown. If you choose a different name for your device, you will also need to use that name throughout this article, and update the device name in the sample applications before you run them.
+   > [!NOTE]
+   > * Replace the *YourIoTHubName* placeholder with the name you choose for your IoT hub.
+   > * Use *MyDevice*, as shown. It's the name given for the registered device. If you choose a different name for your device, use that name throughout this article, and update the device name in the sample applications before you run them.
 
     ```azurecli-interactive
     az iot hub device-identity create --hub-name YourIoTHubName --device-id MyDevice
     ```
 
-2. Run the following commands in Azure Cloud Shell to get the *device connection string* for the device you just registered:
+2. To get the *device connection string* for the device that you just registered, run the following commands in Cloud Shell:
 
-   **YourIoTHubName**: Replace this placeholder below with the name you choose for your IoT hub.
+   > [!NOTE]
+   > Replace the *YourIoTHubName* placeholder with the name you choose for your IoT hub.
 
     ```azurecli-interactive
     az iot hub device-identity show-connection-string --hub-name YourIoTHubName --device-id MyDevice --output table
     ```
 
-    Make a note of the device connection string, which looks like the following example:
+    Note the device connection string for later use in this quickstart. It looks like the following example:
 
    `HostName={YourIoTHubName}.azure-devices.net;DeviceId=MyDevice;SharedAccessKey={YourSharedAccessKey}`
 
-    You use this value later in the quickstart.
-
-## Communicate between device and service via device streams
+## Communicate between the device and the service via device streams
 
 In this section, you run both the device-side application and the service-side application and communicate between the two.
 
 ### Run the device-side application
 
-To run the device-side application, you need to perform the following steps:
+To run the device-side application, do the following:
 
-1. Provide your device credentials by editing the source file `iothub_client_c2d_streaming_sample.c` in the folder `iothub_client/samples/iothub_client_c2d_streaming_sample` and providing your device connection string.
+1. Provide your device credentials by editing the *iothub_client_c2d_streaming_sample.c* source file in the *iothub_client/samples/iothub_client_c2d_streaming_sample* folder and then providing your device connection string.
 
    ```C
    /* Paste in your iothub connection string  */
@@ -177,21 +173,20 @@ To run the device-side application, you need to perform the following steps:
 
 ### Run the service-side application
 
-As mentioned previously, the IoT Hub C SDK only supports device streams on the device side. To build and run the service-side application, follow the steps available in one of the following quickstarts:
+As mentioned previously, the IoT Hub C SDK supports device streams on the device side only. To build and run the service-side application, follow the instructions in one of the following quickstarts:
 
 * [Communicate to a device app in C# via IoT Hub device streams](./quickstart-device-streams-echo-csharp.md)
-
-* [Communicate to a device app in Node.js via IoT Hub device streams](./quickstart-device-streams-echo-nodejs.md).
+* [Communicate to a device app in Node.js via IoT Hub device streams](./quickstart-device-streams-echo-nodejs.md)
 
 ## Clean up resources
 
 [!INCLUDE [iot-hub-quickstarts-clean-up-resources-device-streams](../../includes/iot-hub-quickstarts-clean-up-resources-device-streams.md)]
 
 ## Next steps
 
-In this quickstart, you have set up an IoT hub, registered a device, established a device stream between a C application on the device and another application on the service side, and used the stream to send data back and forth between the applications.
+In this quickstart, you've set up an IoT hub, registered a device, established a device stream between a C application on the device and another application on the service side, and used the stream to send data back and forth between the applications.
 
-Use the links below to learn more about device streams:
+To learn more about device streams, see:
 
 > [!div class="nextstepaction"]
-> [Device streams overview](./iot-hub-device-streams-overview.md)
+> [Device streams overview](./iot-hub-device-streams-overview.md)