Merge pull request #5768 from MicrosoftDocs/master637339080028119214

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

Author: ghogen

docs/azure/vs-azure-tools-configure-roles-for-cloud-service.md

@@ -30,7 +30,7 @@ You can configure an Azure cloud service from Solution Explorer in Visual Studio
 
 1. Create or open an Azure cloud service project in Visual Studio.
 
-1. In **Solution Explorer**, right-click (or select and hold) the project, and, from the context menu, select **Properties**.
+1. In **Solution Explorer**, right-click the project, and, from the context menu, select **Properties**.
 
     ![Solution Explorer project context menu](./media/vs-azure-tools-configure-roles-for-cloud-service/solution-explorer-project-context-menu.png)
 
@@ -50,7 +50,7 @@ To improve the performance of your cloud service, you can change the number of i
 
 1. Create or open an Azure cloud service project in Visual Studio.
 
-1. In **Solution Explorer**, expand the project node. Under the **Roles** node, right-click (or select and hold) the role you want to update, and, from the context menu, select **Properties**.
+1. In **Solution Explorer**, expand the project node. Under the **Roles** node, right-click the role you want to update, and, from the context menu, select **Properties**.
 
     ![Solution Explorer Azure role context menu](./media/vs-azure-tools-configure-roles-for-cloud-service/solution-explorer-azure-role-context-menu.png)
 
@@ -80,7 +80,7 @@ By using a different value for each service configuration, you do not have to us
 
 1. Create or open an Azure cloud service project in Visual Studio.
 
-1. In **Solution Explorer**, expand the project node. Under the **Roles** node, right-click (or select and hold) the role you want to update, and, from the context menu, select **Properties**.
+1. In **Solution Explorer**, expand the project node. Under the **Roles** node, right-click the role you want to update, and, from the context menu, select **Properties**.
 
     ![Solution Explorer Azure role context menu](./media/vs-azure-tools-configure-roles-for-cloud-service/solution-explorer-azure-role-context-menu.png)
 
@@ -142,7 +142,7 @@ By using a different value for each service configuration, you do not have to us
 
 1. Create or open an Azure cloud service project in Visual Studio.
 
-1. In **Solution Explorer**, expand the project node. Under the **Roles** node, right-click (or select and hold) the role you want to update, and, from the context menu, select **Properties**.
+1. In **Solution Explorer**, expand the project node. Under the **Roles** node, right-click the role you want to update, and, from the context menu, select **Properties**.
 
     ![Solution Explorer Azure role context menu](./media/vs-azure-tools-configure-roles-for-cloud-service/solution-explorer-azure-role-context-menu.png)
 
@@ -193,7 +193,7 @@ You can add local file system storage for each instance of a role. The data stor
 
 1. Create or open an Azure cloud service project in Visual Studio.
 
-1. In **Solution Explorer**, expand the project node. Under the **Roles** node, right-click (or select and hold) the role you want to update, and, from the context menu, select **Properties**.
+1. In **Solution Explorer**, expand the project node. Under the **Roles** node, right-click the role you want to update, and, from the context menu, select **Properties**.
 
     ![Solution Explorer Azure role context menu](./media/vs-azure-tools-configure-roles-for-cloud-service/solution-explorer-azure-role-context-menu.png)
 
@@ -248,7 +248,7 @@ using (FileStream writeStream = File.Create(filePath))
 
 To view the file created by the code in the previous section, follow these steps:
 
-1. In the Windows notification area, right-click (or select and hold) the Azure icon, and, from the context menu, select **Show Compute Emulator UI**.
+1. In the Windows notification area, right-click the Azure icon, and, from the context menu, select **Show Compute Emulator UI**.
 
     ![Show Azure compute emulator](./media/vs-azure-tools-configure-roles-for-cloud-service/show-compute-emulator.png)
 

docs/azure/vs-azure-tools-connected-services-storage.md

@@ -15,7 +15,7 @@ ms.author: ghogen
 With Visual Studio, you can connect any of the following to Azure Storage by using the **Connected Services** feature:
 
 - .NET Framework console app
-- ASP.NET MVC (.NET Framework) 
+- ASP.NET MVC (.NET Framework)
 - ASP.NET Core
 - .NET Core (including console app, WPF, Windows Forms, class library)
 - .NET Core Worker Role
@@ -39,7 +39,7 @@ The connected service functionality adds all the needed references and connectio
 
 1. Open your project in Visual Studio.
 
-1. In **Solution Explorer**, right-click (or select and hold) the **Connected Services** node, and, from the context menu, and select **Add Connected Service**.
+1. In **Solution Explorer**, right-click the **Connected Services** node, and from the context menu, select **Add Connected Service**.
 
     ![Add Azure connected service](./media/vs-azure-tools-connected-services-storage/add-connected-service.png)
 

docs/azure/vs-azure-tools-debug-cloud-services-virtual-machines.md

@@ -23,7 +23,7 @@ The emulator simulates the Azure Compute service and runs in your local environm
 
 ### To debug your cloud service on your local computer
 
-1. On the menu bar, select **Debug** > **Start Debugging** to run your Azure cloud service project. As an alternative, you can select F5. You’ll see a message that the Compute Emulator is starting. When the emulator starts, the system tray icon confirms it.
+1. On the menu bar, select **Debug** > **Start Debugging** to run your Azure cloud service project. As an alternative, you can press F5. You’ll see a message that the Compute Emulator is starting. When the emulator starts, the system tray icon confirms it.
 
     ![Azure emulator in the system tray](./media/vs-azure-tools-debug-cloud-services-virtual-machines/IC783828.png)
 

docs/azure/vs-azure-tools-emulator-express-debug-run.md

@@ -17,7 +17,7 @@ When you create an Azure project in Azure SDK 2.3 or later, Emulator Express is
 
 1. Create or open an Azure cloud service project in Visual Studio.
 
-1. In Solution Explorer, right-click (or select and hold) the project, and, from the context menu, select **Properties**.
+1. In Solution Explorer, right-click the project, and, from the context menu, select **Properties**.
 
 1. In the projects properties pages, select the **Web** tab.
 

docs/azure/vs-azure-tools-resources-managing-with-cloud-explorer.md

@@ -81,7 +81,7 @@ To view your Azure resources, you can choose either **Resource Types** or **Reso
 
 To navigate to an Azure resource and view its information in Cloud Explorer, expand the item's type or associated resource group and then select the resource. When you select a resource, information appears in the two tabs - **Actions** and **Properties** - at the bottom of Cloud Explorer.
 
-* **Actions** tab - Lists the actions you can take in Cloud Explorer for the selected resource. You can also view these options by right-clicking (or selecting and holding) the resource to view its context menu.
+* **Actions** tab - Lists the actions you can take in Cloud Explorer for the selected resource. You can also view these options by right-clicking the resource to view its context menu.
 
 * **Properties** tab - Shows the properties of the resource, such as its type, locale, and resource group with which it is associated.
 

docs/code-quality/analyzer-rule-sets.md

@@ -78,7 +78,7 @@ To make a rule set the active rule set for analysis in .NET Core or .NET Standar
 
 To make a rule set the active rule set for analysis in .NET Framework projects:
 
-- Right-click (or select and hold) on the project in **Solution Explorer** and select **Properties**.
+- Right-click the project in **Solution Explorer** and select **Properties**.
 
 - In the project property pages, select the **Code Analysis** tab.
 

docs/code-quality/code-analysis-for-managed-code-overview.md

@@ -13,7 +13,6 @@ ms.workload:
 ---
 # Overview of code analysis for managed code in Visual Studio
 
-Visual Studio can perform code analysis of managed code in two ways: 
+Visual Studio can perform code analysis of managed code in two ways:
 - With [legacy analysis](../code-quality/walkthrough-analyzing-managed-code-for-code-defects.md), also known as FxCop static analysis of managed assemblies.
-- With the more modern [.NET Compiler Platform-based code analyzers](../code-quality/roslyn-analyzers-overview.md). .NET Compiler Platform-based code analyzers, which analyze your code live as you type, replace legacy FxCop static code analysis, which only analyzes compiled code.
-
+- With the more modern [.NET Compiler Platform-based code analyzers](../code-quality/roslyn-analyzers-overview.md). .NET Compiler Platform-based code analyzers, which analyze your code live as you type, replace legacy FxCop static code analysis, which only analyzes compiled code.

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

@@ -17,7 +17,7 @@ ms.workload:
 For certain .NET code-quality analyzers (those whose rule IDs start with `CA`), you can refine which parts of your codebase they should be applied to through [configurable options](fxcop-analyzer-options.md). Each option is specified by adding a key-value pair to an [EditorConfig](https://editorconfig.org) file. A configuration file can be specific to a file, project, solution, or the entire repo.
 
 > [!TIP]
-> Add an .editorconfig file to your project by right-clicking (or selecting and holding) on the project in **Solution Explorer** and selecting **Add** > **New Item**. In the **Add New Item** window, enter **editorconfig** in the search box. Select the **editorconfig File (default)** template and choose **Add**.
+> Add an .editorconfig file to your project by right-clicking the project in **Solution Explorer** and selecting **Add** > **New Item**. In the **Add New Item** window, enter **editorconfig** in the search box. Select the **editorconfig File (default)** template and choose **Add**.
 >
 > ![Add editorconfig file to project in Visual Studio](media/add-editorconfig-file.png)
 

docs/code-quality/disable-code-analysis.md

@@ -2,7 +2,7 @@
 title: Turn off code analysis
 ms.date: 10/03/2019
 ms.topic: how-to
-helpviewer_keywords: 
+helpviewer_keywords:
   - code analysis, disable
   - disable code analysis
 author: mikejo5000
@@ -29,13 +29,13 @@ Starting in Visual Studio 2019 version 16.3, there are two checkboxes available
 
 ![Enable or disable live code analysis or on build in Visual Studio](media/run-on-build-run-live-analysis.png)
 
-To open this page, right-click (or select and hold) on the project node in **Solution Explorer** and select **Properties**. Select the **Code Analysis** tab.
+To open this page, right-click the project node in **Solution Explorer** and select **Properties**. Select the **Code Analysis** tab.
 
 - To disable source analysis at build time, uncheck the **Run on build** option.
 - To disable live source analysis, uncheck the **Run on live analysis** option.
 
 > [!NOTE]
-> Starting in Visual Studio 2019 version 16.5, if you prefer the on-demand code analysis execution workflow, you can disable analyzer execution during live analysis and/or build and manually trigger code analysis once on a project or a solution on demand. For information about running code analysis manually, see [How to: Run Code Analysis Manually for Managed Code](how-to-run-code-analysis-manually-for-managed-code.md).  
+> Starting in Visual Studio 2019 version 16.5, if you prefer the on-demand code analysis execution workflow, you can disable analyzer execution during live analysis and/or build and manually trigger code analysis once on a project or a solution on demand. For information about running code analysis manually, see [How to: Run Code Analysis Manually for Managed Code](how-to-run-code-analysis-manually-for-managed-code.md).
 
 ## .NET Framework projects
 

docs/code-quality/how-to-configure-code-analysis-for-a-managed-code-project.md

@@ -2,21 +2,21 @@
 title: Configure Code Analysis
 ms.date: 04/04/2018
 ms.topic: how-to
-f1_keywords: 
+f1_keywords:
   - vs.codeanalysis.propertypages.csvb
   - vs.codeanalysis.propertypages.solution
   - vs.codeanalysis.propertypages.asp
 dev_langs:
   - "CSharp"
   - "VB"
   - "FSharp"
-helpviewer_keywords: 
+helpviewer_keywords:
   - code analysis, selecting rule sets
   - code analysis, rule sets
 author: mikejo5000
 ms.author: mikejo
 manager: jillfra
-ms.workload: 
+ms.workload:
   - dotnet
 ---
 # How to: Configure legacy analysis for managed code
@@ -28,11 +28,11 @@ In Visual Studio, you can choose from a list of code analysis [rule sets](../cod
 
 ## Configure a rule set for a .NET Framework project
 
-1. Go to the **Code Analysis** tab on the project's property pages. You can do this in either of the following ways:
+1. Open the **Code Analysis** tab on the project's property pages. You can do this in either of the following ways:
 
    - In **Solution Explorer**, choose the project. On the menu bar, select **Analyze** > **Configure Code Analysis** > **For \<projectname>**.
 
-   - Right-click (or select and hold) the project in **Solution Explorer** and select **Properties**, and then select the **Code Analysis** tab.
+   - Right-click the project in **Solution Explorer** and select **Properties**, and then select the **Code Analysis** tab.
 
 2. In the **Configuration** and **Platform** lists, choose the build configuration and target platform.
 

docs/deployment/quickstart-deploy-to-azure.md

@@ -25,7 +25,7 @@ This article describes how to use the **Publish** tool for one-time deployment.
 
 ## Publish to Azure App Service on Windows
 
-1. In Solution Explorer, open the project and choose **Publish** (or use the **Build** > **Publish** menu item).
+1. In Solution Explorer, right-click the project node and choose **Publish** (or use the **Build** > **Publish** menu item).
 
     ![The Publish command on the project context menu in Solution Explorer](../deployment/media/quickstart-publish.png "Choose Publish")
 

docs/designers/walkthrough-windows-forms-designer.md

@@ -37,7 +37,7 @@ The first step is to create the DemoCalculator control project.
 
    ::: moniker-end
 
-2. To rename the file, in **Solution Explorer**, right-select **UserControl1.vb** or **UserControl1.cs**, select **Rename**, and change the file name to DemoCalculator.vb or DemoCalculator.cs. Select **Yes** when you are asked if you want to rename all references to the code element "UserControl1".
+2. To rename the file, in **Solution Explorer**, right-click **UserControl1.vb** or **UserControl1.cs**, select **Rename**, and change the file name to DemoCalculator.vb or DemoCalculator.cs. Select **Yes** when you are asked if you want to rename all references to the code element "UserControl1".
 
 The Windows Forms Designer shows the designer surface for the DemoCalculator control. In this view, you can graphically design the appearance of the control by selecting controls and components from Toolbox and placing them on the designer surface. For more information about custom controls, see [Varieties of custom controls](/dotnet/framework/winforms/controls/varieties-of-custom-controls).
 
@@ -155,7 +155,7 @@ When your control or form is populated with several controls, you may find it ea
 
    The Document Outline window shows a tree view of the DemoCalculator control and its constituent controls. Container controls like the `SplitContainer` show their child controls as subnodes in the tree. You can also rename controls in place using the Document Outline window.
 
-2. In the **Document Outline** window, right-select **button1**, and then select **Rename**. Change its name to sevenButton.
+2. In the **Document Outline** window, right-click **button1**, and then select **Rename**. Change its name to sevenButton.
 
 3. Using the **Document Outline** window, rename the `Button` controls from the designer-generated name to the production name according to the following list:
 
@@ -269,11 +269,11 @@ The first step is to create the application project. You'll use this project to
 
 1. Create a new **Windows Forms Application** project and name it **DemoCalculatorTest**.
 
-2. In **Solution Explorer**, select and hold (or right click) the **DemoCalculatorTest** project, and then select **Add Reference** to open the **Add Reference** dialog box.
+2. In **Solution Explorer**, right-click the **DemoCalculatorTest** project, and then select **Add Reference** to open the **Add Reference** dialog box.
 
 3. Go to the **Projects** tab, and then select the DemoCalculatorLib project to add the reference to the test project.
 
-4. In **Solution Explorer**, select and hold (or right click) **DemoCalculatorTest**, and then select **Set as StartUp Project**.
+4. In **Solution Explorer**, right-click **DemoCalculatorTest**, and then select **Set as StartUp Project**.
 
 5. In the Windows Forms Designer, increase the size of the form to about **700 x 500**.
 
@@ -291,7 +291,7 @@ To use the DemoCalculator control in an application, you need to place it on a f
 
 4. Move the `Button` control around the DemoCalculator control and observe where the snaplines appear. You can align your controls precisely and easily using this feature. Delete the `Button` control when you're finished.
 
-5. Right-select the DemoCalculator control, and then select **Properties**.
+5. Right-click the DemoCalculator control, and then select **Properties**.
 
 6. Change the value of the `Dock` property to `Fill`.
 

docs/extensibility/adding-a-menu-to-the-visual-studio-menu-bar.md

@@ -37,13 +37,13 @@ Starting in Visual Studio 2015, you do not install the Visual Studio SDK from th
 
 ::: moniker range="vs-2017"
 
-2. When the project opens, add a custom command item template named **TestCommand**. In the **Solution Explorer**, select and hold (or right-click) the project node and select **Add** >  **New Item**. In the **Add New Item** dialog, go to **Visual C# / Extensibility** and select **Custom Command**. In the **Name** field at the bottom of the window, change the command file name to *TestCommand.cs*.
+2. When the project opens, add a custom command item template named **TestCommand**. In the **Solution Explorer**, right-click the project node and select **Add** >  **New Item**. In the **Add New Item** dialog, go to **Visual C# / Extensibility** and select **Custom Command**. In the **Name** field at the bottom of the window, change the command file name to *TestCommand.cs*.
 
 ::: moniker-end
 
 ::: moniker range=">=vs-2019"
 
-2. When the project opens, add a custom command item template named **TestCommand**. In the **Solution Explorer**, select and hold (or right-click) the project node and select **Add** >  **New Item**. In the **Add New Item** dialog, go to **Visual C# / Extensibility** and select **Command**. In the **Name** field at the bottom of the window, change the command file name to *TestCommand.cs*.
+2. When the project opens, add a custom command item template named **TestCommand**. In the **Solution Explorer**, right-click the project node and select **Add** >  **New Item**. In the **Add New Item** dialog, go to **Visual C# / Extensibility** and select **Command**. In the **Name** field at the bottom of the window, change the command file name to *TestCommand.cs*.
 
 ::: moniker-end