Fix corrupted markdown and wrong link in EFLOW troubleshoot guide

- Remove garbled code block closing and duplicate code block
- Fix internal link: point to troubleshoot-iot-edge-for-linux-on-windows-networking.md
  instead of troubleshoot-common-errors.md

Author: jlian

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

@@ -84,14 +84,11 @@ Second, the issue could be related to lack of resources. You can set the *EflowV
     Get-CIMInstance Win32_OperatingSystem | Select FreePhysicalMemory
     ```
 1. Check the available CPU cores. Make sure that *NumberOfLogicalProcessors* is greater than *EflowVmAssignedCPUcores*.
-   ```powershell
-    wmic cpu get NumberOfLogicalProcessors
-    ```ssignedCPUcores*.
    ```powershell
     wmic cpu get NumberOfLogicalProcessors
     ```
 
-Finally, the issue might be related to networking. For more information about EFLOW VM networking issues, see [How to troubleshoot Azure IoT Edge for Linux on Windows networking](./troubleshoot-common-errors.md).
+Finally, the issue might be related to networking. For more information about EFLOW VM networking issues, see [How to troubleshoot Azure IoT Edge for Linux on Windows networking](./troubleshoot-iot-edge-for-linux-on-windows-networking.md).
 
 ## Check the status of the IoT Edge runtime