Merge pull request #5739 from MicrosoftDocs/master637330486681981057

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

Author: ghogen

.openpublishing.redirection.json

@@ -16,7 +16,7 @@ ms.workload:
 ---
 # CA1805: Do not initialize unnecessarily.
 
-|||
+|Item|Value|
 |-|-|
 |CheckId|CA1805|
 |Category|Microsoft.Performance|

docs/code-quality/ca1805.md

@@ -16,7 +16,7 @@ ms.workload:
 ---
 # CA1830: Prefer strongly-typed Append and Insert method overloads on StringBuilder.
 
-|||
+|Item|Value|
 |-|-|
 |CheckId|CA1830|
 |Category|Microsoft.Performance|

docs/code-quality/ca1830.md

@@ -19,7 +19,7 @@ ms.workload:
 ---
 # CA2016: Forward the CancellationToken parameter to methods that take one
 
-|||
+|Item|Value|
 |-|-|
 |TypeName|ForwardCancellationTokenToInvocations|
 |CheckId|CA2016|

docs/code-quality/ca2016.md

@@ -16,7 +16,7 @@ ms.workload:
 ---
 # CA2247: Argument passed to TaskCompletionSource constructor should be TaskCreationOptions enum instead of TaskContinuationOptions enum
 
-|||
+|Item|Value|
 |-|-|
 |CheckId|CA2247|
 |Category|Microsoft.Usage|

docs/code-quality/ca2247.md

@@ -1,5 +1,5 @@
 ---
-title: Code analysis for managed code
+title: Legacy analysis for managed code
 ms.date: 06/12/2019
 ms.topic: conceptual
 helpviewer_keywords:
@@ -11,7 +11,7 @@ manager: jillfra
 ms.workload:
   - "dotnet"
 ---
-# Overview of code analysis for managed code in Visual Studio
+# Overview of legacy analysis for managed code in Visual Studio
 
 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, and with the more modern .NET Compiler Platform-based [code analyzers](../code-quality/roslyn-analyzers-overview.md). This topic covers legacy analysis. To learn more about .NET Compiler Platform-based code analysis, see [Overview of .NET Compiler Platform-based analyzers](../code-quality/roslyn-analyzers-overview.md).
 

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

@@ -11,7 +11,7 @@ manager: jillfra
 ms.workload:
 - vssdk
 ---
-# Implementing a Legacy Language Service
+# Implementing a legacy language service 1
 You can use classes in the managed package framework (MPF) to implement a legacy language service that supports a wide variety of features, such as syntax highlighting, brace matching, and IntelliSense completion.
 
  Legacy language services are implemented as part of a VSPackage, but the newer way to implement language service features is to use MEF extensions. To find out more about the new way to implement a language service, see [Editor and Language Service Extensions](../../extensibility/editor-and-language-service-extensions.md).

docs/extensibility/internals/implementing-a-legacy-language-service1.md

@@ -11,7 +11,7 @@ manager: jillfra
 ms.workload:
 - vssdk
 ---
-# Implementing a Legacy Language Service
+# Implementing a legacy language service 2
 To implement a language service using the managed package framework (MPF), you must derive a class from the <xref:Microsoft.VisualStudio.Package.LanguageService> class and implement the following abstract methods and properties:
 
 - The <xref:Microsoft.VisualStudio.Package.LanguageService.GetLanguagePreferences%2A> method

docs/extensibility/internals/implementing-a-legacy-language-service2.md

@@ -11,7 +11,7 @@ manager: jillfra
 ms.workload:
 - vssdk
 ---
-# Legacy Language Service Features
+# Legacy language service features 1
 A managed package framework (MPF) language service can support one or more [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)] features, such as syntax highlighting, IntelliSense, and breakpoint validation. Each feature can be implemented independent of the others but all require a parser and a scanner except for syntax highlighting, which requires only a scanner.
 
 ## In This Section

docs/extensibility/internals/legacy-language-service-features1.md

@@ -11,7 +11,7 @@ manager: jillfra
 ms.workload:
 - vssdk
 ---
-# Legacy Language Service Features
+# Legacy language service features 2
 The following topics list some of the legacy language service features you can provide.
 
  Legacy language services are implemented as part of a VSPackage, but the newer way to implement language service features is to use MEF extensions. To find out more about the new way to implement a language service, see [Editor and Language Service Extensions](../../extensibility/editor-and-language-service-extensions.md).

docs/extensibility/internals/legacy-language-service-features2.md

@@ -15,7 +15,7 @@ manager: jillfra
 ms.workload:
 - vssdk
 ---
-# Parameter Info in a Legacy Language Service
+# Parameter Info in a legacy language service 1
 The IntelliSense Parameter Info tooltip provides users with hints about where they are in a language construct.
 
  Legacy language services are implemented as part of a VSPackage, but the newer way to implement language service features is to use MEF extensions. To find out more, see [Extending the Editor and Language Services](../../extensibility/extending-the-editor-and-language-services.md).

docs/extensibility/internals/parameter-info-in-a-legacy-language-service1.md

@@ -13,7 +13,7 @@ manager: jillfra
 ms.workload:
 - vssdk
 ---
-# Parameter Info in a Legacy Language Service
+# Parameter Info in a legacy language service 2
 IntelliSense Parameter Info is a tooltip that displays the signature of a method when the user types the parameter list start character (typically an open parenthesis) for the method parameter list. As each parameter is entered and the parameter separator (typically a comma) is typed, the tooltip is updated to show the next parameter in bold.
 
  The managed package framework (MPF) classes provide support for managing the Parameter Info tooltip. The parser must detect parameter start, parameter next, and parameter end characters, and it must supply a list of the method signatures and their associated parameters.

docs/extensibility/internals/parameter-info-in-a-legacy-language-service2.md

@@ -11,7 +11,7 @@ manager: jillfra
 ms.workload:
 - vssdk
 ---
-# Registering a Legacy Language Service
+# Registering a legacy language service 1
 In the managed package framework (MPF), the language service is proffered by a VSPackage (see [VSPackages](../../extensibility/internals/vspackages.md)) and is registered with [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)] by adding registry keys and entries. This registration process is done in partly during installation and partly at run time.
 
 ## Register the Language Service by Using Attributes

docs/extensibility/internals/registering-a-legacy-language-service1.md

@@ -13,7 +13,7 @@ manager: jillfra
 ms.workload:
 - vssdk
 ---
-# Registering a Legacy Language Service
+# Registering a legacy language service 2
 The following sections provide lists of registry entries for the various language service options available in [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)].
 
  In the following list of registry entries, *VS Reg Root* is equal to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\\*X.Y*, where *X.Y* is the [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)] version number.