Merge pull request #10719 from MicrosoftDocs/main638805351076862125sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

docs/debugger/how-to-start-spy-increment.md

@@ -1,48 +1,49 @@
 ---
-title: Start the Spy++ tool to debug a solution
+title: Start the Spy++ Tool to Debug a Solution
 description: Explore the Spy++ tool in Visual Studio for debugging a solution and start the tool from the integrated development environment (IDE) or from a command prompt.
-ms.date: 02/05/2024
+ms.date: 04/17/2025
 ms.topic: how-to
 helpviewer_keywords: 
   - Spy++, starting
 author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: debug-diagnostics
+#customer intent: As a developer, I want to use the Spy++ tool in Visual Studio so I can debug my solution.
 ---
 
 # Start Spy++
 
 You can start Spy++ either from Visual Studio or at a command prompt.
 
- When you start Spy++, if a message is displayed to ask permission to make changes to the computer, select **Yes**.
+When you start Spy++, if a message appears requesting permission to make changes to the computer, select **Yes**.
 
 > [!NOTE]
-> You can run only one instance of Spy++. If you try to start a second instance, it just causes the currently running instance to get the focus.
+> You can run only one instance of Spy++. If you try to start a second instance, the current running instance gets the focus.
 
 ## Prerequisites
 
-Spy++ requires the following components. You can select these components from the Visual Studio Installer by selecting the **Individual Components** tab, and then selecting the following components.
+Spy++ requires the following components. You can select these components from the Visual Studio Installer by selecting the **Individual Components** tab, and then selecting the following components:
 
-* Under Debugging and testing, select **C++ profiling tools**
-* Under Development activities, select **C++ core features**
+* Under **Debugging and testing**, select **C++ profiling tools**.
+* Under **Development activities**, select **C++ core features**.
 
-If you made any changes, follow the prompts to install these components.
+If you make any changes in the Visual Studio Installer, follow the prompts to complete installation of these components.
 
 ## Start Spy++ from Visual Studio
 
 On the **Tools** menu, select **Spy++**.
 
-Because Spy++ runs independently, after you start it you can close Visual Studio.
+Because Spy++ runs independently, after you start the tool, you can close Visual Studio.
 
 > [!NOTE]
-> When you log messages with Spy++, it might cause the operating system to perform more slowly.
+> When you log messages with Spy++, you might notice the operating system performing more slowly.
 
 ## Start Spy++ at a command prompt
 
-1. In a Command Prompt window, change directories to the folder that contains spyxx.exe. Typically, the path to this folder is ..\\*Visual Studio installation folder*\Common7\Tools\\.
+1. Open a Command Prompt window, and change directories to the folder that contains the *spyxx.exe* file. Typically, the path to this folder is *..\\\<Visual Studio installation folder>\Common7\Tools\\*.
 
-2. Enter *spyxx.exe* or, for the 64-bit version, *spyxx_amd64.exe*.
+1. Enter *spyxx.exe* or, for the 64-bit version, enter *spyxx_amd64.exe*.
 
 For more information on the 32-bit and 64-bit version of Spy++, see [64-bit operating systems](introducing-spy-increment.md#64-bit-operating-systems).
 

docs/ide/not-in-toc/default.md

@@ -112,11 +112,9 @@ manager: mijacobs
 author: mikejo5000
 ms.author: mikejo
 ---
-# Oops! No `F1` help match was found
+# No `F1` help match was found
 
-## Now what?
-
-We're sorry! It looks like we couldn't find what you were looking for. 
+It looks like we couldn't find what you were looking for. 
 
 **Looking for `F1` help on a window, a keyword, or an API name?**
 - **Try your favorite search engine [Recommended]**

docs/test/create-a-unit-test-project.md

@@ -1,44 +1,45 @@
 ---
-title: Create a unit test project
+title: Create a Unit Test Project
 description: Learn how to create a unit test project. The test project can be in the same solution as the production code, or it can be in a separate solution.
-ms.date: 02/22/2023
+ms.date: 04/17/2025
 ms.topic: how-to
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: test-tools
 author: mikejo5000
+#customer intent: As a developer, I want to create unit test projects in Visual Studio so I can run unit tests on project code in my solution.
 ---
 # Create a unit test project
 
-Unit tests often mirror the structure of the code under test. For example, a unit test project would be created for each code project in the product. The test project can be in the same solution as the production code, or it can be in a separate solution. You can have multiple unit test projects in a solution.
+Unit tests often mirror the structure of the code under test. For example, a unit test project might be created for each code project in the product. The test project can be in the same solution as the production code, or it can be in a separate solution. You can have multiple unit test projects in a solution.
 
 > [!NOTE]
-> The location of unit tests for native code and the test project structure can be different than the structure that's described in this article. For more information, see [Writing unit tests for C/C++](writing-unit-tests-for-c-cpp.md).
+> The location of unit tests for native code and the test project structure can be different from the structure described in this article. For more information, see [Writing unit tests for C/C++](writing-unit-tests-for-c-cpp.md).
 
 ## To create a unit test project
 
 1. On the **File** menu, select **New** > **Project**, or press **Ctrl**+**Shift**+**N**.
 
-2. On the **Create a new project** page, type **unit test** into the search box. Select the project template for the test framework that you want to use, for example **MSTest Test Project** or **NUnit Test Project**, and then select **Next**.
+1. On the **Create a new project** page, enter *unit test* in the search box. Select the project template for the test framework that you want to use, such as **MSTest Test Project** or **NUnit Test Project**, and then select **Next**.
 
    ::: moniker range=">=vs-2022"
-   ![Screenshot of test project templates in Visual Studio 2022.](media/vs-2022/test-project-templates.png)
+   :::image type="content" source="media/vs-2022/test-project-templates.png" alt-text="Screenshot of test project templates in Visual Studio 2022.":::
    ::: moniker-end
    ::: moniker range="vs-2019"
-   ![Screenshot of test project templates in Visual Studio 2019.](media/vs-2019/test-project-templates.png)
+   :::image type="content" source="media/vs-2019/test-project-templates.png" alt-text="Screenshot of test project templates in Visual Studio 2019.":::
    ::: moniker-end
 
-3. On the **Configure your new project** page, enter a name for your project, and then select **Create**.
+1. On the **Configure your new project** page, enter a name for your project, and then select **Create**.
 
-4. In your unit test project, add a reference to the code under test. To add a reference to a code project in the same solution:
+1. In your unit test project, add a reference to the code under test. To add a reference to a code project in the same solution:
 
-   1. Select the test project in **Solution Explorer**.
+   1. In **Solution Explorer**, right-click the test project, and select **Add** > **Reference**.
 
-   2. On the **Project** menu, select **Add Reference**.
+   1. In **Reference Manager**, select the **Solution** node under **Projects**.
+   
+   1. Select the code project you want to test, and then select **OK**.
 
-   3. In **Reference Manager**, select the **Solution** node under **Projects**. Select the code project you want to test, and then select **OK**.
-
-   If the code that you want to test is in another location, see [Managing references in a project](../ide/managing-references-in-a-project.md) for information about adding a reference.
+   If the code you want to test is in another location, see [Managing references in a project](../ide/managing-references-in-a-project.md) for information about adding a reference.
 
 ## Related content
 

docs/test/install-third-party-unit-test-frameworks.md

@@ -1,55 +1,64 @@
 ---
-title: Install third-party unit test frameworks
-description: Visual Studio Test Explorer can run tests from any unit test framework that has developed an adapter interface for it.
-ms.date: 12/04/2023
+title: Install Third-party Unit Test Frameworks
+description: Visual Studio Test Explorer can run tests from any unit test framework that has an adapter interface available.
+ms.date: 04/17/2025
 ms.topic: how-to
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: test-tools
 author: mikejo5000
+#customer intent: As a developer, I want to install unit test frameworks from other parties so I can run unit tests from any unit test framework in Visual Studio.
 ---
 # Install unit test frameworks
 
-Visual Studio Test Explorer can run tests from any unit test framework that has developed an adapter interface for it. Installing the framework copies the binaries and adds Visual Studio project templates for the languages it supports. When you create a project with the template, the framework is registered with Test Explorer.
+Visual Studio Test Explorer can run tests from any unit test framework that has an adapter interface available. Installing the framework copies the binaries and adds Visual Studio project templates for the languages it supports. When you create a project with the template, the framework is registered with Test Explorer.
 
 A Visual Studio solution can contain unit test projects that use different frameworks and that are targeted at different languages.
 
-For .NET, [MSTest, NUnit, and xUnit](getting-started-with-unit-testing.md) are the test frameworks provided by Visual Studio which are installed by default. For C++, a different set of test frameworks are provided, such as CTest.
+For .NET, [MSTest, NUnit, and xUnit](getting-started-with-unit-testing.md) are the test frameworks provided by Visual Studio, which are installed by default. For C++, a different set of test frameworks are provided, such as CTest.
 
 ## Acquire frameworks
 
-Install third-party unit test frameworks by using **NuGet Package Manager**.
+Install third-party unit test frameworks by using **NuGet Package Manager**:
 
-1. Right-click on the project that will contain your test code and select **Manage NuGet Packages**.
+1. In **Solution Explorer**, right-click the project for your test code, and select **Manage NuGet Packages**.
 
-2. In **NuGet Package Manager**, search for the test framework you want to install, and then click **Install**.
+1. In **NuGet Package Manager**, search for the test framework you want to install:
 
    ::: moniker range=">=vs-2022"
-   ![NuGet Package Manager in Visual Studio](media/vs-2022/nuget-package-manager.png)
+   :::image type="content" source="media/vs-2022/nuget-package-manager.png" alt-text="Screenshot of NuGet Package Manager in Visual Studio 2022.":::
    ::: moniker-end
    ::: moniker range="vs-2019"
-   ![NuGet Package Manager in Visual Studio](media/vs-2019/nuget-package-manager.png)
+   :::image type="content" source="media/vs-2019/nuget-package-manager.png" alt-text="Screenshot of NuGet Package Manager in Visual Studio 2019.":::
    ::: moniker-end
 
+1. Select the framework and then select **Install**.
+
 ## Update to the latest test adapters
 
 Update to the latest stable test adapter to experience better test discovery and execution. For more information about updates to MSTest, NUnit, and xUnit test adapters, see the [Visual Studio blog](https://devblogs.microsoft.com/visualstudio/test-experience-improvements/).
 
 ### To update to the latest stable test adapter version
 
-1. Open the NuGet Package Manager for your solution by navigating to **Tools** > **NuGet Package Manager** > **Manage NuGet Packages for Solution**.
+1. Open **NuGet Package Manager** for your solution by selecting **Tools** > **NuGet Package Manager** > **Manage NuGet Packages for Solution**.
 
-2. Click on the **Updates** tab and search for MSTest, NUnit, or xUnit test adapters that are installed.
+1. Select the **Updates** tab and search for MSTest, NUnit, or xUnit test adapters that are installed.
 
-3. Select each test adapter, and then select the button to update to a new version.
+1. Select the checkbox next to each test adapter you want to refresh, and then select **Update** to install the latest version of each adapter.
 
    ::: moniker range=">=vs-2022"
-   ![Upgrade Test Adapter](media/vs-2022/install-adapter-upgrade.png)
+
+   :::image type="content" source="media/vs-2022/install-adapter-upgrade.png" alt-text="Screenshot of Upgrade Test Adapter in Visual Studio 2022.":::
+
+   If the **Preview changes** dialog opens, confirm your selection, and select **Apply**. Accept any licensing changes, as needed.
+
    ::: moniker-end
    ::: moniker range="vs-2019"
-   ![Upgrade Test Adapter](media/install-adapter-upgrade.png)
 
-   Choose the **Install** button.
+   :::image type="content" source="media/install-adapter-upgrade.png" alt-text="Screenshot of Upgrade Test Adapter in Visual Studio 2019.":::
+
+   Select **Install**.
+
    ::: moniker-end
 
 ## Related content

subscriptions/product-keys.md

@@ -1,16 +1,16 @@
 ---
-title: Using product keys in Visual Studio subscriptions
+title: Understanding the product keys offered in your Visual Studio subscription
 author: joseb-rdc
 ms.author: amast
 manager: shve
-ms.date: 12/13/2024
+ms.date: 04/17/2025
 ms.topic: conceptual
 description: Obtain and manage your product keys in Visual Studio subscriptions for products that require keys for installation or activation.
 ---
 
-# Using product keys in Visual Studio subscriptions
+# Understanding the product keys offered in your Visual Studio subscription
 
-Visual Studio subscriptions provide access to a wide range of Microsoft products for designing, developing, testing, and demonstrating applications. Some of these products require product keys during installation, and some of those require activation.
+Visual Studio subscriptions provide access to a wide range of Microsoft products for designing, developing, testing, and demonstrating applications. Some of these products require product keys during installation, and some of those products require activation.
 
 Visual Studio subscriptions typically include five product keys for current versions of Windows and Office products, and three keys for older versions.
 Keys often have multiple activations, and many products allow 30-day use without activation. For most subscribers, that's more than enough.