Merge pull request #8728 from microsoft/release-1103-pr

Merge updates for 1.103 (pr) update

Author: ntrogh

docs/debugtest/port-forwarding.md

@@ -9,7 +9,7 @@ Support for port forwarding is built into Visual Studio Code via [Microsoft dev
 
 ## How to use port forwarding
 
-First, you need to have a service you want to forward. If you don't have one yet but do have Node.js installed, you can run this command to start up a server on port 3000:
+First, you need to have a service to forward. If you don't have one yet but do have Node.js installed, you can run this command to start up a server on port 3000:
 
 ```bash
 npx serve
@@ -19,33 +19,34 @@ Then, navigate to the **Ports** view in the Panel region (**Ports: Focus on Port
 
 ![Forward a Port button displayed in the Ports view](images/port-forwarding/ports-view.png)
 
-If you haven't logged in with GitHub before, you'll be prompted to sign in. Then, enter the port you'd like to forward; the default port using the above command is port 3000. Once you do, the port forwarding system starts and the **Ports** view updates to show the port you forwarded and its **Forwarded Address**.
+If you haven't logged in with GitHub before, you'll be prompted to sign in. Then, enter the port you'd like to forward; the default port using the above command is port 3000. Once you do this, port forwarding starts and the **Ports** view updates to show the port you forwarded and its **Forwarded Address**.
 
 ![Port 3000 added to the Ports view](images/port-forwarding/forwarded-port.png)
 
-Hovering over the **Forwarded Address**, you can use the inline actions copy the address, open it in your browser, or open an in-editor preview.
+Hovering over the **Forwarded Address**, you can use the inline actions to copy the address, open it in your browser, or open an in-editor preview.
 
-By default, the forwarded port is **Private**. When you navigate to the URL, you'll be required to sign in with the same GitHub account you used to start the port forwarding process in VS Code. You can change the visibility right-clicking on the port and selecting **Port Visibility > Public**. **Public** ports don't require sign in.
+By default, the forwarded port is **Private**. When you navigate to the URL, you'll be required to sign in with the same GitHub account you used to start the port forwarding process in VS Code. You can change the visibility by right-clicking on the port and selecting **Port Visibility > Public**. **Public** ports don't require sign in.
 
 ## Common questions
 
 ### How do I forward local services if I'm connected to a remote machine?
 
-Currently, port forwarding only works to expose locally-running services. It doesn't work in remote connections yet, although we expect it to in the future.
+Port forwarding currently exposes only locally-running services. Remote connections aren't supported yet, but we plan to add this capability in the future.
 
 Depending on your scenario, you may want to use the VS Code [Remote - Tunnels](https://marketplace.visualstudio.com/items?itemName=ms-vscode.remote-server) extension to tunnel into a remote machine. You can learn more in the [Remote - Tunnels documentation](/docs/remote/tunnels.md).
 
 ### How are forwarded ports secured?
 
-By default, both hosting and connecting to a tunnel requires authentication with the same GitHub or Microsoft account on each end. In both cases, VS Code makes outbound connections to a service hosted in Azure; no firewall changes are generally necessary, and VS Code doesn't set up any network listeners.
+By default, both hosting and connecting to a tunnel require authentication with the same GitHub or Microsoft account on each end. In both cases, VS Code makes outbound connections to a service hosted in Azure; no firewall changes are generally necessary, and VS Code doesn't set up any network listeners.
 
-However, if you've opened a **Public** port, any user with your link can access the forwarded service. You should be careful to avoid hosting any confidential information or insecure services over such ports.
+> [!CAUTION]
+> If you've opened a **Public** port, any user with your link can access the forwarded service. Avoid hosting confidential information or insecure services on public ports.
 
-You can learn more about the security of the underlying dev tunnels service in its [documentation](https://learn.microsoft.com/azure/developer/dev-tunnels/security).
+Learn more about the [security of the underlying dev tunnels service](https://learn.microsoft.com/azure/developer/dev-tunnels/security).
 
 ### What limits are there on port forwarding?
 
-There are limits to both the amount of bandwidth used and the number of active machines that can be used in port forwarding, which are subject to change over time. Read more about tunnel usage limits in the [Remote-Tunnels](https://aka.ms/vscode-dev-tunnel-limit) documentation.
+There are limits to both the amount of bandwidth used and the number of active machines that can be used in port forwarding, which are subject to change over time. Read more about [tunnel usage limits](https://aka.ms/vscode-dev-tunnel-limit).
 
 ### Can I configure policies across my organization?