Merge pull request #277301 from PatAltimore/patricka-freshness

Freshness

Author: JamesJBarnett

articles/iot-edge/iot-edge-for-linux-on-windows-security.md

@@ -34,7 +34,7 @@ The EFLOW virtual machine is made up of two main partitions *rootfs*, and *data*
 
 Because you may need write access to `/etc`, `/home`, `/root`, `/var` for specific use cases, write access for these directories is done by overlaying them onto our data partition specifically to the directory `/var/.eflow/overlays`. The end result of this is that users can write anything to the previous mentioned directories. For more information about overlays, see [*overlayfs*](https://docs.kernel.org/filesystems/overlayfs.html).
 
-[ ![EFLOW CR partition layout](./media/iot-edge-for-linux-on-windows-security/eflow-cr-partition-layout.png) ](./media/iot-edge-for-linux-on-windows-security/eflow-cr-partition-layout.png#lightbox)
+[![EFLOW CR partition layout](./media/iot-edge-for-linux-on-windows-security/eflow-cr-partition-layout.png)](./media/iot-edge-for-linux-on-windows-security/eflow-cr-partition-layout.png#lightbox)
 
 | Partition | Size | Description | 
 | --------- |---------- |------------ |
@@ -48,7 +48,7 @@ Because you may need write access to `/etc`, `/home`, `/root`, `/var` for specif
 | Data | 2 GB to 2 TB | Stateful partition for storing persistent data across updates. Expandable according to the deployment configuration |
 
 >[!NOTE]
->The partition layout represents the logical disk size and does not indicate the physical space the virtual machine will occupy on the host OS disk.​
+>The partition layout represents the logical disk size and does not indicate the physical space the virtual machine will occupy on the host OS disk.
 
 ### Firewall
 

articles/iot-edge/iot-edge-for-linux-on-windows-support.md

@@ -1,9 +1,9 @@
 ---
-title: Supported operating systems, container engines - Azure IoT Edge for Linux on Windows
-description: Learn which operating systems can run Azure IoT Edge for Linux on Windows
+title: Supported platforms for IoT Edge for Linux on Windows
+description: Learn which operating systems and container engines are supported for Azure IoT Edge for Linux on Windows
 author: PatAltimore
-ms.author: fcabrera
-ms.date: 11/15/2022
+ms.author: patricka
+ms.date: 06/05/2024
 ms.topic: conceptual
 ms.service: iot-edge
 ms.custom: linux-related-content
@@ -14,7 +14,7 @@ services: iot-edge
 
 [!INCLUDE [iot-edge-version-1.4](includes/iot-edge-version-1.4.md)]
 
-This article provides details about which systems are supported by IoT Edge for Linux on Windows, whether generally available or in preview. 
+This article provides details about which systems support IoT Edge for Linux on Windows, whether generally available or in preview. 
 
 ## Get support
 

articles/iot-edge/iot-edge-for-linux-on-windows-updates.md

@@ -1,6 +1,6 @@
 ---
 title: Azure IoT Edge for Linux on Windows updates
-description: Overview of Azure IoT Edge for Linux on Windows updates
+description: Overview of Azure IoT Edge for Linux on Windows updates. Learn how to update your IoT Edge for Linux on Windows devices when a new version is available.
 author: PatAltimore
 
 # this is the PM responsible
@@ -9,8 +9,8 @@ ms.service: iot-edge
 ms.custom: linux-related-content
 services: iot-edge
 ms.topic: conceptual
-ms.date: 07/05/2022
-ms.author: fcabrera
+ms.date: 06/05/2024
+ms.author: patricka
 ---
 
 # Update IoT Edge for Linux on Windows
@@ -89,8 +89,8 @@ To migrate between EFLOW 1.1LTS to EFLOW 1.4LTS, use the following steps.
 1. Open an elevated PowerShell session
 1. Start the EFLOW migration
 
-    >[!NOTE]
-    >You can migrate with one single cmdlet by using the `-autoConfirm` flag with the ` Start-EflowMigration` cmdlet. If specified `Confirm-EflowMigration` doesnt needs to be called to proceed with 1.4 migration.
+    > [!NOTE]
+    > You can migrate with one single cmdlet by using the `-autoConfirm` flag with the `Start-EflowMigration` cmdlet. If specified `Confirm-EflowMigration` doesnt needs to be called to proceed with 1.4 migration.
 
     1. If you're using the auto-download migration option run the following cmdlet
         ```powershell

articles/iot-edge/iot-edge-for-linux-on-windows.md

@@ -1,15 +1,14 @@
 ---
-title: What is Azure IoT Edge for Linux on Windows | Microsoft Docs
-description: Overview of you can run Linux IoT Edge modules on Windows 10 devices
+title: What is Azure IoT Edge for Linux on Windows
+description: Overview of running Linux IoT Edge modules with Azure IoT Edge for Linux on Windows. Run containerized Linux workloads alongside Windows applications.
 author: PatAltimore
 
-# this is the PM responsible
 ms.reviewer: fcabrera
 ms.service: iot-edge
 ms.custom: linux-related-content
 services: iot-edge
 ms.topic: conceptual
-ms.date: 11/15/2022
+ms.date: 06/05/2024
 ms.author: patricka
 ---
 
@@ -31,7 +30,7 @@ Azure IoT Edge for Linux on Windows uses the following components to enable Linu
 
 * **Microsoft Update**: Integration with Microsoft Update keeps the Windows runtime components, the CBL-Mariner Linux VM, and Azure IoT Edge up to date. For more information about IoT Edge for Linux on Windows updates, see [Update IoT Edge for Linux on Windows](./iot-edge-for-linux-on-windows-updates.md).
 
-[ ![Windows and the Linux VM run in parallel, while the Windows Admin Center controls both components](./media/iot-edge-for-linux-on-windows/architecture-eflow1-2.png) ](./media/iot-edge-for-linux-on-windows/architecture-eflow1-2.png#lightbox)
+[![Windows and the Linux VM run in parallel, while the Windows Admin Center controls both components](./media/iot-edge-for-linux-on-windows/architecture-eflow1-2.png)](./media/iot-edge-for-linux-on-windows/architecture-eflow1-2.png#lightbox)
 
 Bi-directional communication between Windows process and the Linux virtual machine means that Windows processes can provide user interfaces or hardware proxies for workloads run in the Linux containers.
 

articles/iot-edge/iot-edge-limits-and-restrictions.md

@@ -1,9 +1,9 @@
 ---
-title: Limits and restrictions - Azure IoT Edge | Microsoft Docs 
-description: Description of the limits and restrictions when using IoT Edge.
-author: raisalitch
-ms.author: ralitchf
-ms.date: 11/7/2022
+title: Azure IoT Edge limits and restrictions
+description: Understand the limits and restrictions when using Azure IoT Edge
+author: PatAltimore
+ms.author: patricka
+ms.date: 06/05/2024
 ms.topic: conceptual
 ms.service: iot-edge
 services: iot-edge
@@ -59,7 +59,7 @@ IoT Hub has the following restrictions for IoT Edge automatic deployments:
 
 IoT Edge certificates have the following restrictions:
 
-* The common name (CN) can't be the same as the "hostname" that will be used in the configuration file on the IoT Edge device.
+* The common name (CN) can't be the same as the *hostname* that is used in the configuration file on the IoT Edge device.
 * The name used by clients to connect to IoT Edge can't be the same as the common name used in the edge CA certificate.
 
 For more information, see [Certificates for device security](iot-edge-certs.md).