IoT Hub EG review

Author: ash2017

articles/event-grid/publish-iot-hub-events-to-logic-apps.md

@@ -166,15 +166,15 @@ In this section, you configure your IoT Hub to publish events as they occur.
 
     * **Event Subscription Details**: Provide a descriptive name and select **Event Grid Schema**
 
-You could save the event subscription here, and receive notifications for every device that is created in your IoT hub. For this tutorial, though, let's use the optional fields to filter for specific devices: 
+  You could save the event subscription here, and receive notifications for every device that is created in your IoT hub. For this tutorial, though, let's use the optional fields to filter for specific devices: 
 
-* **Subject Begins With**: Enter `devices/Building1_` to filter for device events in building 1.
-* **Subject Ends With**: Enter `_Temperature` to filter for device events related to temperature.
+  * **Subject Begins With**: Enter `devices/Building1_` to filter for device events in building 1.
+  * **Subject Ends With**: Enter `_Temperature` to filter for device events related to temperature.
 
-When you're done, the form should look like the following example: 
+  When you're done, the form should look like the following example: 
 
-   ![Sample event subscription form](./media/publish-iot-hub-events-to-logic-apps/subscription-form.png)
-   
+    ![Sample event subscription form](./media/publish-iot-hub-events-to-logic-apps/subscription-form.png)
+    
 5. Select **Create** to save the event subscription.
 
 ## Create a new device

articles/iot-hub/iot-hub-event-grid.md

@@ -39,7 +39,7 @@ Use either the Azure portal or Azure CLI to configure which events to publish fr
 
 IoT Hub events contain all the information you need to respond to changes in your device lifecycle. You can identify an IoT Hub event by checking that the eventType property starts with **Microsoft.Devices**. For more information about how to use Event Grid event properties, see the [Event Grid event schema](../event-grid/event-schema.md).
 
-### Device Connected schema
+### Device connected schema
 
 The following example shows the schema of a device connected event: 
 
@@ -125,9 +125,9 @@ The subject of IoT Events uses the format:
 ```json
 devices/{deviceId}
 ```
-## Limitations for Device Connected and Device Disconnected Events
+## Limitations for device connected and device disconnected events
 
-To receive device connected and device disconnected events, you must open the D2C link or C2D link for your device. If your device is using MQTT protocol, IoT Hub will keep the C2D link open. For AMQP you can open the C2D link by calling the [Receive Async API](https://docs.microsoft.com/en-us/dotnet/api/microsoft.azure.devices.client.deviceclient.receiveasync?view=azure-dotnet#Microsoft_Azure_Devices_Client_DeviceClient_ReceiveAsync). The D2C link is open if you are sending telemetry. If the device connection is flickering, i.e. the device connects and disconnects frequently, we will not send every single connection state, but will publish the connection state that is snapshotted every minute. In case of an IoT Hub outage, we will publish the device connection state as soon as the outage is over. If the device disconnects during that outage, the device disconnected event will be published within 10 minutes.
+To receive device connected and device disconnected events, you must open the D2C link or C2D link for your device. If your device is using MQTT protocol, IoT Hub will keep the C2D link open. For AMQP you can open the C2D link by calling the [Receive Async API](https://docs.microsoft.com/dotnet/api/microsoft.azure.devices.client.deviceclient.receiveasync?view=azure-dotnet). The D2C link is open if you are sending telemetry. If the device connection is flickering, i.e. the device connects and disconnects frequently, we will not send every single connection state, but will publish the connection state that is snapshotted every minute. In case of an IoT Hub outage, we will publish the device connection state as soon as the outage is over. If the device disconnects during that outage, the device disconnected event will be published within 10 minutes.
 
 ## Tips for consuming events
 
@@ -137,7 +137,6 @@ Applications that handle IoT Hub events should follow these suggested practices:
 * Don't assume that all events you receive are the types that you expect. Always check the eventType before processing the message.
 * Messages can arrive out of order or after a delay. Use the etag field to understand if your information about objects is up-to-date.
 
-
 ## Next steps
 
 * [Try the IoT Hub events tutorial](../event-grid/publish-iot-hub-events-to-logic-apps.md)

articles/iot-hub/iot-hub-how-to-order-connection-state-events.md

@@ -33,7 +33,7 @@ The sequence number is a string representation of a hexadecimal number. You can
 
 First, create a stored procedure and set it up to run a logic that compares sequence numbers of incoming events and records the latest event per device in the database.
 
-1. In your Cosmos DB SQL API, select **Data Explorer**-> **Items**->**New Stored Procedure**.
+1. In your Cosmos DB SQL API, select **Data Explorer** > **Items** > **New Stored Procedure**.
 
    ![Create stored procedure](./media/iot-hub-how-to-order-connection-state-events/create-stored-procedure.png)
 
@@ -255,10 +255,10 @@ In this section, you configure your IoT Hub to publish events as they occur.
 
 5. Select **Create** to save the event subscription.
 
-## Observe Events
+## Observe events
 Now that your event subscription is set up, let's test by connecting a device.
 
-### Register a device in the IoT Hub
+### Register a device in IoT Hub
 
 1. From your IoT hub, select **IoT Devices**. 
 2. Select **Add**.
@@ -272,7 +272,7 @@ Now that your event subscription is set up, let's test by connecting a device.
 
    ![How to outcome](./media/iot-hub-how-to-order-connection-state-events/DeviceConnString.png)
 
-### Start Raspberry Pi Simulator
+### Start Raspberry Pi simulator
 
 1. Let's use the Raspberry Pi web simulator to simulate device connection.