Merge pull request #300203 from DENKEN02MSFT/Top50_sonialopez_Row11

Top50 - row 11

Author: prmerger-automator[bot]

articles/iot-hub/create-connect-device.md

@@ -7,7 +7,7 @@ author: SoniaLopezBravo
 ms.author: sonialopez
 ms.service: azure-iot-hub
 ms.topic: how-to
-ms.date: 06/19/2024
+ms.date: 05/20/2025
 ---
 
 # Create and manage device identities
@@ -16,11 +16,11 @@ Create a device identity for your device to connect to Azure IoT Hub. This artic
 
 ## Prerequisites
 
-* An IoT hub in your Azure subscription. If you don't have a hub yet, you can follow the steps in [Create an IoT hub](create-hub.md).
+* An IoT hub in your Azure subscription. If you don't have a hub yet, you can follow the steps in [Create an IoT hub](create-hub.md#create-an-iot-hub).
 
 * Depending on which tool you use, either have access to the [Azure portal](https://portal.azure.com) or [install the Azure CLI](/cli/azure/install-azure-cli).
 
-* If your IoT hub is managed with role-based access control (RBAC), then you need **Read/Write/Delete Device/Module** permissions for the steps in this article. Those permissions are included in [IoT Hub Registry Contributor](../role-based-access-control/built-in-roles/internet-of-things.md#iot-hub-registry-contributor) role.
+* If your IoT hub is managed with role-based access control (RBAC), then you need **Read/Write/Delete Device/Module** permissions for the steps in this article. Those permissions are included in the [IoT Hub Registry Contributor](../role-based-access-control/built-in-roles/internet-of-things.md#iot-hub-registry-contributor) role.
 
 ## Prepare certificates
 
@@ -36,7 +36,7 @@ Azure IoT devices use TLS to verify the authenticity of the IoT hub or DPS endpo
 * DigiCert Global G2 root CA
 * Microsoft RSA root CA 2017
 
-For more information about IoT Hub's recommended certificate practices, see [TLS support](./iot-hub-tls-support.md).
+For more information about IoT Hub's recommended certificate practices, see [Transport Layer Security (TLS) support in IoT Hub](./iot-hub-tls-support.md).
 
 ### Authentication certificates
 
@@ -60,7 +60,7 @@ When you register a device, you choose its authentication method. IoT Hub suppor
 
 * **Symmetric key** - *This option is easiest for quickstart scenarios.*
 
-  When you register a device, you can provide keys or IoT Hub will generate keys for you. Both the device and the IoT hub have a copy of the symmetric key that can be compared when the device connects.
+  When you register a device, you can provide keys or IoT Hub generates keys for you. Both the device and the IoT hub have a copy of the symmetric key that can be compared when the device connects.
 
 * **X.509 self-signed**
 
@@ -137,11 +137,11 @@ The Azure portal provides device connection strings only for devices that use sy
 
    :::image type="content" source="./media/create-connect-device/copy-connection-string.png" alt-text="Screenshot that shows copying the value of the primary connection string from the Azure portal.":::
 
-   By default, the keys and connection strings are masked because 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.
+   By default, the keys and connection strings are masked because they're sensitive information. If you select the eye icon, they're revealed. It's not necessary to reveal them to copy them with the copy button.
 
 ### [Azure CLI](#tab/cli)
 
-Use the [az iot hub device-identity connection-string show](/cli/azure/iot/hub/device-identity#az-iot-hub-device-identity-connection-string-show) command to retrieve a device's connection string. For example:
+Use the [az iot hub device-identity connection-string show](/cli/azure/iot/hub/device-identity/connection-string) command to retrieve a device's connection string. For example:
 
 ```bash
 az iot hub device-identity connection-string show --device-id <DEVICE_NAME> --hub-name <IOT_HUB_NAME>