Merge pull request #109780 from CarlRabeler/sqldwcontextualedits

First pass - update existing TOC links

Author: PMEds28

articles/azure-monitor/log-query/query-language.md

@@ -10,6 +10,7 @@ ms.date: 01/11/2019
 ---
 
 # Azure Monitor log queries
+
 Azure Monitor logs are built on Azure Data Explorer, and Azure Monitor log queries use a version of the same Kusto query language. The [Kusto query language documentation](/azure/kusto/query) has all of the details for the language and should be your primary resource for writing Azure Monitor log queries. This page provides links to other resources for learning how to write queries and on differences with the Azure Monitor implementation of the language.
 
 [!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-log-analytics-rebrand.md)]
@@ -20,6 +21,7 @@ Azure Monitor logs are built on Azure Data Explorer, and Azure Monitor log queri
 - [Get started with Azure Monitor log queries](get-started-queries.md) is a lesson for writing queries using Azure Monitor log data.
 
 ## Concepts
+
 - [Analyze log data in Azure Monitor](../../azure-monitor/log-query/log-query-overview.md) gives a brief overview of log queries and describes how Azure Monitor log data is structured.
 - [Viewing and analyzing log data in Azure Monitor](../../azure-monitor/log-query/portals.md) explains the portals where you create and run log queries.
 
@@ -30,17 +32,14 @@ Azure Monitor logs are built on Azure Data Explorer, and Azure Monitor log queri
 - [Standard properties in Azure Monitor log records](../../azure-monitor/platform/log-standard-properties.md) describes properties that are standard to all Azure Monitor log data.
 - [Perform cross-resource log queries in Azure Monitor](../../azure-monitor/log-query/cross-workspace-query.md) describes how to write log queries that use data from multiple Log Analytics workspaces and Application Insights applications.
 
-
 ## Examples
 
 - [Azure Monitor log query examples](examples.md) provides example queries using Azure Monitor log data.
 
-
-
 ## Lessons
 
 - [Working with strings in Azure Monitor log queries](string-operations.md) describes how to work with string data.
-- [Working with date time values in Azure Monitor log queries](datetime-operations.md) describes how to work with date and time data. 
+- [Working with date time values in Azure Monitor log queries](datetime-operations.md) describes how to work with date and time data.
 - [Aggregations in Azure Monitor log queries](aggregations.md) and [Advanced aggregations in Azure Monitor log queries](advanced-aggregations.md) describe how to aggregate and summarize data.
 - [Joins in Azure Monitor log queries](joins.md) describes how to join data from multiple tables.
 - [Working with JSON and data Structures in Azure Monitor log queries](json-data-structures.md) describes how to parse json data.
@@ -49,9 +48,9 @@ Azure Monitor logs are built on Azure Data Explorer, and Azure Monitor log queri
 
 ## Cheatsheets
 
--  [SQL to Azure Monitor log query](sql-cheatsheet.md) assists users who are already familiar with SQL.
--  [Splunk to Azure Monitor log query](splunk-cheatsheet.md) assists users who are already familiar with Splunk.
- 
+- [SQL to Azure Monitor log query](sql-cheatsheet.md) assists users who are already familiar with SQL.
+- [Splunk to Azure Monitor log query](splunk-cheatsheet.md) assists users who are already familiar with Splunk.
+
 ## Next steps
 
 - Access the complete [reference documentation for the Kusto query language](/azure/kusto/query/).

articles/azure-resource-manager/management/move-resource-group-and-subscription.md

@@ -102,7 +102,7 @@ For illustration purposes, we have only one dependent resource.
 
 * Step 1: If dependent resources are distributed across different resource groups, first move them into one resource group.
 * Step 2: Move the resource and dependent resources together from the source subscription to the target subscription.
-* Step 3: Optionally, redistribute the dependent resources to different resource groups within the target subscription. 
+* Step 3: Optionally, redistribute the dependent resources to different resource groups within the target subscription.
 
 ## Validate move
 
@@ -255,8 +255,9 @@ When moving a resource, its dependent resources must either exist in the destina
 For example, moving a virtual machine could require moving seven resource types with three different resource providers. Those resource providers and types are:
 
 * Microsoft.Compute
-   * virtualMachines
-   * disks
+
+  * virtualMachines
+  * disks
 * Microsoft.Network
   * networkInterfaces
   * publicIPAddresses
@@ -267,7 +268,7 @@ For example, moving a virtual machine could require moving seven resource types
 
 Another common example involves moving a virtual network. You may have to move several other resources associated with that virtual network. The move request could require moving public IP addresses, route tables, virtual network gateways, network security groups, and others.
 
-**Question: Why can’t I move some resources in Azure?**
+**Question: Why can't I move some resources in Azure?**
 
 Currently, not all resources in Azure support move. For a list of resources that support move, see [Move operation support for resources](move-support-resources.md).
 

articles/storage/blobs/storage-blobs-introduction.md

@@ -34,35 +34,35 @@ A storage account provides a unique namespace in Azure for your data. Every obje
 For example, if your storage account is named *mystorageaccount*, then the default endpoint for Blob storage is:
 
 ```
-http://mystorageaccount.blob.core.windows.net 
+http://mystorageaccount.blob.core.windows.net
 ```
 
 To create a storage account, see [Create a storage account](../common/storage-account-create.md). To learn more about storage accounts, see [Azure storage account overview](../common/storage-account-overview.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json).
 
 ### Containers
 
-A container organizes a set of blobs, similar to a directory in a file system. A storage account can include an unlimited number of containers, and a container can store an unlimited number of blobs. 
+A container organizes a set of blobs, similar to a directory in a file system. A storage account can include an unlimited number of containers, and a container can store an unlimited number of blobs.
 
-  > [!NOTE]
-  > The container name must be lowercase. For more information about naming containers, see [Naming and Referencing Containers, Blobs, and Metadata](https://docs.microsoft.com/rest/api/storageservices/Naming-and-Referencing-Containers--Blobs--and-Metadata).
+> [!NOTE]
+> The container name must be lowercase. For more information about naming containers, see [Naming and Referencing Containers, Blobs, and Metadata](/rest/api/storageservices/Naming-and-Referencing-Containers--Blobs--and-Metadata).
 
 ### Blobs
- 
+
 Azure Storage supports three types of blobs:
 
 - **Block blobs** store text and binary data, up to about 4.7 TB. Block blobs are made up of blocks of data that can be managed individually.
 - **Append blobs** are made up of blocks like block blobs, but are optimized for append operations. Append blobs are ideal for scenarios such as logging data from virtual machines.
 - **Page blobs** store random access files up to 8 TB in size. Page blobs store virtual hard drive (VHD) files and serve as disks for Azure virtual machines. For more information about page blobs, see [Overview of Azure page blobs](storage-blob-pageblob-overview.md)
 
-For more information about the different types of blobs, see [Understanding Block Blobs, Append Blobs, and Page Blobs](https://docs.microsoft.com/rest/api/storageservices/understanding-block-blobs--append-blobs--and-page-blobs).
+For more information about the different types of blobs, see [Understanding Block Blobs, Append Blobs, and Page Blobs](/rest/api/storageservices/understanding-block-blobs--append-blobs--and-page-blobs).
 
 ## Move data to Blob storage
 
 A number of solutions exist for migrating existing data to Blob storage:
 
-- **AzCopy** is an easy-to-use command-line tool for Windows and Linux that copies data to and from Blob storage, across containers, or across storage accounts. For more information about AzCopy, see [Transfer data with the AzCopy v10 (Preview)](../common/storage-use-azcopy-v10.md). 
-- The **Azure Storage Data Movement library** is a .NET library for moving data between Azure Storage services. The AzCopy utility is built with the Data Movement library. For more information, see the [reference documentation](/dotnet/api/microsoft.azure.storage.datamovement) for the Data Movement library. 
-- **Azure Data Factory** supports copying data to and from Blob storage by using the account key, a shared access signature, a service principal, or managed identities for Azure resources. For more information, see [Copy data to or from Azure Blob storage by using Azure Data Factory](https://docs.microsoft.com/azure/data-factory/connector-azure-blob-storage?toc=%2fazure%2fstorage%2fblobs%2ftoc.json). 
+- **AzCopy** is an easy-to-use command-line tool for Windows and Linux that copies data to and from Blob storage, across containers, or across storage accounts. For more information about AzCopy, see [Transfer data with the AzCopy v10 (Preview)](../common/storage-use-azcopy-v10.md).
+- The **Azure Storage Data Movement library** is a .NET library for moving data between Azure Storage services. The AzCopy utility is built with the Data Movement library. For more information, see the [reference documentation](/dotnet/api/microsoft.azure.storage.datamovement) for the Data Movement library.
+- **Azure Data Factory** supports copying data to and from Blob storage by using the account key, a shared access signature, a service principal, or managed identities for Azure resources. For more information, see [Copy data to or from Azure Blob storage by using Azure Data Factory](../../data-factory/connector-azure-blob-storage.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json).
 - **Blobfuse** is a virtual file system driver for Azure Blob storage. You can use blobfuse to access your existing block blob data in your Storage account through the Linux file system. For more information, see [How to mount Blob storage as a file system with blobfuse](storage-how-to-mount-container-linux.md).
 - **Azure Data Box** service is available to transfer on-premises data to Blob storage when large datasets or network constraints make uploading data over the wire unrealistic. Depending on your data size, you can request [Azure Data Box Disk](../../databox/data-box-disk-overview.md), [Azure Data Box](../../databox/data-box-overview.md), or [Azure Data Box Heavy](../../databox/data-box-heavy-overview.md) devices from Microsoft. You can then copy your data to those devices and ship them back to Microsoft to be uploaded into Blob storage.
 - The **Azure Import/Export service** provides a way to import or export large amounts of data to and from your storage account using hard drives that you provide. For more information, see [Use the Microsoft Azure Import/Export service to transfer data to Blob storage](../common/storage-import-export-service.md).

articles/synapse-analytics/sql-data-warehouse/analyze-your-workload.md

@@ -63,7 +63,7 @@ Synapse SQL has the following wait types:
 * **LocalQueriesConcurrencyResourceType**: Queries that sit outside of the concurrency slot framework. DMV queries and system functions such as `SELECT @@VERSION` are examples of local queries.
 * **UserConcurrencyResourceType**: Queries that sit inside the concurrency slot framework. Queries against end-user tables represent examples that would use this resource type.
 * **DmsConcurrencyResourceType**: Waits resulting from data movement operations.
-* **BackupConcurrencyResourceType**: This wait indicates that a database is being backed up. The maximum value for this resource type is 1. If multiple backups have been requested at the same time, the others queue. In general, we recommend a minimum time between consecutive snapshots of 10 minutes. 
+* **BackupConcurrencyResourceType**: This wait indicates that a database is being backed up. The maximum value for this resource type is 1. If multiple backups have been requested at the same time, the others queue. In general, we recommend a minimum time between consecutive snapshots of 10 minutes.
 
 The `sys.dm_pdw_waits` DMV can be used to see which resources a request is waiting for.