DocuMentor edits

Author: RoseHJM

articles/dev-box/how-to-set-up-dev-tunnels.md

@@ -16,17 +16,17 @@ Use Microsoft Dev Box with Visual Studio Code (VS Code) to create secure, cloud-
 ## Prerequisites
 
 - A dev center configured with at least one project and a dev box pool.
-    - If you don't have a dev center, create one following these steps:[Quickstart: Configure Microsoft Dev Box](quickstart-configure-dev-box-service.md)
+    - If you don't have a dev center, create one following these steps: [Quickstart: Configure Microsoft Dev Box](quickstart-configure-dev-box-service.md)
 - A dev box.
     - If you don't have a dev box, create one following these steps: [Quickstart: Create and connect to a dev box by using the Microsoft Dev Box developer portal](quickstart-create-dev-box.md)
 
 ## Enable Dev Tunnels on a Dev Box Pool
 
-Dev Box Dev Tunnels is a feature that allows developers to connect to their Dev Box using Visual Studio Code (VS Code) through secure tunnels. This feature is particularly useful for developers who want to work remotely or from different locations without needing a full remote desktop connection.
+Dev Box Dev Tunnels is a feature that developers use to connect to their Dev Box by using Visual Studio Code (VS Code) through secure tunnels. This feature is particularly useful for developers who want to work remotely or from different locations without needing a full remote desktop connection.
 
 ### Register the Dev Box Tunnels preview feature
 
-While Dev Box Tunnels is in preview, you must register the feature in your Azure subscription.
+While Dev Box Tunnels is in preview, register the feature in your Azure subscription.
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 
@@ -44,9 +44,9 @@ While Dev Box Tunnels is in preview, you must register the feature in your Azure
 
 ### Enable dev tunnels for a dev box pool
 
-Dev tunnels are enabled on a per-pool basis. To enable tunnels for a dev box pool:
+Enable dev tunnels for each dev box pool. To enable tunnels for a dev box pool:
 
-1. Navigate to the project that contains the dev box pool where you want to enable tunnels.
+1. Go to the project that contains the dev box pool where you want to enable tunnels.
 
 1. On the left menu, select **Manage** > **Dev box pools**.
 
@@ -60,7 +60,7 @@ Dev tunnels are enabled on a per-pool basis. To enable tunnels for a dev box poo
 
 ## Connect to a dev box by using a dev tunnel
 
-Follow these steps to set up a dev tunnel and connect to your dev box using VS Code.
+Follow these steps to set up a dev tunnel and connect to your dev box by using VS Code.
 
 1. Install VS Code extension
 
@@ -80,56 +80,56 @@ Follow these steps to set up a dev tunnel and connect to your dev box using VS C
 
 1. Explore the remote experience in VS Code
 
-   A new VS Code window opens. You can open any folder or workspace on the remote Dev Box using **File** > **Open File/Folder/Workspace** just as you would locally.
+   A new VS Code window opens. You can open any folder or workspace on the remote Dev Box by using **File** > **Open File/Folder/Workspace** just as you would locally.
 
-### Connect to Windows Substem for Linux
+### Connect to Windows Subsystem for Linux
 
-If you have a Windows Subsystem for Linux (WSL) environment on the Dev Box, connect to it using **Remote Explorer**.
+If you have a Windows Subsystem for Linux (WSL) environment on the Dev Box, use **Remote Explorer** to connect to it.
 
-Select WSL targets from the dropdown to see all the WSL distributions. Open any WSL distribution in the current or a new window.
+Select WSL targets from the dropdown to see all the WSL distributions. Open any WSL distribution in the current window or a new window.
 
 :::image type="content" source="media/how-to-set-up-dev-tunnels/dev-box-dev-tunnel-linux.png" alt-text="Screenshot of Visual Studio Code Remote Explorer showing available WSL distributions with the Dev Box WSL target highlighted.":::
 
 
 For more information on the WSL development experience, see [Remote - WSL](https://code.visualstudio.com/docs/remote/wsl) and [Set up a WSL development environment](/windows/wsl/setup/environment).
 
-## Troubleshoot connectivity issues with Copilot
+## Troubleshoot connectivity problems with Copilot
 
-If you're experiencing connectivity issues with your Dev Box, use **Copilot connectivity assist** to diagnose and resolve problems. This feature provides guided troubleshooting through GitHub Copilot and the Dev Box MCP Server to help you identify and fix common connection issues.
+If you have connectivity problems with your Dev Box, use **Copilot connectivity assist** to diagnose and resolve them. This feature provides guided troubleshooting through GitHub Copilot and the Dev Box MCP Server to help you identify and fix common connection problems.
 
 To use Copilot connectivity assist:
 
 1. In VS Code, open the Dev Box extension by selecting the Dev Box icon in the left sidebar.
 
-1. In the **Dev Box Resources** panel, locate the Dev Box you're having trouble connecting to.
+1. In the **Dev Box Resources** panel, find the Dev Box you can't connect to.
 
 1. Select the settings icon (gear) next to the Dev Box, or right-click the Dev Box name to open the context menu.
 
 1. Select **Copilot connectivity assist**.
 
    :::image type="content" source="media/how-to-set-up-dev-tunnels/dev-tunnels-connect-tunnel-copilot.png" alt-text="Screenshot of the Dev Box extension in VS Code showing the context menu with the Copilot connectivity assist option highlighted.":::
 
-1. Follow the guided prompts from Copilot to diagnose and resolve your connectivity issue.
+1. Follow the guided prompts from Copilot to diagnose and resolve your connectivity problem.
 
 > [!NOTE]
 > This menu option runs `devbox_think` from the DevBox MCP Server. You must have the [DevBox MCP Server](overview-what-is-dev-box-mcp-server.md) installed and configured in VS Code to use this feature. Follow the prompts provided by Copilot to complete the troubleshooting process.
 
-Copilot connectivity assist can help with issues such as:
+Copilot connectivity assist can help with problems such as:
 
 - Tunnel connection failures
 - Authentication problems
-- Network configuration issues
+- Network configuration problems
 - Dev Box state problems (stopped, hibernated, or unavailable)
 
 ## Frequently asked questions
 
-- Why do I need to sign-in to the Dev Box before enabling the tunnel?
+- Why do I need to sign in to the Dev Box before enabling the tunnel?
 
-    This step is required to establish a user session for setting up the tunnel. After the initial sign-in, you can just disconnect from the Dev Box. Then you can enable or connect to the tunnel without logging in again, unless the Dev Box is shut down or restarted.
+    You need to sign in to create a user session for setting up the tunnel. After the initial authentication, you can disconnect from the Dev Box. You can enable or connect to the tunnel without signing in again, unless the Dev Box shuts down or restarts.
 
 - Why can't I connect to the Dev Box even if the tunnel is enabled?
 
-    Refresh the Dev Box extension explorer view with the button in the top right corner to check the latest status of the tunnel. If the tunnel is enabled, but you still can't connect, try disabling the tunnel, signing in to the Dev Box, and then re-enabling the tunnel.
+    Refresh the Dev Box extension explorer view by using the button in the upper right corner to check the latest status of the tunnel. If the tunnel is enabled, but you still can't connect, try disabling the tunnel, signing in to the Dev Box, and then re-enabling the tunnel.
 
 ## Related content