Fix validation issues in VS docs (#8546)

ghogen · v-andreaco · web-flow · commit 42aec4a2ea6d · 2021-08-26T14:15:08.000-06:00
* validation issues in vs docs

* Update docs/test/live-unit-testing-faq.yml

* Update docs/test/live-unit-testing-faq.yml

Co-authored-by: Andrea Courtright &lt;74212614+v-andreaco@users.noreply.github.com&gt;
diff --git a/docs/code-quality/ca0070.md b/docs/code-quality/ca0070.md
@@ -1,5 +1,6 @@
 ---
 title: CA0070
+description: "This error occurs when code analysis analyzes an assembly and encounters permission attributes and certain conditions are true."
 ms.date: 10/19/2016
 ms.topic: reference
 f1_keywords:
diff --git a/docs/code-quality/fxcop-unported-rules.md b/docs/code-quality/fxcop-unported-rules.md
@@ -1,5 +1,6 @@
 ---
 title: Unported rules
+description: "Learn about FxCop legacy analysis rules that haven't been implemented as Roslyn analyzers."
 ms.date: 05/21/2019
 ms.topic: reference
 helpviewer_keywords:
diff --git a/docs/debugger/configure-the-windows-firewall-for-remote-debugging.md b/docs/debugger/configure-the-windows-firewall-for-remote-debugging.md
@@ -47,7 +47,7 @@ Visual Studio and the remote debugger try to open the correct ports during insta
 
 **To open a port using PowerShell:**
 
-For Windows Firewall, you can use PowerShell commands such as [New-NetFirewallRule](/powershell/module/netsecurity/new-netfirewallrule?view=win10-ps).
+For Windows Firewall, you can use PowerShell commands such as [New-NetFirewallRule](/powershell/module/netsecurity/new-netfirewallrule).
 
 The following example opens port 4024 for the remote debugger on the remote computer. The path you need to use may be different.
 
diff --git a/docs/debugger/debug-interface-access/idiasymbol-findsymbolsforacceleratorpointertag.md b/docs/debugger/debug-interface-access/idiasymbol-findsymbolsforacceleratorpointertag.md
@@ -1,5 +1,5 @@
 ---
-description: "Returns the number of accelerator pointer tags in a C++ AMP stub function."
+description: "Given a corresponding tag value, this method returns an enumeration of symbols that are contained in this stub function."
 title: "IDiaSymbol::findSymbolsForAcceleratorPointerTag | Microsoft Docs"
 ms.date: "11/04/2016"
 ms.topic: "reference"
@@ -14,7 +14,8 @@ ms.workload:
   - "multiple"
 ---
 # IDiaSymbol::findSymbolsForAcceleratorPointerTag
-Returns the number of accelerator pointer tags in a C++ AMP stub function.
+
+Given a corresponding tag value, this method returns an enumeration of symbols that are contained in this stub function.
 
 ## Syntax
 
diff --git a/docs/debugger/debug-interface-access/idiasymbol-get-basetype.md b/docs/debugger/debug-interface-access/idiasymbol-get-basetype.md
@@ -1,5 +1,6 @@
 ---
-title: "IDiaSymbol::get_baseType | Microsoft Docs"
+title: "IDiaSymbol::get_baseType"
+description: "Retrieves the base type for this symbol"
 ms.date: "11/04/2016"
 ms.topic: "reference"
 dev_langs:
@@ -15,7 +16,7 @@ ms.workload:
   - "multiple"
 ---
 # IDiaSymbol::get_baseType
-Retrieves the base type for this symbol<em>.</em>
+Retrieves the base type for this symbol.
 
 ## Syntax
 
diff --git a/docs/deployment/how-to-create-a-localized-bootstrapper-package.md b/docs/deployment/how-to-create-a-localized-bootstrapper-package.md
@@ -88,7 +88,7 @@ After you create a bootstrapper package, you can create localized versions of th
 6. Save the *package.xml* file.
 
 >[!NOTE]
-> Starting with the Visual Studio 2019 Update 7 release bootstrapper packages will also be discovered under the path *<VS Install Path>\MSBuild\Microsoft\VisualStudio\BootstrapperPackages*.
+> Starting with the Visual Studio 2019 Update 7 release bootstrapper packages will also be discovered under the path *{VS Install Path}\MSBuild\Microsoft\VisualStudio\BootstrapperPackages*.
 
 ## See also
 - [Create bootstrapper packages](../deployment/creating-bootstrapper-packages.md)
diff --git a/docs/get-started/csharp/tutorial-aspnet-core.md b/docs/get-started/csharp/tutorial-aspnet-core.md
@@ -352,7 +352,7 @@ Here's a quick FAQ to highlight some key concepts.
 
 ### What is C#?
 
-[C#](https://docs.microsoft.com/dotnet/csharp/tour-of-csharp/) is a type-safe and object-oriented programming language that's designed to be both robust and easy to learn.
+[C#](/dotnet/csharp/tour-of-csharp/) is a type-safe and object-oriented programming language that's designed to be both robust and easy to learn.
 
 ### What is ASP.NET Core?
 
diff --git a/docs/ide/how-to-view-save-and-configure-build-log-files.md b/docs/ide/how-to-view-save-and-configure-build-log-files.md
@@ -26,7 +26,7 @@ If you build any kind of project by using MSBuild, you can create a log file to
 
 ## To view the build log file for a C++ project
 
-1. In **Windows Explorer** or **File Explorer**, open the following file (relative to the project root folder): *Release*\\<ProjectName>\>.Log* or *Debug\\<ProjectName\>.log*
+1. In **Windows Explorer** or **File Explorer**, open the following file (relative to the project root folder): *Release*\\{ProjectName}.Log* or *Debug\\{ProjectName}.log*
 
 ## To create a build log file for a managed-code project
 
diff --git a/docs/ide/quickstart-fsharp.md b/docs/ide/quickstart-fsharp.md
@@ -4,8 +4,8 @@ description: "Learn how to create an ASP.NET Core web service in Visual Studio w
 ms.date: 08/24/2018
 ms.topic: quickstart
 ms.custom: vs-acquisition
-author: "cartermp"
-ms.author: "phcart"
+author: anandmeg
+ms.author: meghaanand
 manager: jmartens
 ms.technology: vs-ide-general
 dev_langs:
diff --git a/docs/ide/reference/use-pattern-matching.md b/docs/ide/reference/use-pattern-matching.md
@@ -20,7 +20,7 @@ This refactoring applies to:
 
 **What:** Use pattern matching.
 
-**When:** You want to use the new [C# pattern matching](https://docs.microsoft.com/dotnet/csharp/whats-new/csharp-9#pattern-matching-enhancements) capabilities.
+**When:** You want to use the new [C# pattern matching](/dotnet/csharp/whats-new/csharp-9#pattern-matching-enhancements) capabilities.
 
 **Why:** This refactoring will make your code more clear and concise.
 
diff --git a/docs/install/visual-studio-enterprise-guide.md b/docs/install/visual-studio-enterprise-guide.md
@@ -23,7 +23,7 @@ If you’re looking to save time while you're getting your company running on Vi
 ## Get started 
 Learn how to deploy Visual Studio to your enterprise in networked and offline environments.
 
-- **[Enabling Administrator Updates using Microsoft Endpoint Configuration Manager (SCCM)](enabling-administrator-updates.md)**.  Visual Studio updates are included in the [Microsoft Update Catalog](https://www.catalog.update.microsoft.com/Home.aspx) and the [Windows Server Update Services (WSUS)](https://docs.microsoft.com/windows-server/administration/windows-server-update-services/get-started/windows-server-update-services-wsus). Enterprise administrators can then download the update and distribute it to Visual Studio client machines across the organization using standard deployment tools such as Microsoft Endpoint Configuration Manager (SCCM).
+- **[Enabling Administrator Updates using Microsoft Endpoint Configuration Manager (SCCM)](enabling-administrator-updates.md)**.  Visual Studio updates are included in the [Microsoft Update Catalog](https://www.catalog.update.microsoft.com/Home.aspx) and the [Windows Server Update Services (WSUS)](/windows-server/administration/windows-server-update-services/get-started/windows-server-update-services-wsus). Enterprise administrators can then download the update and distribute it to Visual Studio client machines across the organization using standard deployment tools such as Microsoft Endpoint Configuration Manager (SCCM).
 
 - **Understand options for enterprise deployment in networked environments**. The [Visual Studio administrator guide](visual-studio-administrator-guide.md) provides scenario-based guidance for system administrators. 
 
diff --git a/docs/javascript/compile-typescript-code-nuget.md b/docs/javascript/compile-typescript-code-nuget.md
@@ -152,7 +152,7 @@ For instructions to run the app after you compile it, see [Create your first Nod
 
 ### Remove default imports
 
-In older ASP.NET Core projects that use the [non-SDK-style format](https://docs.microsoft.com/nuget/resources/check-project-format), you may need to remove some project file elements.
+In older ASP.NET Core projects that use the [non-SDK-style format](/nuget/resources/check-project-format), you may need to remove some project file elements.
 
 If you are using the NuGet package for MSBuild support for a project, the project file must not import `Microsoft.TypeScript.Default.props` or `Microsoft.TypeScript.targets`. The files get imported by the NuGet package, so including them separately may cause unintended behavior.
 
diff --git a/docs/msbuild/customize-your-build.md b/docs/msbuild/customize-your-build.md
@@ -239,9 +239,11 @@ But, you can use the following properties to specify *.props* file(s) to be auto
 
 To customize the default values of properties for all C++ builds, create another *.props* file (say, *MyProps.props*), and define the `ForceImportAfterCppProps` property in `Directory.Build.props` pointing to it:
 
+```xml
 <PropertyGroup>
   <ForceImportAfterCppProps>$(MsbuildThisFileDirectory)\MyProps.props<ForceImportAfterCppProps>
 </PropertyGroup>
+```
 
 *MyProps.props* will be automatically imported at the very end of *Microsoft.Cpp.props*.
 
diff --git a/docs/msbuild/errors/msb3821.md b/docs/msbuild/errors/msb3821.md
@@ -22,9 +22,9 @@ ms.workload:
 
 This error occurs when MSBuild attempts to process a file downloaded from the web with security restrictions.
 
-When you download web assets such as HTML pages to a Windows device using a browser, the browser inserts a marker called the *mark of the web*, which records the security zone of the site from which the page originated. This is intended to protect from potentially malicious pages and enforce the security level on the original site, even after a page from the site is downloaded. This security check is required due to this security issue: [Visual Studio Remote Code Execution Vulnerability CVE-2018-8172](https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2018-8172).
+When you download web assets such as HTML pages to a Windows device using a browser, the browser inserts a marker called the *mark of the web*, which records the security zone of the site from which the page originated. This is intended to protect from potentially malicious pages and enforce the security level on the original site, even after a page from the site is downloaded. This security check is required due to this security issue: [Visual Studio Remote Code Execution Vulnerability CVE-2018-8172](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2018-8172).
 
- MSBuild respects this security restriction, but if you decide that you trust the content in question, but you can override the restriction by unblocking a single file from File Explorer (open the **Properties** window on the file, and check **Unblock**). To unblock multiple files using a PowerShell script, use the [Unblock-File](https://docs.microsoft.com/powershell/module/microsoft.powershell.utility/unblock-file) cmdlet.
+ MSBuild respects this security restriction, but if you decide that you trust the content in question, but you can override the restriction by unblocking a single file from File Explorer (open the **Properties** window on the file, and check **Unblock**). To unblock multiple files using a PowerShell script, use the [Unblock-File](/powershell/module/microsoft.powershell.utility/unblock-file) cmdlet.
 
 The full message is similar to the following:
 
diff --git a/docs/msbuild/errors/msb4166.md b/docs/msbuild/errors/msb4166.md
@@ -26,6 +26,6 @@ MSB4166: Child node 'node' exited prematurely. Shutting down. Diagnostic
 
 The error text shown is followed by the exception text, if any.
 
-MSBuild can use multiple processes and there's a scheduler process that distributes work to the various worker nodes. If the worker process crashes without reporting an error to the scheduler, then the scheduler emits this error. Check the error log in the temporary files folder in *MSBuild_<guid>.failure.txt*.
+MSBuild can use multiple processes and there's a scheduler process that distributes work to the various worker nodes. If the worker process crashes without reporting an error to the scheduler, then the scheduler emits this error. Check the error log in the temporary files folder in *MSBuild_{guid}.failure.txt*.
 
 This error usually indicates an MSBuild issue, and should be reported to Microsoft. Please report the issue in the [MSBuild GitHub repository](https://github.com/Microsoft/msbuild) or at [Developer Community](https://developercommunity.visualstudio.com/search?space=8).
diff --git a/docs/profiling/analyze-database.md b/docs/profiling/analyze-database.md
@@ -17,7 +17,7 @@ ms.workload:
 Use the Database tool to record the database queries that your app makes during a diagnostic session. You can then analyze information about individual queries to find places to improve your app's performance.
 
 > [!NOTE]
-> The Database tool requires Visual Studio 2019 version 16.3 or later and a .NET Core project on Windows using either [ADO.NET]( https://docs.microsoft.com/dotnet/framework/data/adonet/ado-net-overview) or [Entity Framework Core](/ef/core/).
+> The Database tool requires Visual Studio 2019 version 16.3 or later and a .NET Core project on Windows using either [ADO.NET](/dotnet/framework/data/adonet/ado-net-overview) or [Entity Framework Core](/ef/core/).
 
 ## Setup
 
diff --git a/docs/profiling/how-to-specify-symbol-file-locations-from-the-command-line.md b/docs/profiling/how-to-specify-symbol-file-locations-from-the-command-line.md
@@ -43,9 +43,9 @@ To display symbol information such as function names and line numbers, the VSPer
 
 2. Use the following syntax to set the **_NT_SYMBOL_PATH** environment variable or the VSPerfReport /SymbolPath option:
 
-    `srv*<LocalStore>*https://msdl.microsoft.com/download/symbols`
+    `srv*{LocalStore}*https://msdl.microsoft.com/download/symbols`
 
-    where *<LocalStore>* is the path of the local directory that you created.
+    where *{LocalStore}* is the path of the local directory that you created.
 
 ## Specify component symbol files
  Profiling Tools searches for the.*pdb* files of the components that you want to profile in their original locations that are stored in the components or in the folder that contains the profiling data file. You can specify other locations to search by adding one or more paths to **_NT_SYMBOL_PATH** or to the **/SymbolPath** option. Separate paths with semi-colons.
diff --git a/docs/sharepoint/walkthrough-creating-a-custom-action-project-item-with-an-item-template-part-1.md b/docs/sharepoint/walkthrough-creating-a-custom-action-project-item-with-an-item-template-part-1.md
@@ -425,7 +425,7 @@ ms.workload:
     > [!NOTE]
     > If the **Script Debugging Disabled** dialog box appears, choose the **Yes** button to continue to debug the project.
 
-4. On the **Site Actions** menu, choose **SharePoint Developer Center**, verify that the browser opens the website https://docs.microsoft.com/sharepoint/dev/, and then close the web browser.
+4. On the **Site Actions** menu, choose **SharePoint Developer Center**, verify that the browser opens the website `https://docs.microsoft.com/sharepoint/dev/`, and then close the web browser.
 
 ## Clean up the development computer
  After you finish testing the project item, remove the project item template from the experimental instance of Visual Studio.
diff --git a/docs/sharepoint/walkthrough-creating-a-custom-action-project-item-with-an-item-template-part-2.md b/docs/sharepoint/walkthrough-creating-a-custom-action-project-item-with-an-item-template-part-2.md
@@ -301,7 +301,7 @@ ms.workload:
 
 13. In the  **Description** box, enter **Opens the SharePoint Developer Center website**.
 
-14. In the **URL** box, enter **https://docs.microsoft.com/sharepoint/dev/**, and then choose the **Finish** button.
+14. In the **URL** box, enter `https://docs.microsoft.com/sharepoint/dev/`, and then choose the **Finish** button.
 
      Visual Studio adds an item that's named **CustomAction1** to your project and opens the *Elements.xml* file in the editor. Verify that *Elements.xml* contains the values that you specified in the wizard.
 
@@ -322,7 +322,7 @@ ms.workload:
 
      The **List Settings** page appears.
 
-4. Under the **Communications** heading near the top of the page, choose the **SharePoint Developer Center** link, verify that the browser opens the website https://docs.microsoft.com/sharepoint/dev/, and then close the browser.
+4. Under the **Communications** heading near the top of the page, choose the **SharePoint Developer Center** link, verify that the browser opens the website `https://docs.microsoft.com/sharepoint/dev/`, and then close the browser.
 
 ## Cleaning up the development computer
  After you finish testing the project item, remove the project item template from the experimental instance of Visual Studio.
diff --git a/docs/test/live-unit-testing-faq.yml b/docs/test/live-unit-testing-faq.yml
@@ -108,7 +108,7 @@ sections:
           
           During build, Live Unit Testing automatically overrides the `<BaseOutputPath>`/`<BaseIntermediateOutputPath>` variables to target the Live Unit Testing artifacts folder.
           
-          For example, if your build overrides the <OutputPath> as shown below:
+          For example, if your build overrides the `<OutputPath>` as shown below:
           
           ```xml
           <Project>
diff --git a/docs/vsto/create-vsto-add-ins-for-office-by-using-visual-studio.md b/docs/vsto/create-vsto-add-ins-for-office-by-using-visual-studio.md
@@ -17,7 +17,7 @@ ms.workload:
 ---
 # Create VSTO Add-ins for Office by using Visual Studio
 > [!IMPORTANT]
-> VSTO relies on the [.NET Framework](https://docs.microsoft.com/dotnet/framework/get-started/overview). COM add-ins can also be written with the .NET Framework. Office Add-ins cannot be created with [.NET Core and .NET 5+](https://docs.microsoft.com/dotnet/core/dotnet-five), the latest versions of .NET. This is because .NET Core/.NET 5+ cannot work together with .NET Framework in the same process and may lead to add-in load failures. You can continue to use .NET Framework to write VSTO and COM add-ins for Office. Microsoft will not be updating VSTO or the COM add-in platform to use .NET Core or .NET 5+. You can take advantage of .NET Core and .NET 5+, including ASP.NET Core, to create the server side of [Office Web Add-ins](https://docs.microsoft.com/office/dev/add-ins/overview/office-add-ins).
+> VSTO relies on the [.NET Framework](/dotnet/framework/get-started/overview). COM add-ins can also be written with the .NET Framework. Office Add-ins cannot be created with [.NET Core and .NET 5+](/dotnet/core/dotnet-five), the latest versions of .NET. This is because .NET Core/.NET 5+ cannot work together with .NET Framework in the same process and may lead to add-in load failures. You can continue to use .NET Framework to write VSTO and COM add-ins for Office. Microsoft will not be updating VSTO or the COM add-in platform to use .NET Core or .NET 5+. You can take advantage of .NET Core and .NET 5+, including ASP.NET Core, to create the server side of [Office Web Add-ins](/office/dev/add-ins/overview/office-add-ins).
 
   You can use the Microsoft Office developer tools in Visual Studio to create .NET Framework applications that extend Office. These applications are also named *Office solutions*.
 
diff --git a/docs/vsto/getting-started-programming-vsto-add-ins.md b/docs/vsto/getting-started-programming-vsto-add-ins.md
@@ -21,7 +21,7 @@ ms.workload:
 ---
 # Get started programming VSTO Add-ins
 > [!IMPORTANT]
-> VSTO relies on the [.NET Framework](https://docs.microsoft.com/dotnet/framework/get-started/overview). COM add-ins can also be written with the .NET Framework. Office Add-ins cannot be created with [.NET Core and .NET 5+](https://docs.microsoft.com/dotnet/core/dotnet-five), the latest versions of .NET. This is because .NET Core/.NET 5+ cannot work together with .NET Framework in the same process and may lead to add-in load failures. You can continue to use .NET Framework to write VSTO and COM add-ins for Office. Microsoft will not be updating VSTO or the COM add-in platform to use .NET Core or .NET 5+. You can take advantage of .NET Core and .NET 5+, including ASP.NET Core, to create the server side of [Office Web Add-ins](https://docs.microsoft.com/office/dev/add-ins/overview/office-add-ins).
+> VSTO relies on the [.NET Framework](/dotnet/framework/get-started/overview). COM add-ins can also be written with the .NET Framework. Office Add-ins cannot be created with [.NET Core and .NET 5+](/dotnet/core/dotnet-five), the latest versions of .NET. This is because .NET Core/.NET 5+ cannot work together with .NET Framework in the same process and may lead to add-in load failures. You can continue to use .NET Framework to write VSTO and COM add-ins for Office. Microsoft will not be updating VSTO or the COM add-in platform to use .NET Core or .NET 5+. You can take advantage of .NET Core and .NET 5+, including ASP.NET Core, to create the server side of [Office Web Add-ins](/office/dev/add-ins/overview/office-add-ins).
 
   You can use VSTO Add-ins to automate Microsoft Office applications, extend features of the application, and customize the user interface (UI) of the application. For information about how VSTO Add-ins compare to other types of Office solutions you can create by using Visual Studio, see [Office solutions development overview &#40;VSTO&#41;](../vsto/office-solutions-development-overview-vsto.md).
 
