Merge pull request #5771 from MicrosoftDocs/master637339744543723546

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

Author: ghogen

docs/code-quality/how-to-create-a-custom-rule-set.md

@@ -2,14 +2,14 @@
 title: Create a custom code analysis rule set
 ms.date: 11/02/2018
 ms.topic: how-to
-f1_keywords: 
+f1_keywords:
   - vs.codeanalysis.addremoverulesets
-helpviewer_keywords: 
+helpviewer_keywords:
   - rule sets
 author: mikejo5000
 ms.author: mikejo
 manager: jillfra
-ms.workload: 
+ms.workload:
   - multiple
 ---
 # Customize a rule set
@@ -20,9 +20,9 @@ You can create a custom rule set to meet specific project needs for code analysi
 
 To create a custom rule set, you can open a built-in rule set in the **rule set editor**. From there, you can add or remove specific rules, and you can change the action that occurs when a rule is violated—for example, show a warning or an error.
 
-1. In **Solution Explorer**, select and hold (or right-click) the project and then select **Properties**.
+1. In **Solution Explorer**, right-click the project and then select **Properties**.
 
-2. On the **Properties** pages, go to the **Code Analysis** tab.
+2. On the **Properties** pages, select the **Code Analysis** tab.
 
 ::: moniker range="vs-2017"
 
@@ -51,7 +51,7 @@ To create a custom rule set, you can open a built-in rule set in the **rule set
 
 You can create a new rule set file from the **New File** dialog:
 
-1. Select **File** > **New** > **File**, or select **Ctrl**+**N**.
+1. Select **File** > **New** > **File**, or press **Ctrl**+**N**.
 
 2. In the **New File** dialog box, select the **General** category on the left, and then select **Code Analysis Rule Set**.
 
@@ -64,9 +64,9 @@ You can create a new rule set file from the **New File** dialog:
 > [!NOTE]
 > The following procedure does not apply to .NET Core projects, which don't have a **Code Analysis** property tab.
 
-1. In **Solution Explorer**, select and hold (or right-click) the project and then select **Properties**.
+1. In **Solution Explorer**, right-click the project and then select **Properties**.
 
-2. On the **Properties** pages, go to the **Code Analysis** tab.
+2. On the **Properties** pages, select the **Code Analysis** tab.
 
 ::: moniker range="vs-2017"
 

docs/code-quality/how-to-generate-code-metrics-data.md

@@ -2,14 +2,14 @@
 title: Generate code metrics from the IDE or command line
 ms.date: 11/02/2018
 ms.topic: how-to
-helpviewer_keywords: 
+helpviewer_keywords:
   - code metrics data
   - code metrics results
   - code metrics [Visual Studio]
 author: mikejo5000
 ms.author: mikejo
 manager: jillfra
-ms.workload: 
+ms.workload:
   - multiple
 ---
 # How to: Generate code metrics data
@@ -66,23 +66,23 @@ You can configure the thresholds at which the code metrics rules fire.
 
 ## Calculate Code Metrics menu command
 
-Generate code metrics for one or all of your open projects in the IDE by going to the **Analyze** > **Calculate Code Metrics** menu.
+Generate code metrics for one or all of your open projects in the IDE by using the **Analyze** > **Calculate Code Metrics** menu.
 
 ### Generate code metrics results for an entire solution
 
 You can generate code metrics results for an entire solution in any of the following ways:
 
 - From the menu bar, select **Analyze** > **Calculate Code Metrics** > **For Solution**.
 
-- In **Solution Explorer**, select and hold (or right-click) the solution and then select **Calculate Code Metrics**.
+- In **Solution Explorer**, right-click the solution and then select **Calculate Code Metrics**.
 
 - In the **Code Metrics Results** window, select the **Calculate Code Metrics for Solution** button.
 
 The results are generated and the **Code Metrics Results** window is displayed. To view the results details, expand the tree in the **Hierarchy** column.
 
 ### Generate code metrics results for one or more projects
 
-1. In **Solution Explorer**, choose one or more projects.
+1. In **Solution Explorer**, select one or more projects.
 
 1. From the menu bar, select **Analyze** > **Calculate Code Metrics** > **For Selected Project(s)**.
 

docs/code-quality/how-to-run-code-analysis-manually-for-managed-code.md

@@ -2,25 +2,25 @@
 title: How to run code analysis manually for managed code
 ms.date: 11/04/2019
 ms.topic: how-to
-helpviewer_keywords: 
+helpviewer_keywords:
   - code analysis, running
   - run code analysis
 ms.assetid: 5086d228-f92e-4515-9708-c5b89b9e9a03
 author: mavasani
 ms.author: mikejo
 manager: jillfra
-ms.workload: 
+ms.workload:
   - dotnet
 ---
 # How to: Run code analysis manually for managed code (requires Visual Studio 2019 version 16.5 or later)
 By default, .NET Compiler Platform ("Roslyn") code analyzers analyze your C# or Visual Basic code as you type by doing live analysis, as well as during build. Hence, you would normally not require to manually trigger code analysis. However, there are some scenarios where you may want to manually trigger code analysis:
 
 - By default, live code analysis executes analyzers only for open files in Visual Studio. However, you may be interested in viewing code analysis warnings for all files in a specific project or solution. If so, you would want to trigger code analysis once on a project or a solution. Alternatively, you can enable continuous live code analysis to execute on entire solution. For more information, see [How to: Configure live code analysis scope for managed code](./configure-live-code-analysis-scope-managed-code.md).
-- You may prefer on-demand code analysis execution workflow over continuous live analysis or build-time analysis. If so, you can disable analyzer execution during live analysis and/or build. For information about disabling analysis, see [How to disable source code analysis](disable-code-analysis.md). Then you would want to manually trigger code analysis once on a project or a solution. 
+- You may prefer on-demand code analysis execution workflow over continuous live analysis or build-time analysis. If so, you can disable analyzer execution during live analysis and/or build. For information about disabling analysis, see [How to disable source code analysis](disable-code-analysis.md). Then you would want to manually trigger code analysis once on a project or a solution.
 
 ### Run code analysis manually
 
-1. In **Solution Explorer**, choose the project.
+1. In **Solution Explorer**, select the project.
 
 2. On the **Analyze** menu, select **Run Code Analysis on** *Project Name*.
 

docs/code-quality/in-source-suppression-overview.md

@@ -44,7 +44,7 @@ In C++/CLI, use the macros CA\_SUPPRESS\_MESSAGE or CA\_GLOBAL\_SUPPRESS_MESSAGE
 
 ## SuppressMessage attribute
 
-When you select **Suppress** from the context or right-click (or select and hold) menu of a code analysis warning in the **Error List**, a <xref:System.Diagnostics.CodeAnalysis.SuppressMessageAttribute> attribute is added either in your code or to the project's global suppression file.
+When you select **Suppress** from the context or right-click menu of a code analysis warning in the **Error List**, a <xref:System.Diagnostics.CodeAnalysis.SuppressMessageAttribute> attribute is added either in your code or to the project's global suppression file.
 
 The <xref:System.Diagnostics.CodeAnalysis.SuppressMessageAttribute> attribute has the following format:
 

docs/code-quality/install-fxcop-analyzers.md

@@ -2,12 +2,12 @@
 title: Install FxCop analyzers
 ms.date: 08/03/2018
 ms.topic: how-to
-helpviewer_keywords: 
+helpviewer_keywords:
   - fxcop analyzers
 author: mikejo5000
 ms.author: mikejo
 manager: jillfra
-ms.workload: 
+ms.workload:
   - dotnet
 ---
 # Install FxCop analyzers in Visual Studio
@@ -22,7 +22,7 @@ You can install these FxCop analyzers either as a NuGet package or as a VSIX ext
 
 In Visual Studio 2019 version 16.3 and later, you can install the [Microsoft.CodeAnalysis.FxCopAnalyzers](https://www.nuget.org/packages/Microsoft.CodeAnalysis.FxCopAnalyzers) NuGet package directly from the project's Code Analysis properties page:
 
-1. Right-click (or select and hold) on the project node in **Solution Explorer**, select **Properties**, and then go to the **Code Analysis** tab.
+1. Right-click on the project node in **Solution Explorer**, select **Properties**, and then select the **Code Analysis** tab.
 
    ![Install FxCop analyzers package from properties page in Visual Studio](media/install-fxcop-properties-page.png)
 
@@ -66,7 +66,7 @@ Use the following guidelines to determine which version of the FxCop analyzers p
 
 | Visual Studio version | FxCop analyzer package version |
 | - | - |
-| Visual Studio 2019 (all versions) | [latest](https://www.nuget.org/packages/Microsoft.CodeAnalysis.FxCopAnalyzers/) | 
+| Visual Studio 2019 (all versions) | [latest](https://www.nuget.org/packages/Microsoft.CodeAnalysis.FxCopAnalyzers/) |
 | Visual Studio 2017 version 15.9 | [2.9.10](https://www.nuget.org/packages/Microsoft.CodeAnalysis.FxCopAnalyzers/2.9.10) |
 | Visual Studio 2017 version 15.5 to 15.8 | [2.6.4](https://www.nuget.org/packages/Microsoft.CodeAnalysis.FxCopAnalyzers/2.6.4) |
 | Visual Studio 2017 version 15.3 to 15.4 | [2.3.0-beta1](https://www.nuget.org/packages/Microsoft.CodeAnalysis.FxCopAnalyzers/2.3.0-beta1) |

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

@@ -22,11 +22,11 @@ You can do much of the customization of analyzer diagnostics from **Solution Exp
 
 ![Analyzers node in Solution Explorer](media/analyzers-expanded-in-solution-explorer.png)
 
-You can view the properties of a diagnostic, including its description and default severity, in the **Properties** window. To view the properties, right-click (or select and hold) on the rule and select **Properties**, or select the rule and then select **Alt**+**Enter**.
+You can view the properties of a diagnostic, including its description and default severity, in the **Properties** window. To view the properties, right-click the rule and select **Properties**, or select the rule and then press **Alt**+**Enter**.
 
 ![Diagnostic properties in Properties window](media/analyzer-diagnostic-properties.png)
 
-To see online documentation for a diagnostic, right-click (or select and hold) on the diagnostic and select **View Help**.
+To see online documentation for a diagnostic, right-click the diagnostic and select **View Help**.
 
 The icons next to each diagnostic in **Solution Explorer** correspond to the icons you see in the rule set when you open it in the editor:
 
@@ -219,7 +219,7 @@ Visual Studio provides a convenient way to configure a rule's severity from the
 
 Visual Studio also provides a convenient way to configure a rule's severity from the error list context menu.
 
-1. After a violation occurs, right-click (or select and hold) the diagnostic entry in the error list.
+1. After a violation occurs, right-click the diagnostic entry in the error list.
 
 2. From the context menu, select **Set severity**.
 
@@ -236,12 +236,12 @@ Visual Studio also provides a convenient way to configure a rule's severity from
 
 ### Set rule severity from Solution Explorer
 
-1. In Solution Explorer, select **References** > **Analyzers** (or **Dependencies** > **Analyzers** for .NET Core projects).
+1. In Solution Explorer, expand **References** > **Analyzers** (or **Dependencies** > **Analyzers** for .NET Core projects).
 
 2. Expand the assembly that contains the rule you want to set severity for.
 
 ::: moniker range=">=vs-2019"
-3. Right-click (or select and hold) the rule and select **Set severity**. In the context menu, choose one of the severity options.
+3. Right-click the rule and select **Set severity**. In the context menu, choose one of the severity options.
 
    Visual Studio adds an entry to the EditorConfig file to configure the rule to the requested level. If your project uses a ruleset file instead of an EditorConfig file, the severity entry is added to the ruleset file.
 
@@ -250,7 +250,7 @@ Visual Studio also provides a convenient way to configure a rule's severity from
 ::: moniker-end
 
 ::: moniker range="vs-2017"
-3. Right-click (or select and hold) the rule and select **Set Rule Set Severity**. In the context menu, choose one of the severity options.
+3. Right-click the rule and select **Set Rule Set Severity**. In the context menu, choose one of the severity options.
 
    The severity for the rule is saved in the active rule set file.
 ::: moniker-end
@@ -261,7 +261,7 @@ Visual Studio also provides a convenient way to configure a rule's severity from
 
 1. Open the the active rule set file in one of the following ways:
 
-- In **Solution Explorer**, double click the file, right-click (or select and hold) **References** > **Analyzers** node, and select **Open Active Rule Set**.
+- In **Solution Explorer**, double click the file, right-click **References** > **Analyzers** node, and select **Open Active Rule Set**.
 - On the **Code Analysis** property page for the project, select **Open** .
 
   If this is the first time you're editing the rule set, Visual Studio makes a copy of the default rule set file, names it *\<projectname>.ruleset*, and adds it to your project. This custom rule set also becomes the active rule set for your project.
@@ -330,13 +330,13 @@ There are multiple ways to suppress rule violations:
 
 - From the **code editor**
 
-  Place the cursor in the line of code with the violation and select **Ctrl**+**Period (.)** to open the **Quick Actions** menu. Select **Suppress CAXXXX** > **in Source/in Suppression File**.
+  Place the cursor in the line of code with the violation and press **Ctrl**+**Period (.)** to open the **Quick Actions** menu. Select **Suppress CAXXXX** > **in Source/in Suppression File**.
 
   ![Suppress diagnostic from quick actions menu](media/suppress-diagnostic-from-editor.png)
 
 - From the **Error List**
 
-  Choose the rules you want to suppress, and then right-click (or select and hold) and select **Suppress** > **In Source/In Suppression File**.
+  Select the rules you want to suppress, and then right-click and select **Suppress** > **In Source/In Suppression File**.
 
   - If you suppress **In Source**, the **Preview Changes** dialog opens and shows a preview of the C# [#pragma warning](/dotnet/csharp/language-reference/preprocessor-directives/preprocessor-pragma-warning) or Visual Basic [#Disable warning](/dotnet/visual-basic/language-reference/directives/directives) directive that's added to the source code.
 

docs/code-quality/working-in-the-code-analysis-rule-set-editor.md

@@ -32,7 +32,7 @@ The editor displays the rules in a tree structure that groups the rules by a rul
    > [!TIP]
    > You can change how rules are grouped in the **Group by** drop-down.
 
-- In the **Action** field of a group, specify the action to apply to all rules in the group.
+- Click the **Action** field of a group, specify the action to apply to all rules in the group.
 
 - Select or clear the check box for an individual rule. When you select the check box for a rule, the rule is set to the **Warning** action.
 

docs/xml-tools/how-to-create-an-xml-document-based-on-an-xsd-schema.md

@@ -37,7 +37,7 @@ Also, note that `xs:base64Binary` content will be generated only if enumerations
 
 1. Follow the steps in [How to: Create and edit an XSD schema file](../xml-tools/how-to-create-and-edit-an-xsd-schema-file.md).
 
-2. In the [XML Schema Explorer](../xml-tools/xml-schema-explorer.md), select and hold (or right-click) the `PurchaseOrder` global element, and then select **Generate Sample XML**.
+2. In the [XML Schema Explorer](../xml-tools/xml-schema-explorer.md), right-click the `PurchaseOrder` global element, and then select **Generate Sample XML**.
 
      When you select this option, the PurchaseOrder.*xml* file with the following sample XML content will be generated and opened in the XML editor: