Merge pull request #10624 from MicrosoftDocs/main638753510833209655sync_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/code-quality/in-source-suppression-overview.md

@@ -49,6 +49,7 @@ To suppress violations using the code editor, follow these steps:
 
       :::image type="content" source="media/suppress-diagnostic-from-editor-attribute.png" alt-text="Screenshot that shows in Source (attribute) selection from the Quick Actions Suppress menu." lightbox="media/suppress-diagnostic-from-editor-attribute.png":::
 
+::: moniker range="vs-2019"
 ### Suppress violations using the Error List
 
 To suppress violations using the **Error List** window, follow these steps:
@@ -74,6 +75,7 @@ Diagnostics from live analysis, or IntelliSense, are always up-to-date with curr
    ![Screenshot that shows the Error List source filter.](media/error-list-filter.png)
 
 1. Select the diagnostics you want to suppress and proceed as described previously.
+::: moniker-end
 
 ## Suppress violations using a global suppression file
 
@@ -89,6 +91,7 @@ To suppress violations with a global suppression file by using the code editor,
 
     Visual Studio creates a tab in the code editor containing the new global suppression file.
 
+::: moniker range="vs-2019"
 ### Use a global suppression file from the Error List
 
 To suppress violations with a global suppression file by using the **Error List** window, follow these steps:
@@ -102,6 +105,7 @@ To suppress violations with a global suppression file by using the **Error List*
    ![Screenshot that shows the Preview Changes dialog box with a SuppressMessageAttribute attribute in the suppression file.](media/preview-changes-in-suppression-file.png)
 
 1. Select **Apply** to save the global suppression file.
+::: moniker-end
 
 ## Suppress all current violations
 

docs/code-quality/use-roslyn-analyzers.md

@@ -19,7 +19,13 @@ Each Roslyn analyzer rule, or *diagnostic*, has a default severity and suppressi
 
 ## Severity levels
 
+::: moniker range=">=vs-2022"
+You can configure the severity of analyzer rules in an [EditorConfig file](#set-rule-severity-in-an-editorconfig-file) and from the [light bulb menu](#set-rule-severity-from-the-light-bulb-menu).
+::: moniker-end
+
+::: moniker range="vs-2019"
 In Visual Studio 2019 version 16.3 and later, you can configure the severity of analyzer rules in an [EditorConfig file](#set-rule-severity-in-an-editorconfig-file), from the [light bulb menu](#set-rule-severity-from-the-light-bulb-menu), and from the **Error List** window.
+::: moniker-end
 
 The following table shows the different severity options that you can configure for a diagnostic:
 
@@ -53,7 +59,6 @@ You can set the rule severity using any of the following methods:
 ::: moniker range=">=vs-2022"
 - [EditorConfig](#set-rule-severity-in-an-editorconfig-file)
 - [Light bulb menu](#set-rule-severity-from-the-light-bulb-menu)
-- [Error List window](#set-rule-severity-from-the-error-list-window)
 - [Solution Explorer](#set-rule-severity-from-solution-explorer)
 ::: moniker-end
 
@@ -170,6 +175,7 @@ Visual Studio provides a convenient way to configure a rule's severity from the
 
    If you don't already have an EditorConfig file in the project, Visual Studio creates one for you.
 
+::: moniker range="vs-2019"
 ### Set rule severity from the Error List window
 
 Visual Studio also provides a convenient way to configure a rule's severity from the error list context menu. Follow these steps:
@@ -183,6 +189,7 @@ Visual Studio also provides a convenient way to configure a rule's severity from
    Visual Studio adds an entry to the EditorConfig file to configure the rule to the requested level.
 
    If you don't already have an EditorConfig file in the project, Visual Studio creates one for you.
+::: moniker-end
 
 ### Set rule severity from Solution Explorer
 

docs/debugger/remote-debugging-cpp.md

@@ -18,7 +18,7 @@ ms.subservice: debug-diagnostics
 ---
 # Remote Debugging a C++ Project in Visual Studio
 
-To debug a Visual Studio application on a different computer, install and run the remote tools on the computer where you will deploy your app, configure your project to connect to the remote computer from Visual Studio, and then deploy and run your app.
+To debug a Visual Studio application on a different computer, install and run the remote tools on the computer where you'll deploy your app, configure your project to connect to the remote computer from Visual Studio, and then deploy and run your app.
 
 ![Remote debugger components](../debugger/media/remote-debugger-client-apps.png "Remote_debugger_components")
 
@@ -29,7 +29,7 @@ For information about remote debugging Universal Windows Apps (UWP), see [Debug
 The remote debugger is supported on Windows 7 and newer and versions of Windows Server starting with Windows Server 2008 Service Pack 2. For a complete list of requirements, see [Requirements](../debugger/remote-debugging.md#requirements_msvsmon).
 
 > [!NOTE]
-> Debugging between two computers connected through a proxy is not supported. Debugging over a high latency or low bandwidth connection, such as dialup Internet, or over the Internet across countries/regions is not recommended and may fail or be unacceptably slow.
+> Debugging between two computers connected through a proxy isn't supported. Debugging over a high latency or low bandwidth connection, such as dialup Internet, or over the Internet across countries/regions isn't recommended and may fail or be unacceptably slow.
 
 ## Download and Install the remote tools
 
@@ -40,6 +40,8 @@ The remote debugger is supported on Windows 7 and newer and versions of Windows
 
 ## <a name="BKMK_setup"></a> Set up the remote debugger
 
+After you install the remote debugger, follow these steps.
+
 [!INCLUDE [remote-debugger-configuration](../debugger/includes/remote-debugger-configuration.md)]
 
 > [!NOTE]
@@ -99,7 +101,7 @@ The remote debugger is supported on Windows 7 and newer and versions of Windows
 
 ## Set Up Debugging with Remote Symbols
 
-You should be able to debug your code with the symbols you generate on the Visual Studio computer. The performance of the remote debugger is much better when you use local symbols.
+You should be able to debug your code with the symbols you generate on the Visual Studio computer. The performance of the remote debugger is significantly better when you use local symbols.
 
 If you must use remote symbols, you need to specify the remote symbols in Visual Studio by adding a Windows file share to the symbol search path in **Tools > Options > Debugging > Symbols**.
 

docs/debugger/remote-debugging-csharp.md

@@ -29,7 +29,7 @@ For information about remote debugging Universal Windows Apps (UWP), see [Debug
 The remote debugger is supported on Windows 7 and newer and on versions of Windows Server starting with Windows Server 2008 Service Pack 2. For a complete list of requirements, see [Requirements](../debugger/remote-debugging.md#requirements_msvsmon).
 
 > [!NOTE]
-> Debugging between two computers connected through a proxy is not supported. Debugging over a high latency or low bandwidth connection, such as dialup Internet, or over the Internet across countries/regions is not recommended and may fail or be unacceptably slow.
+> Debugging between two computers connected through a proxy isn't supported. Debugging over a high latency or low bandwidth connection, such as dialup Internet, or over the Internet across countries/regions isn't recommended and may fail or be unacceptably slow.
 
 ## Download and Install the remote tools
 
@@ -40,18 +40,20 @@ The remote debugger is supported on Windows 7 and newer and on versions of Windo
 
 ## <a name="BKMK_setup"></a> Set up the remote debugger
 
+After you install the remote debugger, follow these steps.
+
 [!INCLUDE [remote-debugger-configuration](../debugger/includes/remote-debugger-configuration.md)]
 
 > [!NOTE]
 > If you need to add permissions for additional users, change the authentication mode, or port number for the remote debugger, see [Configure the remote debugger](../debugger/remote-debugging.md#configure_msvsmon).
 
 ## <a name="remote_csharp"></a> Remote debug the project
 
-The debugger cannot deploy Visual C# or Visual Basic desktop applications to a remote machine, but you can still debug them remotely as follows. The following procedure assumes that you want to debug it on a computer named **MJO-DL**, as shown in the illustration below.
+The debugger can't deploy Visual C# or Visual Basic desktop applications to a remote machine, but you can still debug them remotely as follows. The following procedure assumes that you want to debug it on a computer named **MJO-DL**, as shown in the illustration below.
 
 1. Create a WPF project named **MyWpf**.
 
-   If you are trying to remote debug a MAUI app instead of WPF, see [Remote debug a .NET MAUI app on Windows](#remote-debug-a-net-maui-app-on-windows).
+   If you're trying to remote debug a MAUI app instead of WPF, see [Remote debug a .NET MAUI app on Windows](#remote-debug-a-net-maui-app-on-windows).
 
 2. Set a breakpoint somewhere in the code that is easily reached.
 
@@ -86,7 +88,7 @@ The debugger cannot deploy Visual C# or Visual Basic desktop applications to a r
     **MJO-DL:4024** on Visual Studio 2019
     ::: moniker-end
 
-7. Make sure that **Enable native code debugging** is not selected.
+7. Make sure that **Enable native code debugging** isn't selected.
 
 8. Build the project.
 
@@ -95,7 +97,7 @@ The debugger cannot deploy Visual C# or Visual Basic desktop applications to a r
 10. Copy the executable that you just built from your Visual Studio computer to the newly created folder on the remote computer.
 
     > [!CAUTION]
-    > Do not make changes to the code or rebuild (or you must repeat this step). The executable you copied to the remote machine must exactly match your local source and symbols.
+    > Don't make changes to the code or rebuild (or you must repeat this step). The executable you copied to the remote machine must exactly match your local source and symbols.
 
     You can copy the project manually, use XCopy, Robocopy, PowerShell, or other options.