Fix git push error for protected CLA branch

docs/debugger/how-to-install-a-visualizer.md

@@ -24,11 +24,12 @@ After you have created a visualizer, you must install the visualizer so that it
 > [!NOTE]
 > In UWP apps, only the standard text, HTML, XML, and JSON visualizers are supported. Custom (user-created) visualizers are not supported.
 
+::: moniker range=">=vs-2019"
 ### To install a visualizer for Visual Studio 2019
 
-1. Locate the DLL that contains the visualizer you have built.
+1. Locate the DLL that contains the visualizer you built.
 
-2. Copy the [Debugger Side](create-custom-visualizers-of-data.md#to-create-the-debugger-side) DLL to either of the following locations:
+2. Copy the [Debugger Side](create-custom-visualizers-of-data.md#to-create-the-debugger-side) DLL (and any DLLs it depends on) to either of the following locations:
 
     - *VisualStudioInstallPath* `\Common7\Packages\Debugger\Visualizers`
 
@@ -40,17 +41,22 @@ After you have created a visualizer, you must install the visualizer so that it
 
     - `My Documents\` *VisualStudioVersion* `\Visualizers\` *Framework*
 
-    Where *Framework* is either:
+    where *Framework* is either:
     - `net2.0` for debuggees running the `.NET Framework` runtime.
     - `netstandard2.0` for debuggees using a runtime that supports `netstandard 2.0` (`.NET Framework v4.6.1+` or `.NET Core 2.0+`).
     - `netcoreapp` for debuggees running the `.NET Core` runtime. (supports `.NET Core 2.0+`)
 
 4. Restart the debugging session.
 
+> [!NOTE]
+> The procedure is different in Visual Studio 2017 and older. See the [previous version](how-to-install-a-visualizer.md?view=vs-2017) of this article.
+::: moniker-end
+
+::: moniker range="vs-2017"
 ### To install a visualizer for Visual Studio 2017 and older
 
 > [!IMPORTANT]
-> Only .NET Framework visualizers are supported in Visual Studio 2017 and older
+> Only .NET Framework visualizers are supported in Visual Studio 2017 and older.
 
 1. Locate the DLL that contains the visualizer you have built.
 
@@ -64,6 +70,7 @@ After you have created a visualizer, you must install the visualizer so that it
 
 > [!NOTE]
 > If you want to use a managed visualizer for remote debugging, copy the DLL to the same path on the remote computer.
+::: moniker-end
 
 ## See also
 - [Create Custom Visualizers](../debugger/create-custom-visualizers-of-data.md)

docs/test/live-unit-testing-faq.md

@@ -128,8 +128,6 @@ There are several differences:
 
 - Live Unit Testing runs tests in each test assembly sequentially. In **Test Explorer**, you can choose to run multiple tests in parallel.
 
-- Discovery and execution of tests in Live Unit Testing uses version 2 of `TestPlatform`, whereas the **Test Explorer** window uses version 1. You won't notice a difference in most cases, though.
-
 - **Test Explorer** runs tests in a single-threaded apartment (STA) by default, whereas Live Unit Testing runs tests in a multi-threaded apartment (MTA). To run MSTest tests in STA in Live Unit Testing, decorate the test method or the containing class with the `<STATestMethod>` or `<STATestClass>` attribute that can be found in the `MSTest.STAExtensions 1.0.3-beta` NuGet package. For NUnit, decorate the test method with the `<RequiresThread(ApartmentState.STA)>` attribute, and for xUnit, with the `<STAFact>` attribute.
 
 ## Exclude tests

mac/installation.md

@@ -13,7 +13,7 @@ ms.custom: video
 To start developing native, cross-platform .NET apps on macOS, install Visual Studio 2019 for Mac following the steps below.
 
  > [!div class="button"]
- > [Download Visual Studio for Mac](https://visualstudio.microsoft.com/downloads/?utm_medium=microsoft&utm_source=docs.microsoft.com&utm_campaign=navigation+cta&utm_content=download+vsmac2019)
+ > [Download Visual Studio for Mac](https://aka.ms/vsmac)
 
 ## Requirements