Fixed PR blocking issues

Author: w-azure

articles/iot-hub/iot-hub-create-through-portal.md

@@ -54,15 +54,15 @@ For more detailed information about the access granted by specific permissions,
 
 [!INCLUDE [iot-hub-include-create-device](../../includes/iot-hub-include-create-device.md)]
 
-## Message Routing for an IoT hub
+## Message routing for an IoT hub
 
 Select **Message Routing** under **Messaging** to see the Message Routing pane, where you define routes and custom endpoints for the hub. [Message routing](iot-hub-devguide-messages-d2c.md) enables you to manage how data is sent from your devices to your endpoints. The first step is to add a new route. Then you can add an existing endpoint to the route, or create a new one of the types supported, such as blob storage.
 
 ### Routes
 
 **Routes** is the first tab on the **Message Routing** pane. To add a new route, select **+ Add**. 
 
-![Message routing pane](./media/iot-hub-create-through-portal/iot-hub-message-routing.png)
+![Screenshot showing the 'Message Routing' pane with the '+ Add' button.](./media/iot-hub-create-through-portal/iot-hub-message-routing.png)
 
 You see the following screen.
 
@@ -74,7 +74,7 @@ For **Endpoint**, select one from the dropdown list or add a new one. In this ex
 
 The following screen shows where the storage account and container are specified.
 
-![Screenshot showing adding a storage endpoint for the routing rule](./media/iot-hub-create-through-portal/iot-hub-routing-add-storage-endpoint.png)
+![Screenshot showing how to add a storage endpoint for the routing rule.](./media/iot-hub-create-through-portal/iot-hub-routing-add-storage-endpoint.png)
 
 Add an endpoint name in **Endpoint name** if needed. Select **Pick a container** to select the storage account and container. When you've chosen a container then **Select**, the page returns to the **Add a storage endpoint** pane. Use the defaults for the rest of the fields and **Create** to create the endpoint for the storage account and add it to the routing rules. 
 
@@ -109,7 +109,7 @@ Here are two ways to find a specific IoT hub in your subscription:
 
 ## Delete the IoT hub
 
-To delete an Iot hub, find the IoT hub you want to delete, then choose **Delete**.
+To delete an IoT hub, find the IoT hub you want to delete, then choose **Delete**.
 
 ## Next steps
 

includes/iot-hub-include-create-device.md

@@ -15,19 +15,19 @@ In this section, you create a device identity in the identity registry in your I
 
 1. In your IoT hub navigation menu, open **Devices**, then select **Add Device** to add a device in your IoT hub.
 
-    :::image type="content" source="./media/iot-hub-include-create-device/create-identity-portal.png" alt-text="Screen capture that shows how to create a device identity in the portal" border="true":::
+    :::image type="content" source="./media/iot-hub-include-create-device/create-identity-portal.png" alt-text="Screen capture that shows how to create a device identity in the portal." border="true":::
 
 1. In **Create a device**, provide a name for your new device, such as **myDeviceId**, and select **Save**. This action creates a device identity for your IoT hub. Leave **Auto-generate keys** checked so that the primary and secondary keys will be generated automatically.
 
-    :::image type="content" source="./media/iot-hub-include-create-device/create-device.png" alt-text="Screen capture that shows how to add a new device" border="true":::
+    :::image type="content" source="./media/iot-hub-include-create-device/create-device.png" alt-text="Screen capture that shows how to add a new device." border="true":::
 
     [!INCLUDE [iot-hub-pii-note-naming-device](iot-hub-pii-note-naming-device.md)]
 
 1. After the device is created, open the device from the list in the **Devices** pane. Copy the **Primary Connection String**. This connection string is used by device code to communicate with the hub.
 
     By default, the keys and connection strings are masked as they're sensitive information. If you click the eye icon, they're revealed. It's not necessary to reveal them to copy them with the copy button.
 
-    :::image type="content" source="./media/iot-hub-include-create-device/device-details.png" alt-text="Screen capture that shows the device connection string" border="true" lightbox="./media/iot-hub-include-create-device/device-details.png":::
+    :::image type="content" source="./media/iot-hub-include-create-device/device-details.png" alt-text="Screen capture that shows the device connection string." border="true" lightbox="./media/iot-hub-include-create-device/device-details.png":::
 
 > [!NOTE]
 > The IoT Hub identity registry only stores device identities to enable secure access to the IoT hub. It stores device IDs and keys to use as security credentials, and an enabled/disabled flag that you can use to disable access for an individual device. If your application needs to store other device-specific metadata, it should use an application-specific store. For more information, see [IoT Hub developer guide](../articles/iot-hub/iot-hub-devguide-identity-registry.md).