Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into fixName

Author: roygara

articles/event-hubs/event-processor-balance-partition-load.md

@@ -11,7 +11,7 @@ ms.devlang: na
 ms.topic: conceptual
 ms.tgt_pltfrm: na
 ms.workload: na
-ms.date: 01/16/2020
+ms.date: 05/28/2020
 ms.author: shvija 
 
 ---
@@ -41,7 +41,7 @@ When designing the consumer in a distributed environment, the scenario must hand
 
 ## Event processor or consumer client
 
-You don't need to build your own solution to meet these requirements. The Azure Event Hubs SDKs provide this functionality. In .NET or Java SDKs, you use an event processor client (EventProcessorClient), and in Python and Java Script SDKs, you use EventHubConsumerClient. In the old version of SDK, it was the event processor host (EventProcessorHost) that supported these features.
+You don't need to build your own solution to meet these requirements. The Azure Event Hubs SDKs provide this functionality. In .NET or Java SDKs, you use an event processor client (EventProcessorClient), and in Python and JavaScript SDKs, you use EventHubConsumerClient. In the old version of SDK, it was the event processor host (EventProcessorHost) that supported these features.
 
 For the majority of production scenarios, we recommend that you use the event processor client for reading and processing events. The processor client is intended to provide a robust experience for processing events across all partitions of an event hub in a performant and fault tolerant manner while providing a means to checkpoint its progress. Event processor clients are also capable of working cooperatively within the context of a consumer group for a given event hub. Clients will automatically manage distribution and balancing of work as instances become available or unavailable for the group.
 
@@ -51,7 +51,7 @@ An event processor instance typically owns and processes events from one or more
 
 Each event processor is given a unique identifier and claims ownership of partitions by adding or updating an entry in a checkpoint store. All event processor instances communicate with this store periodically to update its own processing state as well as to learn about other active instances. This data is then used to balance the load among the active processors. New instances can join the processing pool to scale up. When instances go down, either due to failures or to scale down, partition ownership is gracefully transferred to other active processors.
 
-Partition ownership records in the checkpoint store keeps track of Event Hubs namespace,  event hub name, consumer group, event processor identifier (also known as owner), partition id and the last modified time.
+Partition ownership records in the checkpoint store keep track of Event Hubs namespace,  event hub name, consumer group, event processor identifier (also known as owner), partition ID and the last modified time.
 
 
 
@@ -89,7 +89,7 @@ When the checkpoint is performed to mark an event as processed, an entry in chec
 
 ## Thread safety and processor instances
 
-By default, event processor or consumer is thread safe and behaves in a synchronous manner. When events arrive for a partition, the function that processes the events is called. Subsequent messages and calls to this function queue up behind the scenes as the message pump continues to run in the background on other threads. This thread safety removes the need for thread-safe collections and dramatically increases performance.
+By default, the function that processes the events is called sequentially for a given partition. Subsequent events and calls to this function from the same partition queue up behind the scenes as the event pump continues to run in the background on other threads. Note that events from different partitions can be processed concurrently and any shared state that is accessed across partitions have to be synchronized.
 
 ## Next steps
 See the following quick starts:

articles/governance/resource-graph/first-query-portal.md

@@ -73,7 +73,7 @@ functions to achieve your intended results.
 After running the last query above, if you select the **Charts** tab, you get a message that "the
 result set isn't compatible with a pie chart visualization." Queries that list results can't be made
 into a chart, but queries that provide counts of resources can. Using the
-[Sample query - Count virtual machines by OS type](./samples/starter.md#count-virtual-machines-by-os-type),
+[Sample query - Count virtual machines by OS type](./samples/starter.md#count-os),
 let's create a visualization from the Resource Graph query.
 
 1. In the **Query 1** portion of the window, enter the following query and select **Run query**.

articles/governance/resource-graph/samples/advanced.md

@@ -38,7 +38,7 @@ Graph. Before running any of the following queries, check that your environment
 PowerShell](../first-query-powershell.md#add-the-resource-graph-module) for steps to install and
 validate your shell environment of choice.
 
-## <a name="apiversion" />Show resource types and API versions
+## <a name="apiversion"></a>Show resource types and API versions
 
 Resource Graph primarily uses the most recent non-preview version of a Resource Provider's API to
 `GET` resource properties during an update. In some cases, the API version used has been overridden
@@ -74,7 +74,7 @@ Search-AzGraph -Query "Resources | distinct type, apiVersion | where isnotnull(a
 
 ---
 
-## <a name="vmss-capacity" />Get virtual machine scale set capacity and size
+## <a name="vmss-capacity"></a>Get virtual machine scale set capacity and size
 
 This query looks for virtual machine scale set resources and gets various details including the
 virtual machine size and the capacity of the scale set. The query uses the `toint()` function to
@@ -111,7 +111,7 @@ Search-AzGraph -Query "Resources | where type=~ 'microsoft.compute/virtualmachin
 
 ---
 
-## <a name="remove-column" />Remove columns from results
+## <a name="remove-column"></a>Remove columns from results
 
 The following query uses `summarize` to count resources by subscription, `join` to combine it with
 subscription details from _ResourceContainers_ table, then `project-away` to remove some of the
@@ -146,7 +146,7 @@ Search-AzGraph -Query "Resources | summarize resourceCount=count() by subscripti
 
 ---
 
-## <a name="list-all-tags" />List all tag names
+## <a name="list-all-tags"></a>List all tag names
 
 This query starts with the tag and builds a JSON object listing all unique tag names and their
 corresponding types.
@@ -179,7 +179,7 @@ Search-AzGraph -Query "Resources | project tags | summarize buildschema(tags)"
 
 ---
 
-## <a name="vm-regex" />Virtual machines matched by regex
+## <a name="vm-regex"></a>Virtual machines matched by regex
 
 This query looks for virtual machines that match a [regular expression](/dotnet/standard/base-types/regular-expression-language-quick-reference)
 (known as _regex_). The **matches regex \@** allows us to define the regex to match, which is `^Contoso(.*)[0-9]+$`.
@@ -225,7 +225,7 @@ Search-AzGraph -Query "Resources | where type =~ 'microsoft.compute/virtualmachi
 
 ---
 
-## <a name="mvexpand-cosmosdb" />List Cosmos DB with specific write locations
+## <a name="mvexpand-cosmosdb"></a>List Cosmos DB with specific write locations
 
 The following query limits to Cosmos DB resources, uses `mv-expand` to expand the property bag for
 **properties.writeLocations**, then project specific fields and limit the results further to
@@ -263,7 +263,7 @@ Search-AzGraph -Query "Resources | where type =~ 'microsoft.documentdb/databasea
 
 ---
 
-## <a name="join" />Key vault with subscription name
+## <a name="join"></a>Key vault with subscription name
 
 The following query shows a complex use of `join`. The query limits the joined table to
 subscriptions resources and with `project` to include only the original field _subscriptionId_ and
@@ -302,7 +302,7 @@ Search-AzGraph -Query "Resources | join (ResourceContainers | where type=='micro
 
 ---
 
-## <a name="join-sql" />List SQL Databases and their elastic pools
+## <a name="join-sql"></a>List SQL Databases and their elastic pools
 
 The following query uses **leftouter** `join` to bring together SQL Database resources and their
 related elastic pools, if they have any.
@@ -341,7 +341,7 @@ Search-AzGraph -Query "Resources | where type =~ 'microsoft.sql/servers/database
 
 ---
 
-## <a name="join-vmpip" />List virtual machines with their network interface and public IP
+## <a name="join-vmpip"></a>List virtual machines with their network interface and public IP
 
 This query uses two **leftouter** `join` commands to bring together virtual machines, their related
 network interfaces, and any public IP address related to those network interfaces.
@@ -393,7 +393,7 @@ Search-AzGraph -Query "Resources | where type =~ 'microsoft.compute/virtualmachi
 
 ---
 
-## <a name="join-findstoragetag" />Find storage accounts with a specific tag on the resource group
+## <a name="join-findstoragetag"></a>Find storage accounts with a specific tag on the resource group
 
 The following query uses an **inner** `join` to connect storage accounts with resource groups that
 have a specified case sensitive tag name and tag value.
@@ -472,7 +472,7 @@ Search-AzGraph -Query "Resources | where type =~ 'microsoft.storage/storageaccou
 
 ---
 
-## <a name="unionresults" />Combine results from two queries into a single result
+## <a name="unionresults"></a>Combine results from two queries into a single result
 
 The following query uses `union` to get results from the _ResourceContainers_ table and add them to
 results from the _Resources_ table.
@@ -505,7 +505,7 @@ Search-AzGraph -Query "ResourceContainers | where type=='microsoft.resources/sub
 
 ---
 
-## <a name="displaynames" />Include the tenant and subscription names with DisplayNames
+## <a name="displaynames"></a>Include the tenant and subscription names with DisplayNames
 
 This query uses the new **Include** parameter with option _DisplayNames_ to add
 **subscriptionDisplayName** and **tenantDisplayName** to the results. This parameter is only

articles/governance/resource-graph/samples/starter.md

@@ -41,7 +41,7 @@ Graph. Before running any of the following queries, check that your environment
 PowerShell](../first-query-powershell.md#add-the-resource-graph-module) for steps to install and
 validate your shell environment of choice.
 
-## <a name="count-resources" />Count Azure resources
+## <a name="count-resources"></a>Count Azure resources
 
 This query returns number of Azure resources that exist in the subscriptions that you have access
 to. It's also a good query to validate your shell of choice has the appropriate Azure Resource
@@ -74,7 +74,7 @@ Search-AzGraph -Query "Resources | summarize count()"
 
 ---
 
-## <a name="count-keyvaults" />Count key vault resources
+## <a name="count-keyvaults"></a>Count key vault resources
 
 This query uses `count` instead of `summarize` to count the number of records returned. Only key
 vaults are included in the count.
@@ -107,7 +107,7 @@ Search-AzGraph -Query "Resources | where type =~ 'microsoft.keyvault/vaults' | c
 
 ---
 
-## <a name="list-resources" />List resources sorted by name
+## <a name="list-resources"></a>List resources sorted by name
 
 This query returns any type of resource, but only the **name**, **type**, and **location**
 properties. It uses `order by` to sort the properties by the **name** property in ascending (`asc`)
@@ -141,7 +141,7 @@ Search-AzGraph -Query "Resources | project name, type, location | order by name
 
 ---
 
-## <a name="show-vms" />Show all virtual machines ordered by name in descending order
+## <a name="show-vms"></a>Show all virtual machines ordered by name in descending order
 
 To list only virtual machines (which are type `Microsoft.Compute/virtualMachines`), we can match
 the property **type** in the results. Similar to the previous query, `desc` changes the `order by`
@@ -176,7 +176,7 @@ Search-AzGraph -Query "Resources | project name, location, type| where type =~ '
 
 ---
 
-## <a name="show-sorted" />Show first five virtual machines by name and their OS type
+## <a name="show-sorted"></a>Show first five virtual machines by name and their OS type
 
 This query will use `top` to only retrieve five matching records that are ordered by name. The type
 of the Azure resource is `Microsoft.Compute/virtualMachines`. `project` tells Azure Resource Graph
@@ -211,7 +211,7 @@ Search-AzGraph -Query "Resources | where type =~ 'Microsoft.Compute/virtualMachi
 
 ---
 
-## <a name="count-os" />Count virtual machines by OS type
+## <a name="count-os"></a>Count virtual machines by OS type
 
 Building on the previous query, we're still limiting by Azure resources of type
 `Microsoft.Compute/virtualMachines`, but are no longer limiting the number of records returned.
@@ -287,7 +287,7 @@ Search-AzGraph -Query "Resources | where type =~ 'Microsoft.Compute/virtualMachi
 > property is the incorrect case, a null or incorrect value is returned and the grouping or
 > summarization would be incorrect.
 
-## <a name="show-storage" />Show resources that contain storage
+## <a name="show-storage"></a>Show resources that contain storage
 
 Instead of explicitly defining the type to match, this example query will find any Azure resource
 that `contains` the word **storage**.
@@ -319,7 +319,7 @@ Search-AzGraph -Query "Resources | where type contains 'storage' | distinct type
 
 ---
 
-## <a name="list-publicip" />List all public IP addresses
+## <a name="list-publicip"></a>List all public IP addresses
 
 Similar to the previous query, find everything that is a type with the word **publicIPAddresses**.
 This query expands on that pattern to only include results where **properties.ipAddress**
@@ -355,7 +355,7 @@ Search-AzGraph -Query "Resources | where type contains 'publicIPAddresses' and i
 
 ---
 
-## <a name="count-resources-by-ip" />Count resources that have IP addresses configured by subscription
+## <a name="count-resources-by-ip"></a>Count resources that have IP addresses configured by subscription
 
 Using the previous example query and adding `summarize` and `count()`, we can get a list by subscription of resources with configured IP addresses.
 
@@ -387,7 +387,7 @@ Search-AzGraph -Query "Resources | where type contains 'publicIPAddresses' and i
 
 ---
 
-## <a name="list-tag" />List resources with a specific tag value
+## <a name="list-tag"></a>List resources with a specific tag value
 
 We can limit the results by properties other than the Azure resource type, such as a tag. In this
 example, we're filtering for Azure resources with a tag name of **Environment** that have a value
@@ -452,7 +452,7 @@ Search-AzGraph -Query "Resources | where tags.environment=~'internal' | project
 
 ---
 
-## <a name="list-specific-tag" />List all storage accounts with specific tag value
+## <a name="list-specific-tag"></a>List all storage accounts with specific tag value
 
 Combine the filter functionality of the previous example and filter Azure resource type by **type**
 property. This query also limits our search for specific types of Azure resources with a specific
@@ -489,7 +489,7 @@ Search-AzGraph -Query "Resources | where type =~ 'Microsoft.Storage/storageAccou
 > [!NOTE]
 > This example uses `==` for matching instead of the `=~` conditional. `==` is a case sensitive match.
 
-## <a name="show-aliases" />Show aliases for a virtual machine resource
+## <a name="show-aliases"></a>Show aliases for a virtual machine resource
 
 [Azure Policy aliases](../../policy/concepts/definition-structure.md#aliases) are used by Azure
 Policy to manage resource compliance. Azure Resource Graph can return the _aliases_ of a resource
@@ -526,7 +526,7 @@ Search-AzGraph -Query "Resources | where type =~ 'Microsoft.Compute/virtualMachi
 
 ---
 
-## <a name="distinct-alias-values" />Show distinct values for a specific alias
+## <a name="distinct-alias-values"></a>Show distinct values for a specific alias
 
 Seeing the value of aliases on a single resource is helpful, but it doesn't show the true value of
 using Azure Resource Graph to query across subscriptions. This example looks at all values of a
@@ -561,7 +561,7 @@ Search-AzGraph -Query "Resources | where type=~'Microsoft.Compute/virtualMachine
 
 ---
 
-## <a name="unassociated-nsgs" />Show unassociated network security groups
+## <a name="unassociated-nsgs"></a>Show unassociated network security groups
 
 This query returns Network Security Groups (NSGs) that aren't associated to a network interface or
 subnet.
@@ -595,7 +595,7 @@ Search-AzGraph -Query "Resources | where type =~ 'microsoft.network/networksecur
 
 ---
 
-## <a name="advisor-savings" />Get cost savings summary from Azure Advisor
+## <a name="advisor-savings"></a>Get cost savings summary from Azure Advisor
 
 This query summarizes the cost savings of each
 [Azure Advisor](../../../advisor/advisor-overview.md) recommendation.

articles/governance/resource-graph/tutorials/create-share-query.md

@@ -50,7 +50,7 @@ follow these steps:
    Select **Run query** to see the query results in the bottom pane.
 
    For more information about this query, see
-   [Samples – Count virtual machines by OS type](../samples/starter.md#count-virtual-machines-by-os-type).
+   [Samples – Count virtual machines by OS type](../samples/starter.md#count-os).
 
 
 1. Select **Save** or **Save as**, enter **Count VMs by OS** as the name, leave the type as
@@ -95,7 +95,7 @@ To create a new Shared query, follow these steps:
    Select **Run query** to see the query results in the bottom pane.
 
    For more information about this query, see
-   [Samples – Count virtual machines by OS type](../samples/starter.md#count-virtual-machines-by-os-type).
+   [Samples – Count virtual machines by OS type](../samples/starter.md#count-os).
 
 1. Select **Save** or **Save as**.
 

articles/machine-learning/toc.yml

@@ -454,8 +454,6 @@
     - name: Designer module reference
       displayName: module, reference, algorithm, studio
       href: algorithm-module-reference/module-reference.md
-    - name: ML at scale
-      href: /azure/architecture/data-guide/big-data/machine-learning-at-scale
     - name: Monitor data reference
       href: monitor-resource-reference.md
     - name: Machine learning pipeline YAML reference