Updated screenshots

Author: kgremban

articles/iot-hub/media/tutorial-connectivity/metrics-portal.png

@@ -118,13 +118,13 @@ In some scenarios, such as in a cloud protocol gateway or as part of a custom au
 > [!NOTE]
 > The SimulatedDevice-2.js sample includes examples of generating a SAS token both with and without the SDK.
 
-1. To generate a known-good SAS token using the CLI, run the following command:
+1. Run the following command to generate a known-good SAS token using the CLI:
 
    ```azurecli-interactive
    az iot hub generate-sas-token --device-id {your_device_id} --hub-name {your_iot_hub_name}
    ```
 
-1. Make a note of the full text of the generated SAS token. A SAS token looks like the following example: `SharedAccessSignature sr=tutorials-iot-hub.azure-devices.net%2Fdevices%2FMyTestDevice&sig=....&se=1524155307`
+1. Copy the full text of the generated SAS token. A SAS token looks like the following example: `SharedAccessSignature sr=tutorials-iot-hub.azure-devices.net%2Fdevices%2FmyDevice&sig=xxxxxx&se=111111`
 
 1. In a terminal window on your development machine, navigate to the root folder of the sample Node.js project you downloaded. Then navigate to the **iot-hub\Tutorials\ConnectivityTests** folder.
 
@@ -135,9 +135,9 @@ In some scenarios, such as in a cloud protocol gateway or as part of a custom au
    node SimulatedDevice-2.js "{Your SAS token}"
    ```
 
-   The terminal window displays information as it tries to connect to your hub using the SAS token:
+   The terminal window displays a success message once it connects to your hub using the SAS token:
 
-   ![Simulated device connecting with token](media/tutorial-connectivity/sim-2-connected.png)
+   :::image type="content" source="media/tutorial-connectivity/sim-2-connected.png" alt-text="Screenshot that shows a successful connection using a SAS token.":::
 
 You've now successfully authenticated from a device using a test SAS token generated by a CLI command. The **SimulatedDevice-2.js** file includes sample code that shows you how to generate a SAS token in code.
 
@@ -163,7 +163,7 @@ After a device connects, it can start sending telemetry to your IoT hub. This se
 
 ### Send device-to-cloud messages
 
-1. First, retrieve the current connection string for your simulated device using the following command:
+1. Since we reset the connection string for your device in the previous section, use the following command to retrieve the updated connection string:
 
    ```azurecli-interactive
    az iot hub device-identity connection-string show --device-id {your_device_id} --output table --hub-name {your_iot_hub_name}
@@ -180,7 +180,7 @@ After a device connects, it can start sending telemetry to your IoT hub. This se
 
    The terminal window displays information as it sends telemetry to your hub:
 
-   ![Simulated device sending messages](media/tutorial-connectivity/sim-3-sending.png)
+   :::image type="content" source="media/tutorial-connectivity/sim-3-sending.png" alt-text="Screenshot that shows the simulated device sending messages.":::
 
 ### Monitor incoming messages