Fixed build errors

Author: BaileyLawson

docs-conceptual/azps-2.0.0/context-persistence.md

@@ -50,7 +50,7 @@ used in your last session.
 The cmdlets that allow you to manage Azure contexts also allow you fine grained control. If you
 want changes to apply only to the current PowerShell session (`Process` scope) or every PowerShell
 session (`CurrentUser` scope). These options are discussed in more detail in [Using Context
-Scopes](#Using-Context-Scopes).
+Scopes](#using-context-scopes).
 
 ## Running Azure PowerShell cmdlets as background jobs
 

docs-conceptual/azps-2.0.0/migrate-az-1.0.0.md

@@ -20,7 +20,7 @@ This document describes the changes between the 6.x versions of AzureRM and Az v
   - [Removed modules](#removed-modules)
   - [Windows PowerShell 5.1 and .NET 4.7.2](#windows-powershell-51-and-net-472)
   - [Temporary removal of User login using PSCredential](#temporary-removal-of-user-login-using-pscredential)
-  - [Default Device Code login instead of Web Browser prompt](#temporary-default-device-code-login-instead-of-web-browser-prompt)
+  - [Default Device Code login instead of Web Browser prompt](#default-device-code-login-instead-of-web-browser-prompt)
 - [Module breaking changes](#module-breaking-changes)
   - [Az.ApiManagement (previously AzureRM.ApiManagement)](#azapimanagement-previously-azurermapimanagement)
   - [Az.Billing (previously AzureRM.Billing, AzureRM.Consumption, and AzureRM.UsageAggregates)](#azbilling-previously-azurermbilling-azurermconsumption-and-azurermusageaggregates)

docs-conceptual/azurermps-4.4.1/context-persistence.md

@@ -55,7 +55,7 @@ will need to sign in to Azure every time you open a PowerShell session.
 The cmdlets that allow you to manage Azure contexts also allow you fine grained control. If you
 want changes to apply only to the current PowerShell session (`Process` scope) or every PowerShell
 session (`CurrentUser` scope). These options are discussed in mode detail in [Using Context
-Scopes](#Using-Context-Scopes).
+Scopes](#using-context-scopes).
 
 ## Running Azure PowerShell cmdlets as background jobs
 

docs-conceptual/azurermps-5.7.0/context-persistence.md

@@ -55,7 +55,7 @@ will need to sign in to Azure every time you open a PowerShell session.
 The cmdlets that allow you to manage Azure contexts also allow you fine grained control. If you
 want changes to apply only to the current PowerShell session (`Process` scope) or every PowerShell
 session (`CurrentUser` scope). These options are discussed in mode detail in [Using Context
-Scopes](#Using-Context-Scopes).
+Scopes](#using-context-scopes).
 
 ## Running Azure PowerShell cmdlets as background jobs
 

docs-conceptual/azurermps-6.13.0/context-persistence.md

@@ -52,7 +52,7 @@ Each new PowerShell session targets the context used in your last session.
 The cmdlets that allow you to manage Azure contexts also allow you fine grained control. If you
 want changes to apply only to the current PowerShell session (`Process` scope) or every PowerShell
 session (`CurrentUser` scope). These options are discussed in mode detail in [Using Context
-Scopes](#Using-Context-Scopes).
+Scopes](#using-context-scopes).
 
 ## Running Azure PowerShell cmdlets as background jobs