Merge pull request #207903 from atikmapari/Broken-link-fcabrera

Broken link fixed

Author: prmerger-automator[bot]

articles/iot-edge/troubleshoot-iot-edge-for-linux-on-windows-common-errors.md

@@ -20,7 +20,7 @@ The following section addresses the common errors when installing the EFLOW MSI
 - [Azure IoT Edge for Linux on Windows prerequisites](https://aka.ms/AzEFLOW-Requirements)
 - [Nested virtualization for Azure IoT Edge for Linux on Windows](./nested-virtualization.md)
 - [Networking configuration for Azure IoT Edge for Linux on Windows](./how-to-configure-iot-edge-for-linux-on-windows-networking.md)
-- [Azure IoT Edge for Linux on Windows virtual switch creation](/how-to-create-virtual-switch.md)
+- [Azure IoT Edge for Linux on Windows virtual switch creation](./how-to-create-virtual-switch.md)
 - [PowerShell functions for IoT Edge for Linux on Windows](./reference-iot-edge-for-linux-on-windows-functions.md)
 
 > [!div class="mx-tdCol2BreakAll"]
@@ -90,7 +90,7 @@ The following section addresses the common errors related to EFLOW networking an
 
 - [Azure IoT Edge for Linux on Windows networking](./iot-edge-for-linux-on-windows-networking.md)
 - [Networking configuration for Azure IoT Edge for Linux on Windows](./how-to-configure-iot-edge-for-linux-on-windows-networking.md)
-- [Azure IoT Edge for Linux on Windows virtual switch creation](/how-to-create-virtual-switch.md)
+- [Azure IoT Edge for Linux on Windows virtual switch creation](./how-to-create-virtual-switch.md)
 
 > [!div class="mx-tdCol2BreakAll"]
 > | Error | Error Description | Solution |

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

@@ -122,7 +122,7 @@ For more information about EFLOW VM firewall, see [IoT Edge for Linux on Windows
     sudo iptables -L
     ```
 
-To add a firewall rule to the EFLOW VM, you can use the [EFLOW Util - Firewall Rules](https://github.com/Azure/iotedge-eflow/tree/eflow-usbip/eflow-util/firewall-rules) sample PowerShell cmdlets. Also, you can achieve the same rules creation by following these steps:
+To add a firewall rule to the EFLOW VM, you can use the [EFLOW Util - Firewall Rules](https://github.com/Azure/iotedge-eflow/tree/main/eflow-util#get-eflowvmfirewallrules) sample PowerShell cmdlets. Also, you can achieve the same rules creation by following these steps:
 
 1. Start an elevated _PowerShell_ session using **Run as Administrator**.
 1. Connect to the EFLOW virtual machine

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

@@ -183,7 +183,7 @@ Second, if the GPU is correctly assigned, but still not being able to use it ins
 The first step before checking *WSSDAgent* logs is to check if the VM was created and is running. 
 
 1. Start an elevated _PowerShell_ session using **Run as Administrator**.
-1. On Windows Client SKUs, check the [HCS](/virtualization/community/team-blog/2017/20170127-introducing-the-host-compute-service-hcs.md) virtual machines.
+1. On Windows Client SKUs, check the [HCS](/virtualization/community/team-blog/2017/20170127-introducing-the-host-compute-service-hcs) virtual machines.
     ```powershell
     hcsdiag list
     ```
@@ -197,7 +197,7 @@ The first step before checking *WSSDAgent* logs is to check if the VM was create
         VM,                         SavedAsTemplate, 88D7AA8C-0D1F-4786-B4CB-62EFF1DECD92, CmService
     ```
 
-1. On Windows Server SKUs, check the [VMMS](/windows-server/virtualization/hyper-v/hyper-v-technology-overview.md) virtual machines
+1. On Windows Server SKUs, check the [VMMS](/windows-server/virtualization/hyper-v/hyper-v-technology-overview) virtual machines
     ```powershell
     hcsdiag list
     ```