Review

PatAltimore · PatAltimore · commit 89f31fa550e0 · 2024-06-03T15:06:25.000-07:00
diff --git a/articles/iot-edge/how-to-provision-devices-at-scale-linux-on-windows-tpm.md b/articles/iot-edge/how-to-provision-devices-at-scale-linux-on-windows-tpm.md
@@ -1,12 +1,11 @@
 ---
-title: Create and provision an IoT Edge for Linux on Windows device by using a TPM - Azure IoT Edge | Microsoft Docs 
+title: Create and provision an IoT Edge for Linux on Windows device by using a TPM
 description: Use a simulated TPM on a Linux on Windows device to test the Azure device provisioning service for Azure IoT Edge.
 author: PatAltimore
-manager: lizross
 ms.author: patricka
 ms.reviewer: fcabrera
-ms.date: 02/09/2022
-ms.topic: conceptual
+ms.date: 06/03/2024
+ms.topic: how-to
 ms.service: iot-edge
 ms.custom: linux-related-content
 services: iot-edge
@@ -129,7 +128,7 @@ Simulated TPM samples:
    Provision-EflowVM -provisioningType "DpsTpm" -scopeId "SCOPE_ID_HERE"
    ```
    
-   If you have enrolled the device using a custom **Registration Id**, you must specify that registration ID as well when provisioning:
+   If you enrolled the device using a custom **Registration Id**, you must specify that registration ID as well when provisioning:
    
    ```powershell
    Provision-EflowVM -provisioningType "DpsTpm" -scopeId "SCOPE_ID_HERE" -registrationId "REGISTRATION_ID_HERE"
diff --git a/articles/iot-edge/how-to-provision-devices-at-scale-linux-on-windows-x509.md b/articles/iot-edge/how-to-provision-devices-at-scale-linux-on-windows-x509.md
@@ -1,10 +1,10 @@
 ---
-title: Create and provision IoT Edge devices using X.509 certificates on Linux on Windows - Azure IoT Edge | Microsoft Docs
+title: Create and provision Azure IoT Edge devices using X.509 certificates on Linux on Windows
 description: Use X.509 certificate attestation to test provisioning devices at scale for Azure IoT Edge with device provisioning service
 author: PatAltimore
 ms.author: patricka
-ms.date: 11/15/2022
-ms.topic: conceptual
+ms.date: 06/03/2024
+ms.topic: how-to
 ms.service: iot-edge
 ms.custom: linux-related-content
 services: iot-edge
@@ -58,7 +58,7 @@ To create test certificates, follow the steps in [Create demo certificates to te
 * `<WRKDIR>\certs\iot-edge-device-identity-<name>-full-chain.cert.pem`
 * `<WRKDIR>\private\iot-edge-device-identity-<name>.key.pem`
 
-You need both these certificates on the IoT Edge device. If you're going to use individual enrollment in DPS, then you will upload the .cert.pem file. If you're going to use group enrollment in DPS, then you also need an intermediate or root CA certificate in the same certificate chain of trust to upload. If you're using demo certs, use the `<WRKDIR>\certs\azure-iot-test-only.root.ca.cert.pem` certificate for group enrollment.
+You need both these certificates on the IoT Edge device. If you're going to use individual enrollment in DPS, then you upload the .cert.pem file. If you're going to use group enrollment in DPS, then you also need an intermediate or root CA certificate in the same certificate chain of trust to upload. If you're using demo certs, use the `<WRKDIR>\certs\azure-iot-test-only.root.ca.cert.pem` certificate for group enrollment.
 
 <!-- Create a DPS enrollment using X.509 certificates H2 and content -->
 [!INCLUDE [iot-edge-create-dps-enrollment-x509.md](includes/iot-edge-create-dps-enrollment-x509.md)]
@@ -96,7 +96,7 @@ You can verify that the group enrollment that you created in device provisioning
 
 ---
 
-1. Log in to your IoT Edge for Linux on Windows virtual machine using the following command in your PowerShell session:
+1. Sign in to your IoT Edge for Linux on Windows virtual machine using the following command in your PowerShell session:
 
    ```powershell
    Connect-EflowVm
@@ -134,7 +134,7 @@ You can verify that the group enrollment that you created in device provisioning
     >
     >This error is expected on a newly provisioned device because the IoT Edge Hub module isn't running. To resolve the error, in IoT Hub, set the modules for the device and create a deployment. Creating a deployment for the device starts the modules on the device including the IoT Edge Hub module.
 
-When you create a new IoT Edge device, it will display the status code `417 -- The device's deployment configuration is not set` in the Azure portal. This status is normal, and means that the device is ready to receive a module deployment.
+When you create a new IoT Edge device, it displays the status code `417 -- The device's deployment configuration is not set` in the Azure portal. This status is normal, and means that the device is ready to receive a module deployment.
 
 <!-- Uninstall IoT Edge for Linux on Windows H2 and content -->
 [!INCLUDE [uninstall-iot-edge-linux-on-windows.md](includes/iot-edge-uninstall-linux-on-windows.md)]
diff --git a/articles/iot-edge/how-to-provision-single-device-linux-on-windows-symmetric.md b/articles/iot-edge/how-to-provision-single-device-linux-on-windows-symmetric.md
@@ -1,12 +1,12 @@
 ---
-title: Create and provision an IoT Edge for Linux on Windows device using symmetric keys - Azure IoT Edge | Microsoft Docs
+title: Create and provision an Azure IoT Edge for Linux on Windows device using symmetric keys
 description: Create and provision a single IoT Edge for Linux on Windows device in IoT Hub using manual provisioning with symmetric keys
 author: PatAltimore
 ms.service: iot-edge
 ms.custom: linux-related-content
 services: iot-edge
-ms.topic: conceptual
-ms.date: 11/15/2022
+ms.topic: how-to
+ms.date: 06/03/2024
 ms.author: patricka
 ---
 
@@ -57,7 +57,7 @@ This article covers registering your IoT Edge device and installing IoT Edge for
 
 You're ready to set up your device with its cloud identity and authentication information.
 
-To provision your device using symmetric keys, you will need your device's **connection string**.
+To provision your device using symmetric keys, you need your device's **connection string**.
 
 Run the following command in an elevated PowerShell session on your target device. Replace the placeholder text with your own values.
 
@@ -71,7 +71,7 @@ For more information about the `Provision-EflowVM` command, see [PowerShell func
 
 Verify that IoT Edge for Linux on Windows was successfully installed and configured on your IoT Edge device.
 
-1. Log in to your IoT Edge for Linux on Windows virtual machine using the following command in your PowerShell session:
+1. Sign in to your IoT Edge for Linux on Windows virtual machine using the following command in your PowerShell session:
 
    ```powershell
    Connect-EflowVm
@@ -110,7 +110,7 @@ Verify that IoT Edge for Linux on Windows was successfully installed and configu
     >This error is expected on a newly provisioned device because the IoT Edge Hub module isn't running. To resolve the error, in IoT Hub, set the modules for the device and create a deployment. Creating a deployment for the device starts the modules on the device including the IoT Edge Hub module.
 
 
-When you create a new IoT Edge device, it will display the status code `417 -- The device's deployment configuration is not set` in the Azure portal. This status is normal, and means that the device is ready to receive a module deployment.
+When you create a new IoT Edge device, it displays the status code `417 -- The device's deployment configuration is not set` in the Azure portal. This status is normal, and means that the device is ready to receive a module deployment.
 
 <!-- Uninstall IoT Edge for Linux on Windows H2 and content -->
 [!INCLUDE [uninstall-iot-edge-linux-on-windows.md](includes/iot-edge-uninstall-linux-on-windows.md)]
diff --git a/articles/iot-edge/how-to-provision-single-device-linux-on-windows-x509.md b/articles/iot-edge/how-to-provision-single-device-linux-on-windows-x509.md
@@ -1,12 +1,12 @@
 ---
-title: Create and provision an IoT Edge for Linux on Windows device using X.509 certificates - Azure IoT Edge | Microsoft Docs
+title: Create and provision an Azure IoT Edge for Linux on Windows device using X.509 certificates
 description: Create and provision a single IoT Edge for Linux on Windows device in IoT Hub using manual provisioning with X.509 certificates
 author: PatAltimore
 ms.service: iot-edge
 ms.custom: linux-related-content
 services: iot-edge
-ms.topic: conceptual
-ms.date: 02/09/2022
+ms.topic: how-to
+ms.date: 06/03/2024
 ms.author: patricka
 ---
 
@@ -61,7 +61,7 @@ This article covers registering your IoT Edge device and installing IoT Edge for
 
 You're ready to set up your device with its cloud identity and authentication information.
 
-To provision your device using X.509 certificates, you will need your **IoT hub name**, **device ID**, and the absolute paths to your **identity certificate** and **private key** on your Windows host machine.
+To provision your device using X.509 certificates, you need your **IoT hub name**, **device ID**, and the absolute paths to your **identity certificate** and **private key** on your Windows host machine.
 
 Have the device identity certificate and its matching private key ready on your target device. Know the absolute path to both files.
 
@@ -77,7 +77,7 @@ For more information about the `Provision-EflowVM` command, see [PowerShell func
 
 Verify that IoT Edge for Linux on Windows was successfully installed and configured on your IoT Edge device.
 
-1. Log in to your IoT Edge for Linux on Windows virtual machine using the following command in your PowerShell session:
+1. Sign in to your IoT Edge for Linux on Windows virtual machine using the following command in your PowerShell session:
 
    ```powershell
    Connect-EflowVm
@@ -115,7 +115,7 @@ Verify that IoT Edge for Linux on Windows was successfully installed and configu
     >
     >This error is expected on a newly provisioned device because the IoT Edge Hub module isn't running. To resolve the error, in IoT Hub, set the modules for the device and create a deployment. Creating a deployment for the device starts the modules on the device including the IoT Edge Hub module.
 
-When you create a new IoT Edge device, it will display the status code `417 -- The device's deployment configuration is not set` in the Azure portal. This status is normal, and means that the device is ready to receive a module deployment.
+When you create a new IoT Edge device, it displays the status code `417 -- The device's deployment configuration is not set` in the Azure portal. This status is normal, and means that the device is ready to receive a module deployment.
 
 <!-- Uninstall IoT Edge for Linux on Windows H2 and content -->
 [!INCLUDE [uninstall-iot-edge-linux-on-windows.md](includes/iot-edge-uninstall-linux-on-windows.md)]
diff --git a/articles/iot-edge/how-to-retrieve-iot-edge-logs.md b/articles/iot-edge/how-to-retrieve-iot-edge-logs.md
@@ -1,11 +1,11 @@
 ---
-title: Retrieve IoT Edge logs - Azure IoT Edge
+title: Retrieve Azure IoT Edge logs
 description: IoT Edge module log retrieval and upload to Azure Blob Storage. 
 author: PatAltimore
 
 ms.author: patricka
-ms.date: 09/01/2022
-ms.topic: conceptual
+ms.date: 06/03/2024
+ms.topic: how-to
 ms.reviewer: veyalla
 ms.service: iot-edge 
 ms.custom: devx-track-azurecli
@@ -29,7 +29,7 @@ While not required, for best compatibility with this feature, the recommended lo
 <{Log Level}> {Timestamp} {Message Text}
 ```
 
-`{Timestamp}` should be formatted as `yyyy-MM-dd HH:mm:ss.fff zzz`, and `{Log Level}` should follow the table below, which derives its severity levels from the [Severity code in the Syslog standard](https://wikipedia.org/wiki/Syslog#Severity_level).
+`{Timestamp}` should be formatted as `yyyy-MM-dd HH:mm:ss.fff zzz`, and `{Log Level}` should use the following table, which derives its severity levels from the [Severity code in the Syslog standard](https://wikipedia.org/wiki/Syslog#Severity_level).
 
 | Value | Severity |
 |-|-|
@@ -79,7 +79,7 @@ This method accepts a JSON payload with the following schema:
 |-|-|-|
 | schemaVersion | string | Set to `1.0` |
 | items | JSON array | An array with `id` and `filter` tuples. |
-| id | string | A regular expression that supplies the module name. It can match multiple modules on an edge device. [.NET Regular Expressions](/dotnet/standard/base-types/regular-expressions) format is expected. In case there are multiple items whose ID matches the same module, only the filter options of the first matching ID will be applied to that module. |
+| id | string | A regular expression that supplies the module name. It can match multiple modules on an edge device. [.NET Regular Expressions](/dotnet/standard/base-types/regular-expressions) format is expected. In case there are multiple items whose ID matches the same module, only the filter options of the first matching ID is applied to that module. |
 | filter | JSON section | Log filters to apply to the modules matching the `id` regular expression in the tuple. |
 | tail | integer | Number of log lines in the past to retrieve starting from the latest. OPTIONAL. |
 | since | string | Only return logs since this time, as an rfc3339 timestamp, UNIX timestamp, or a duration (days (d) hours (h) minutes (m)). For example, a duration for one day, 12 hours, and 30 minutes can be specified as *1 day 12 hours 30 minutes* or *1d 12h 30m*. If both `tail` and `since` are specified, the logs are retrieved using the `since` value first. Then, the `tail` value is applied to the result, and the final result is returned. OPTIONAL. |
@@ -399,7 +399,7 @@ In the Azure portal, invoke the method with the method name `GetTaskStatus` and
     }
 ```
 
-:::image type="content" source="./media/how-to-retrieve-iot-edge-logs/invoke-get-task-status.png" alt-text="Screenshot showing how to invoke direct method GetTaskStatus in Azure portal .":::
+:::image type="content" source="./media/how-to-retrieve-iot-edge-logs/invoke-get-task-status.png" alt-text="Screenshot showing how to invoke direct method GetTaskStatus in Azure portal.":::
 
 ## Next steps
 
