Repo sync for protected branch

docs/debugger/configure-the-windows-firewall-for-remote-debugging.md

@@ -1,7 +1,7 @@
 ---
 title: Configure Windows Firewall for remote debugging
 description: Configure Windows Firewall for remote debugging. Configure ports for remote debugging. Troubleshoot the remote debugging connection.
-ms.date: 04/24/2024
+ms.date: 09/04/2025
 ms.topic: how-to
 author: mikejo5000
 ms.author: mikejo
@@ -94,28 +94,30 @@ If you select **Use Managed Compatibility Mode** under **Tools** > **Options** >
 
 ::: moniker-end
 
+## Ports for IPsec and IIS
+
 If your domain policy requires network communication to be performed through Internet Protocol Security (IPsec), you must open additional ports on both the Visual Studio and remote computers. To debug on a remote Internet Information Services (IIS) web server, open port 80 on the remote computer.
 
 |**Ports**|**Incoming/Outgoing**|**Protocol**|**Description**|
 |-|-|-|-|
 |500, 4500|Outgoing|UDP|Required if your domain policy requires network communication to be performed through IPsec.|
-|80|Outgoing|TCP|Required for web server debugging.|
+|80|Outgoing|TCP|Required on the remote computer for web server debugging.|
 
 To allow specific apps through the Windows Firewall, see [Configure remote debugging through Windows Firewall](#allow-the-remote-debugger-through-windows-firewall).
 
 ## Allow the remote debugger through Windows Firewall
 
-When you [configure the remote debugger](../debugger/remote-debugging.md#bkmk_setup), the configuration software should open the correct ports. However, in some scenarios you might need to manually allow the remote debugger through the firewall.
+When you [configure the remote debugger](../debugger/remote-debugging.md#bkmk_setup), the configuration software should open the correct ports on the remote computer. However, in some scenarios you might need to manually allow the remote debugger through the firewall.
 
 To allow the remote debugger through Windows Firewall:
 
 1. In Windows **Start** menu, search for and open **Windows Firewall**, or **Windows Defender Firewall**.
 
 1. Select **Allow an app through Windows Firewall**.
 
-1. If **Remote Debugger** or **Visual Studio Remote Debugger** doesn't appear under **Allowed apps and features**, select **Change settings**, and then select **Allow another app**.
+1. If **Remote Debugger** or **Visual Studio Remote Debugger** doesn't appear under **Allowed apps and features**, select **Allow another app**, or select **Change settings** and then **Allow another app**.
 
-1. If the remote debugger app still isn't listed in the **Add an app** dialog, select **Browse**, and navigate to *\<Visual Studio installation directory\>\\Common7\\IDE\\Remote Debugger\\\<x86*, *x64*, or *Appx*\>, depending on the appropriate architecture for your app. Select *msvsmon.exe*, and then select **Add**.
+1. If the remote debugger app still isn't listed in the **Add an app** dialog, select **Browse**, and navigate to *\<Visual Studio installation directory\>\\Common7\\IDE\\Remote Debugger\\\<x86*, *x64*, or *Appx*\>, depending on the appropriate architecture for your app. Select *msvsmon.exe*, and then select **Open**.
 
 1. In the **Apps** list, select the **Remote Debugger** that you just added. Select **Network types**, and then select one or more network types, including the network type for the remote connection.
 

docs/debugger/error-remote-machine-does-not-appear-in-a-remote-connections-dialog.md

@@ -1,7 +1,7 @@
 ---
-description: "If the remote machine does not appear in the Remote Connections dialog, check the following common causes."
-title: "Remote machine does not appear in a Remote Connections dialog"
-ms.date: "11/04/2016"
+description: "If the remote machine doesn't appear in the Remote Connections dialog, check the following common causes."
+title: "Remote machine doesn't appear in a Remote Connections dialog"
+ms.date: "09/04/2025"
 ms.topic: "error-reference"
 dev_langs:
   - "CSharp"
@@ -13,21 +13,21 @@ ms.author: "mikejo"
 manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
-# Error: Remote machine does not appear in a Remote Connections dialog
+# Error: Remote machine doesn't appear in a Remote Connections dialog
 
-If the remote machine does not appear in the Remote Connections dialog, check the following common causes.
+If the remote machine doesn't appear in the Remote Connections dialog, check the following common causes.
 
 ::: moniker range="vs-2019"
-If you are using managed compatibility mode, please check the Visual Studio 2010 documentation: [Troubleshooting Remote Debugging - Visual Studio 2010](/previous-versions/visualstudio/visual-studio-2010/2ys11ead(v=vs.100)).
+If you're using managed compatibility mode, please check the Visual Studio 2010 documentation: [Troubleshooting Remote Debugging - Visual Studio 2010](/previous-versions/visualstudio/visual-studio-2010/2ys11ead(v=vs.100)).
 ::: moniker-end
 
 ### Common causes for this error
 
 - The remote machine is running on a machine that is in a different subnet. To fix this, manually type the machine name or IP address in the Qualifier dialog
 
-- The remote debugger is not running on the remote machine. To fix this, start the remote debugger.
+- The remote debugger isn't running on the remote machine. To fix this, start the remote debugger.
 
-- The firewall is blocking communication between Visual Studio and the remote machine. To fix this, configure your firewall to allow Visual Studio and the remote debugger (msvsmon) to communicate.
+- The firewall is blocking communication between Visual Studio and the remote machine. To fix this, configure your firewall to allow Visual Studio and the remote debugger (msvsmon) to communicate. For more information, see [Configure Windows Firewall for remote debugging](../debugger/error-remote-machine-does-not-appear-in-a-remote-connections-dialog.md).
 
 - Antivirus software is blocking communication between Visual Studio and the remote machine. To fix this, configure antivirus software to allow Visual Studio and the remote debugger (msvsmon) to communicate.
 

docs/ide/how-to-save-and-open-files-with-encoding.md

@@ -52,7 +52,7 @@ Follow these steps to save your file with encoding:
 
 Starting in Visual Studio 2022 version 17.13 Preview 1, you can set the default encoding for saving files.
 
-To set the default, choose **Tools** > **Options** > **Environment**, **Documents**. Next, select **Save files with the following encoding**, and then select the encoding you want as the default.
+To set the default, choose **Tools** > **Options** > **Environment**, **Documents**. Next, select **Save files with a specific encoding**, and then select the encoding you want as the default.
 ::: moniker-end
 
 ## Open encoded file with project

docs/test/quick-start-test-driven-development-with-test-explorer.md

@@ -1,5 +1,5 @@
 ---
-title: Test-driven development tutorial
+title: Test-driven development
 description: Learn how to develop a tested method in C# using Microsoft Test Framework, which you can easily adapt for other languages or test frameworks, such as NUnit.
 ms.date: 5/16/2025
 ms.topic: how-to
@@ -8,7 +8,7 @@ manager: mijacobs
 ms.subservice: test-tools
 author: mikejo5000
 ---
-# Tutorial: Test-driven development using Test Explorer
+# Get started with test-driven development using Test Explorer
 
 Create unit tests to help keep your code working correctly through incremental code changes. There are several frameworks that you can use to write unit tests, including some developed by third parties. Some test frameworks are specialized for testing in different languages or platforms. Test Explorer provides a single interface for unit tests in any of these frameworks. For more information about **Test Explorer**, see [Run unit tests with Test Explorer](run-unit-tests-with-test-explorer.md) and [Test Explorer FAQ](test-explorer-faq.md).
 

docs/test/walkthrough-creating-and-running-unit-tests-for-managed-code.md

@@ -131,8 +131,10 @@ You now have a project with methods you can test. In this article, the tests foc
 
 1. Type **test** in the search box, select **C#** as the language, and then select the C# **MSTest Test Project** for .NET template, and then click **Next**.
 
+   ::: moniker range="vs-2019"
    > [!NOTE]
    > In Visual Studio 2019 version 16.9, the MSTest project template is **Unit Test Project**.
+   ::: moniker-end
 
 1. Name the project **BankTests** and click **Next**.