Apply suggestions from code review

Author: ghogen

docs/ide/how-to-set-multiple-startup-projects.md

@@ -41,7 +41,6 @@ The following example shows a solution WebFrontEndA with three projects, a front
 
 In this example and any other Docker Compose scenario, if you choose `docker-compose` as the single startup project, but then you'll use a different way of specifying which projects or services to start. You'll use a Docker Compose launch profile to determine what services to start, and whether or not to attach the debugger, and there's a different dialog in Visual Studio for configuring it. See [Start a subset of services](../containers/launch-profiles.md). The **Solution Property Pages** dialog is only used for non-containerized solutions or when you are *not* using Docker Compose to manage startup.
 
-
 ## See also
 
 - [Compile and build](../ide/compiling-and-building-in-visual-studio.md)

docs/ide/managing-project-and-solution-properties.md

@@ -31,7 +31,6 @@ You access project properties by right-clicking the project node in **Solution E
 
 :::image type="content" source="media/vs-2022/properties-node-solution-explorer.png" alt-text="Screenshot of Solution Explorer with a Properties node showing.":::
 
-
 > [!NOTE]
 > This topic applies to Visual Studio on Windows. For Visual Studio for Mac, see [Managing solution and project properties (Visual Studio for Mac)](/visualstudio/mac/managing-solutions-and-project-properties).
 
@@ -74,7 +73,6 @@ C++ and JavaScript projects have a different user interface for managing project
 
 :::image type="content" source="media/vs-2022/properties-page-cpp-console.png" alt-text="Screenshot of the C++ project properties page.":::
 
-
 For information about C++ project properties, see [Work with project properties (C++)](/cpp/build/working-with-project-properties). For more information about JavaScript properties, see [Property pages, JavaScript](../ide/reference/property-pages-javascript.md).
 
 ## Solution properties

docs/ide/reference/options-text-editor-basic-visual-basic.md

@@ -113,7 +113,6 @@ When selected, inserts parameter name hints for literals, casted literals, and o
 
 ![Inline Parameter Name Hints for Visual Basic](media/inline-parameter-name-hints-visualbasic.png)
 
-
 **Pretty Listing (reformatting) of code**
 The text editor reformats your code as appropriate. When this option is selected, the code editor will:
 

docs/ide/reference/options-text-editor-csharp-advanced.md

@@ -108,7 +108,6 @@ Use the **Advanced** options page to modify the settings for editor formatting,
 - Suggest usings for types in .NET Framework assemblies
 
 
-
 - Suggest usings for types in NuGet packages
 
    When these options are selected, a [Quick Action](../quick-actions.md) is available to install a NuGet package and add a `using` directive for unreferenced types.

docs/ide/solutions-and-projects-in-visual-studio.md

@@ -79,8 +79,6 @@ A "solution folder" is a virtual folder that's only in **Solution Explorer**, wh
 After you create a new project, you can use **[Solution Explorer](use-solution-explorer.md)** to view and manage the project and solution and their associated items. The following illustration shows **Solution Explorer** with a C# solution that contains two projects:
 
 
-::: moniker range=">=vs-2019"
-
 ![Screenshot of Solution Explorer with two projects in Visual Studio.](../ide/media/solution-explorer.png)
 
 The [toolbar](use-solution-explorer.md#solution-explorer-toolbar) across the top of **Solution Explorer** has buttons to switch from a solution view to a folder view, filter pending changes, show all files, collapse all nodes, view [properties](managing-project-and-solution-properties.md) pages, preview code in the [code editor](writing-code-in-the-code-and-text-editor.md), and more.

docs/ide/walkthrough-building-an-application.md

@@ -20,7 +20,6 @@ In this article, you'll become more familiar with several options that you can c
 
  The sample code used in this tutorial is found at [WPF samples](https://github.com/microsoft/wpf-samples). To clone the repo, use GitHub's green **Clone** button, and choose **Clone in Visual Studio**. You can choose the location on the local hard drive to create a copy of the contents of the repo. The repo contains many solutions. If Visual Studio opens one of the solutions, close the solution and then choose **Open project or solution**, and browse to the location where you cloned the repo, and under that, look for *GettingStarted/WalkthroughFirstWPFApp/csharp/ExpenseItIntro.sln* to work in C#, or *GettingStarted/WalkthroughFirstWPFApp/vb/ExpenseItIntro2.sln* to work in Visual Basic.
 
-
 ## Create a custom build configuration
 
 When you create a solution, Debug and Release build configurations and their default platform targets are defined for the solution automatically. You can then customize these configurations or create your own. Build configurations specify the build type. Build platforms specify the operating system that an application targets for that configuration. For more information, see [Understand build configurations](../ide/understanding-build-configurations.md), [Understand build platforms](../ide/understanding-build-platforms.md), and [How to: Set debug and release configurations](../debugger/how-to-set-debug-and-release-configurations.md).

docs/install/create-a-network-installation-of-visual-studio.md

@@ -163,7 +163,6 @@ Here are a few examples of how to create a custom partial layout.
     vs_enterprise.exe --layout C:\VSLayout --add Microsoft.VisualStudio.Workload.Azure --add Microsoft.VisualStudio.Workload.ManagedDesktop --includeRecommended --includeOptional
     ```
 
-
 ### Ensure your layout is using the latest installer
 
 We recommend that you always use the latest Visual Studio installer in your layout and distribute it to your clients. That way you will have access to the new features and functionality we make available in subsequent versions of the product. For example, if you distribute the Visual Studio 2022 Installer in your Visual Studio 2019 layouts, then your Visual Studio 2019 clients based off of that layout will have the ability to change source location for updates. The scenario where this functionality would be useful is if you want to install from one layout but have updates come from another layout. Further details, including how to turn _off_ using the latest installer, are [described below](#configure-the-layout-to-always-include-and-provide-the-latest-installer)

docs/javascript/create-application-with-vuejs.md

@@ -40,7 +40,6 @@ The following new features support Vue.js application development in Visual Stud
     If a required version is not already installed, install [Visual Studio 2019](https://visualstudio.microsoft.com/downloads).
 
 
-
     If you need to install the workload but already have Visual Studio, go to **Tools** > **Get Tools and Features...**, which opens the Visual Studio Installer. Choose the **Node.js development** workload, then choose **Modify**.
 
 * To create the ASP.NET Core project, you must have the ASP.NET and web development and .NET Core cross-platform development workloads installed.
@@ -73,7 +72,6 @@ For this example, you use an empty ASP.NET Core Application (C#). However, you c
     Choose either the recommended target framework or .NET 6, and then choose **Create**.
 
 
-
     If you don't see the **ASP.NET Core Web Application** project template, you must install the **ASP.NET and web development** workload and the .**NET Core** development workload first. To install the workload(s), click the **Open Visual Studio Installer** link in the left pane of the **New Project** dialog box (select **File** > **New** > **Project**). The Visual Studio Installer launches. Select the required workloads.
 
 #### Configure the project startup file

docs/javascript/npm-package-management.md

@@ -115,7 +115,6 @@ Right-click a package node to take one of the following actions:
 * **Uninstall npm Package(s)** Uninstalls the package and removes it from *package.json* (Runs `npm uninstall --save`.)
 
 
-
 >[!NOTE]
 > For help resolving issues with npm packages, see [Troubleshooting](#troubleshooting-npm-packages).
 

docs/javascript/publish-nodejs-app-azure.md

@@ -40,7 +40,6 @@ In this tutorial, you learn how to:
     If you haven't already installed Visual Studio 2019, go to the [Visual Studio downloads](https://visualstudio.microsoft.com/downloads/) page to install it for free.
 
 
-
     If you need to install the workload but already have Visual Studio, go to **Tools** > **Get Tools and Features...**, which opens the Visual Studio Installer. Choose the **Node.js development** workload, then choose **Modify**.
 
     ![Node.js workload in VS Installer](./media/tutorial-nodejs-workload.png)
@@ -57,7 +56,6 @@ In this tutorial, you learn how to:
 
     Press **Esc** to close the start window. Type **Ctrl + Q** to open the search box, type **Node.js**, then choose **Create new Basic Azure Node.js Express 4 application** (TypeScript). In the dialog box that appears, choose **Create**.
 
-
     If you don't see the **Basic Azure Node.js Express 4 application** project template, you must add the **Node.js development** workload. For detailed instructions, see the [Prerequisites](#prerequisites).
 
     Visual Studio creates the project and opens it in Solution Explorer (right pane).

docs/javascript/tutorial-nodejs-with-react-and-jsx.md

@@ -492,7 +492,6 @@ To start your browser with debugging enabled:
   `chrome.exe --remote-debugging-port=9222`
 
 
-
 The browser starts with debugging enabled. The app isn't running yet, so the browser page is empty.
 
 ### Attach the debugger to client-side script
@@ -542,7 +541,6 @@ The browser starts with debugging enabled. The app isn't running yet, so the bro
 
     If you created a debugging-enabled browser configuration with a friendly name, choose that browser as your debug target.
 
-
     The app opens in a new browser tab.
 
 1. Select **Debug** > **Attach to Process**, or press **Ctrl**+**Alt**+**P**.
@@ -555,7 +553,6 @@ The browser starts with debugging enabled. The app isn't running yet, so the bro
     Make sure the correct debugger for your target browser, **JavaScript (Chrome)** or **JavaScript (Microsoft Edge - Chromium)**, appears in the **Attach to** field. Type *chrome* or *edge* in the filter box to filter the results.
 
 
-
 1. Select the browser process with the correct host port, **localhost** in this example. The port number **1337** or **localhost** might also appear in the **Title** field to help you select the correct process.
 
 1. Select **Attach**.
@@ -565,7 +562,6 @@ The browser starts with debugging enabled. The app isn't running yet, so the bro
     ![Screenshot showing the Attach to process dialog box.](../javascript/media/tutorial-nodejs-react-attach-to-process-edge.png)
 
 
-
     > [!TIP]
     > If the debugger doesn't attach and you see the message **Unable to attach to the process. An operation is not legal in the current state.**, use Task Manager to close all instances of the target browser before starting the browser in debugging mode. Browser extensions may be running and preventing full debug mode.
 

docs/javascript/unit-testing-javascript-with-visual-studio.md

@@ -98,7 +98,6 @@ You can run tests in Visual Studio or from the command line.
 You can run the tests by clicking the **Run All** link in Test Explorer. Or, you can run tests by selecting one or more tests or groups, right-clicking, and selecting **Run** from the shortcut menu. Tests run in the background, and Test Explorer automatically updates and shows the results. Furthermore, you can also debug selected tests by right-clicking and selecting **Debug**.
 
 
-
 For TypeScript, unit tests are run against the generated JavaScript code.
 
 > [!NOTE]
@@ -256,7 +255,6 @@ Test execution time: 1.5731 Seconds
 You can run the tests by clicking the **Run All** link in Test Explorer. Or, you can run tests by selecting one or more tests or groups, right-clicking, and selecting **Run** from the shortcut menu. Tests run in the background, and Test Explorer automatically updates and shows the results. Furthermore, you can also debug selected tests by right-clicking and selecting **Debug**.
 
 
-
 For TypeScript, unit tests are run against the generated JavaScript code.
 
 ![Test Explorer results](../javascript/media/unit-tests-aspnet-core-run.png)

docs/msbuild/errors/msb3327.md

@@ -34,7 +34,6 @@ To resolve this error, try re-importing the .pfx file again in the certificate s
 
 See [How to: Sign application and deployment manifests](../../ide/how-to-sign-application-and-deployment-manifests.md) or for newer .NET projects in Visual Studio 2019 or later, see [Deploy a .NET Windows Desktop application using ClickOnce](../../deployment/quickstart-deploy-using-clickonce-folder.md).
 
-
 When running in a non-interactive environment, such as a script in a pipeline, use the command-line tool [certutil](/windows-server/administration/windows-commands/certutil).
 
 ```cmd