Merge pull request #292551 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

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

@@ -20,7 +20,7 @@ If your move requires setting up new dependent resources, you'll experience an i
 Moving a resource only moves it to a new resource group or subscription. It doesn't change the location of the resource.
 
 > [!NOTE]  
-> You can't move Azure resources to another resource group or another subscription if there's a read-only lock, whether in the source or in the destination. 
+> Azure resources can't be moved if a read-only lock exists on the source or destination resource group or subscription.
 
 ## Changed resource ID
 

articles/digital-twins/how-to-enable-private-link.md

@@ -266,6 +266,9 @@ Here are some common issues that might arise when using Private Link with Azure
 
 For more Private Link troubleshooting suggestions, see [Troubleshoot Azure Private Endpoint connectivity problems](../private-link/troubleshoot-private-endpoint-connectivity.md).
 
+## Limitation:
+   Cross-tenant scenarios are not supported by Azure Digital Twins.
+
 ## Next steps
 
 Quickly set up a protected environment with Private Link using an ARM template: [Azure Digital Twins with Azure function and Private Link](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.digitaltwins/digitaltwins-with-function-private-link).

articles/event-hubs/event-hubs-availability-and-consistency.md

@@ -52,7 +52,7 @@ You can also use the [EventHubProducerClient.SendAsync](/dotnet/api/azure.messag
 ```csharp
 var sendEventOptions  = new SendEventOptions { PartitionKey = "cities" };
 // create the events array
-producer.SendAsync(events, sendOptions)
+producer.SendAsync(events, sendEventOptions)
 ```
 
 

articles/storage/blobs/storage-performance-checklist.md

@@ -98,7 +98,7 @@ Understanding how Azure Storage partitions your blob data is useful for enhancin
 
 Blob storage uses a range-based partitioning scheme for scaling and load balancing. Each blob has a partition key comprised of the full blob name (account+container+blob). The partition key is used to partition blob data into ranges. The ranges are then load-balanced across Blob storage.
 
-Range-based partitioning means that naming conventions that use  lexical ordering (for example, *mypayroll*, *myperformance*, *myemployees*, etc.) or timestamps (*log20160101*, *log20160102*, *log20160102*, etc.) are more likely to result in the partitions being co-located on the same partition server until increased load requires that they're split into smaller ranges. Co-locating blobs on the same partition server enhances performance, so an important part of performance enhancement involves naming blobs in a way that organizes them most effectively.
+Range-based partitioning means that naming conventions that use  lexical ordering (for example, *mypayroll*, *myperformance*, *myemployees*, etc.) or timestamps (*log20160101*, *log20160102*, *log20160102*, etc.) are more likely to result in the partitions being co-located on the same partition server until increased load requires that they're split into smaller ranges. Co-locating blobs on the same partition server impacts performance, so an important part of performance enhancement involves naming blobs in a way that organizes them most effectively.
 
 For example, all blobs within a container can be served by a single server until the load on these blobs requires further rebalancing of the partition ranges. Similarly, a group of lightly loaded accounts with their names arranged in lexical order may be served by a single server until the load on one or all of these accounts require them to be split across multiple partition servers.