Merge pull request #7430 from ghogen/fix-validation

Fix validation errors

Author: v-shmck

docs/azure/vs-azure-tools-publishing-using-powershell-scripts.md

@@ -5,7 +5,6 @@ ms.custom: SEO-VS-2020
 author: ghogen
 manager: jillfra
 assetId: 5fff1301-5469-4d97-be88-c85c30f837c1
-ms.custom: vs-azure
 ms.workload: azure-vs
 ms.topic: conceptual
 ms.date: 11/11/2016

docs/code-quality/ca1013.md

@@ -58,12 +58,12 @@ To fix a violation of this rule, implement the equality operator so that it is m
 ## When to suppress warnings
 It is safe to suppress a warning from this rule when the default implementation of the equality operator provides the correct behavior for the type.
 
-## Example
+## Example 1
 The following example defines a type (`BadAddableType`) that violates this rule. This type should implement the equality operator to make any two instances that have the same field values test `true` for equality. The type `GoodAddableType` shows the corrected implementation. Note that this type also implements the inequality operator and overrides <xref:System.Object.Equals%2A> to satisfy other rules. A complete implementation would also implement <xref:System.Object.GetHashCode%2A>.
 
 [!code-csharp[FxCop.Design.AddAndSubtract#1](../code-quality/codesnippet/CSharp/ca1013-overload-operator-equals-on-overloading-add-and-subtract_1.cs)]
 
-## Example
+## Example 2
 The following example tests for equality by using instances of the types that were previously defined in this topic to illustrate the default and correct behavior for the equality operator.
 
 [!code-csharp[FxCop.Design.TestAddAndSubtract#1](../code-quality/codesnippet/CSharp/ca1013-overload-operator-equals-on-overloading-add-and-subtract_2.cs)]

docs/code-quality/ca2147.md

@@ -45,12 +45,12 @@ To resolve the issue, either mark the code that calls the Assert with the <xref:
 ## When to suppress warnings
 Do not suppress a message from this rule.
 
-## Example
+## Example 1
 This code will fail if `SecurityTestClass` is transparent, when the `Assert` method throws a <xref:System.InvalidOperationException>.
 
 [!code-csharp[FxCop.Security.CA2147.TransparentMethodsMustNotUseSecurityAsserts#1](../code-quality/codesnippet/CSharp/ca2147-transparent-methods-may-not-use-security-asserts_1.cs)]
 
-## Example
+## Example 2
 One option is to code review the SecurityTransparentMethod method in the example below, and if the method is considered safe for elevation, mark SecurityTransparentMethod with secure-critical. This requires that a detailed, complete, and error-free security audit must be performed on the method together with any call-outs that occur within the method under the Assert:
 
 [!code-csharp[FxCop.Security.SecurityTransparentCode2#1](../code-quality/codesnippet/CSharp/ca2147-transparent-methods-may-not-use-security-asserts_2.cs)]

docs/code-quality/ca2202.md

@@ -45,7 +45,7 @@ To fix a violation of this rule, change the implementation so that regardless of
 
 Do not suppress a warning from this rule. Even if <xref:System.IDisposable.Dispose%2A> for the object is known to be safely callable multiple times, the implementation might change in the future.
 
-## Example
+## Example 1
 
 Nested `using` statements (`Using` in Visual Basic) can cause violations of the CA2202 warning. If the IDisposable resource of the nested inner `using` statement contains the resource of the outer `using` statement, the `Dispose` method of the nested resource releases the contained resource. When this situation occurs, the `Dispose` method of the outer `using` statement attempts to dispose its resource for a second time.
 
@@ -61,7 +61,7 @@ using (Stream stream = new FileStream("file.txt", FileMode.OpenOrCreate))
 }
 ```
 
-## Example
+## Example 2
 
 To resolve this issue, use a `try`/`finally` block instead of the outer `using` statement. In the `finally` block, make sure that the `stream` resource is not null.
 

docs/code-quality/ca2240.md

@@ -45,13 +45,13 @@ To fix a violation of this rule, make the <xref:System.Runtime.Serialization.ISe
 ## When to suppress warnings
 Do not suppress a warning from this rule.
 
-## Example
+## Example 1
 The following example shows two serializable types that violate the rule.
 
 [!code-csharp[FxCop.Usage.ImplementISerializableCorrectly#1](../code-quality/codesnippet/CSharp/ca2240-implement-iserializable-correctly_1.cs)]
 [!code-vb[FxCop.Usage.ImplementISerializableCorrectly#1](../code-quality/codesnippet/VisualBasic/ca2240-implement-iserializable-correctly_1.vb)]
 
-## Example
+## Example 2
 The following example fixes the two previous violations by providing an overrideable implementation of <xref:System.Runtime.Serialization.ISerializable.GetObjectData%2A> on the Book class and by providing an implementation of `GetObjectData` on the Library class.
 
 [!code-csharp[FxCop.Usage.ImplementISerializableCorrectly2#1](../code-quality/codesnippet/CSharp/ca2240-implement-iserializable-correctly_2.cs)]

docs/data-tools/handle-a-concurrency-exception.md

@@ -177,7 +177,7 @@ Add the following code below the code that was added in the previous section:
 [!code-csharp[VbRaddataConcurrency#3](../data-tools/codesnippet/CSharp/handle-a-concurrency-exception_4.cs)]
 [!code-vb[VbRaddataConcurrency#3](../data-tools/codesnippet/VisualBasic/handle-a-concurrency-exception_4.vb)]
 
-## Test the form
+## Test the form behavior
 
 You can now test the form to make sure it behaves as expected. To simulate a concurrency violation, you change data in the database after filling the NorthwindDataSet.
 

docs/debugger/graphics/0x-2x-4x-msaa-variants.md

@@ -48,7 +48,7 @@ Overrides multi-sample anti-aliasing (MSAA) settings on all render targets and s
 
  When playback detects these kinds of conflicts, it makes a best effort to replicate the intended behavior, but it might not be possible to match its results exactly. Although it's uncommon for this to affect the performance of these variants in a way that misrepresents their impact, it is possible—for example, when flow control in a pixel shader is determined by the precise content of a texture—because the replicated texture might not have identical contents.
 
-## Example
+## Example 1
  These variants can be reproduced for render targets created by using `ID3D11Device::CreateTexture2D` by using code like this:
 
 ```cpp
@@ -59,7 +59,7 @@ target_description.SampleDesc.Quality = 0;
 d3d_device->CreateTexture2D(&target_description, nullptr, &render_target);
 ```
 
-## Example
+## Example 2
  Or for swap chains created by using IDXGISwapChain::CreateSwapChain or D3D11CreateDeviceAndSwapChain by using code like this:
 
 ```cpp

docs/debugger/graphics/point-bilinear-trilinear-and-anisotropic-texture-filtering-variants.md

@@ -55,7 +55,7 @@ Overrides the filtering mode on appropriate texture samplers.
 ## Restrictions and limitations
  In Direct3D, feature level 9.1 specifies a maximum anisotropy of 2x. Because the **Anisotropic Texture Filtering** variant attempts to use 16x anisotropy exclusively, playback fails when frame analysis is run on a feature-level 9.1 device. Contemporary devices that are affected by this limitation include the ARM-based Surface RT and Surface 2 Windows tablets. Older GPUs that might still be found in some computers can also be affected, but they're widely considered to be obsolete and are increasingly uncommon.
 
-## Example
+## Example 1
  The **Point Texture Filtering** variant can be reproduced by using code like this:
 
 ```cpp
@@ -69,7 +69,7 @@ d3d_device->CreateSamplerState(&sampler_desc, &sampler);
 d3d_context->PSSetSamplers(0, 1, &sampler
 ```
 
-## Example
+## Example 2
  The **Bilinear Texture Filtering** variant can be reproduced by using code like this:
 
 ```cpp
@@ -83,7 +83,7 @@ d3d_device->CreateSamplerState(&sampler_desc, &sampler);
 d3d_context->PSSetSamplers(0, 1, &sampler
 ```
 
-## Example
+## Example 3
  The **Trilinear Texture Filtering** variant can be reproduced by using code like this:
 
 ```cpp
@@ -97,7 +97,7 @@ d3d_device->CreateSamplerState(&sampler_desc, &sampler);
 d3d_context->PSSetSamplers(0, 1, &sampler
 ```
 
-## Example
+## Example 4
  The **Anisotropic Texture Filtering** variant can be reproduced by using code like this:
 
 ```cpp

docs/debugger/how-to-write-a-run-time-error-reporting-function.md

@@ -24,7 +24,7 @@ A custom reporting function for run-time errors must have the same declaration a
 
 The following example shows how to define a custom reporting function.
 
-## Example
+## Example 1
 
 ```cpp
 #include <stdio.h>
@@ -55,7 +55,7 @@ int MyErrorFunc(int errorType, const wchar_t *filename,
 }
 ```
 
-## Example
+## Example 2
 The following example shows a more complex custom reporting function. In this example, the switch statement handles various error types, as defined by the `reportType` parameter of `_CrtDbgReportW`. Because you are replacing `_CrtDbgReportW`, you cannot use `_CrtSetReportMode`. Your function must handle the output. The first variable argument in this function takes a run-time error number. For more information, see [_RTC_SetErrorType](/cpp/c-runtime-library/reference/rtc-seterrortype).
 
 ```cpp
@@ -100,7 +100,7 @@ int Catch_RTC_Failure(int errType, const wchar_t *file, int line,
 #pragma runtime_checks("", restore)
 ```
 
-## Example
+## Example 3
 Use `_RTC_SetErrorFuncW` to install your custom function in place of `_CrtDbgReportW`. For more information, see [_RTC_SetErrorFuncW](/cpp/c-runtime-library/reference/rtc-seterrorfuncw). The `_RTC_SetErrorFuncW` return value is the previous reporting function, which you can save and restore if necessary.
 
 ```cpp

docs/debugger/limitations-on-wcf-debugging.md

@@ -70,7 +70,6 @@ There are three ways that you can begin debugging a WCF service:
 ## Self-Hosting
  A *self-hosted service* is a WCF service that does not run inside IIS, the WCF Service Host, or the [!INCLUDE[vstecasp](../code-quality/includes/vstecasp_md.md)] Development Server. For information about how to debug a self-hosted service, see [How to: Debug a Self-Hosted WCF Service](../debugger/how-to-debug-a-self-hosted-wcf-service.md).
 
-## Self-Hosting
  To enable debugging of [!INCLUDE[vstecasp](../code-quality/includes/vstecasp_md.md)] 3.0 or 3.5 applications, [!INCLUDE[vstecasp](../code-quality/includes/vstecasp_md.md)] 3.0 or 3.5 must be installed before [!INCLUDE[vs_dev10_long](../code-quality/includes/vs_dev10_long_md.md)] is installed. If [!INCLUDE[vs_dev10_long](../code-quality/includes/vs_dev10_long_md.md)] is installed before [!INCLUDE[vstecasp](../code-quality/includes/vstecasp_md.md)] 3.0 or 3.5, an error occurs when you try to debug a [!INCLUDE[vstecasp](../code-quality/includes/vstecasp_md.md)] 3.0 or 3.5 application. The error message is, "Unable to Automatically Step Into the Server." To fix this problem, use the Windows **Control Panel** > **Programs and Features** to repair your [!INCLUDE[vs_dev10_long](../code-quality/includes/vs_dev10_long_md.md)] installation.
 
 ## See also

docs/deployment/dependency-element-clickonce-deployment.md

@@ -122,7 +122,7 @@ Identifies the version of the application to install, and the location of the ap
 ## Remarks
  Deployment manifests typically have a single `assemblyIdentity` element that identifies the name and version of the application manifest.
 
-## Example
+## Example 1
  The following code example shows a `dependency` element in a [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] deployment manifest.
 
 ```xml
@@ -141,7 +141,7 @@ Identifies the version of the application to install, and the location of the ap
 </dependency>
 ```
 
-## Example
+## Example 2
  The following code example specifies a dependency on an assembly already installed in the GAC.
 
 ```xml
@@ -152,7 +152,7 @@ Identifies the version of the application to install, and the location of the ap
 </dependency>
 ```
 
-## Example
+## Example 3
  The following code example specifies a dependency on a specific version of the common language runtime.
 
 ```xml
@@ -163,7 +163,7 @@ Identifies the version of the application to install, and the location of the ap
 </dependency>
 ```
 
-## Example
+## Example 4
  The following code example specifies an operating system dependency.
 
 ```xml

docs/extensibility/binding-keyboard-shortcuts-to-menu-items.md

@@ -75,7 +75,7 @@ To bind a keyboard shortcut to a custom menu command, just add an entry to the *
 
    To make the command available only in a custom editor, set the `editor` attribute to the name of the custom editor that was generated by the [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] Package Template when you created the VSPackage that includes the custom editor. To find the name value, look in the `<Symbols>` section for a `<GuidSymbol>` node whose `name` attribute ends in "`editorfactory`." This is the name of the custom editor.
 
-## Example
+## Example 1
  This example binds the keyboard shortcut **Ctrl**+**Alt**+**C** to a command named `cmdidMyCommand` in a package named `MyPackage`.
 
 ```
@@ -92,7 +92,7 @@ To bind a keyboard shortcut to a custom menu command, just add an entry to the *
 </CommandTable>
 ```
 
-## Example
+## Example 2
  This example binds the keyboard shortcut **Ctrl**+**B** to a command named `cmdidBold` in a project named `TestEditor`. The command is available only in the custom editor and not in other editors.
 
 ```xml

docs/extensibility/internals/registering-a-project-type.md

@@ -23,7 +23,7 @@ When you create a new project type, you must create registry entries that enable
 
  The following examples are from HKEY_CLASSES_ROOT.
 
-## Example
+## Example 1
 
 ```
 \.figp
@@ -52,7 +52,7 @@ When you create a new project type, you must create registry entries that enable
 
  The following examples are from HKEY_LOCAL_MACHINE and are located in the registry under the key [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\99.0Exp\Packages].
 
-## Example
+## Example 2
 
 ```
 \{ACEF4EB2-57CF-11D2-96F4-000000000000} (The CLSID for the VSPackage)
@@ -89,7 +89,7 @@ When you create a new project type, you must create registry entries that enable
 
  All the following examples are located in the registry under the key [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0Exp\Projects].
 
-## Example
+## Example 3
 
 ```
 \{C061DB26-5833-11D2-96F5-000000000000} (The CLSID for projects of this type)
@@ -153,7 +153,7 @@ When you create a new project type, you must create registry entries that enable
 
  All the following examples are located in the registry under the key [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0Exp\Projects].
 
-## Example
+## Example 4
 
 ```
 {FE3BBBB6-72D5-11d2-9ACE-00C04F79A2A4} (The CLSID for Enterprise Projects)
@@ -173,7 +173,7 @@ When you create a new project type, you must create registry entries that enable
 
  All the following examples are located in the registry under the key [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0Exp\Projects].
 
-## Example
+## Example 5
 
 ```
 \{A2FE74E1-B743-11d0-AE1A-00A0C90FFFC3} (CLSID for Miscellaneous Files projects)
@@ -194,7 +194,7 @@ When you create a new project type, you must create registry entries that enable
 
  The following example is located in the registry under the key [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0Exp\Menus].
 
-## Example
+## Example 6
 
 ```
 "{ACEF4EB2-57CF-11D2-96F4-000000000000}"=",1000,1"

docs/profiling/collecting-concurrency-data-for-an-aspnet-web-application.md

@@ -49,5 +49,5 @@ The concurrency method of [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.m
 
 - [Concurrency Visualizer](../profiling/concurrency-visualizer.md)
 
-## Reference
+## See also
 - [Command-line profiling tools reference](../profiling/command-line-profiling-tools-reference.md)

docs/profiling/profile-currentid.md

@@ -15,14 +15,14 @@ ms.workload:
 # PROFILE_CURRENTID
 The PROFILE_CURRENTID returns the pseudo-token for the thread ID or process ID, in a call to NameProfile, StartProfile, StopProfile, SuspendProfile, and ResumeProfile functions. Use it to cause the function to operate on the current thread or process, rather than a specifically indicated one.
 
-## Example
+## Example 1
  PROFILE_CURRENTID is defined in *VSPerf.h* as:
 
 ```cpp
 static const unsigned int PROFILE_CURRENTID = (unsigned int)-1;
 ```
 
-## Example
+## Example 2
  The following example illustrates PROFILE_CURRENTID. The example uses PROFILE_CURRENTID as a parameter identifying the current thread in a call to the [StartProfile](../profiling/startprofile.md) function.
 
 ```cpp