Merge pull request #175994 from MicrosoftDocs/repo_sync_working_branch

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

Author: huypub

articles/cosmos-db/consistency-levels.md

@@ -10,7 +10,7 @@ ms.date: 09/20/2021
 # Consistency levels in Azure Cosmos DB
 [!INCLUDE[appliesto-all-apis](includes/appliesto-all-apis.md)]
 
-Distributed databases that rely on replication for high availability, low latency, or both, must make a fundamental tradeoff between the read consistency, availability, latency, and throughput as defined by the [PACLC theorem](https://en.wikipedia.org/wiki/PACELC_theorem). The linearizability of the strong consistency model is the gold standard of data programmability. But it adds a steep price from higher write latencies due to data having to replicate and commit across large distances. Strong consistency may also suffer from reduced availability (during failures) because data cannot replicate and commit in every region. Eventual consistency offers higher availability and better performance, but its more difficult to program applications because data may not be completely consistent across all regions.
+Distributed databases that rely on replication for high availability, low latency, or both, must make a fundamental tradeoff between the read consistency, availability, latency, and throughput as defined by the [PACELC theorem](https://en.wikipedia.org/wiki/PACELC_theorem). The linearizability of the strong consistency model is the gold standard of data programmability. But it adds a steep price from higher write latencies due to data having to replicate and commit across large distances. Strong consistency may also suffer from reduced availability (during failures) because data cannot replicate and commit in every region. Eventual consistency offers higher availability and better performance, but its more difficult to program applications because data may not be completely consistent across all regions.
 
 Most commercially available distributed NoSQL databases available in the market today provide only strong and eventual consistency. Azure Cosmos DB offers five well-defined levels. From strongest to weakest, the levels are:
 

articles/cosmos-db/how-to-configure-private-endpoints.md

@@ -133,7 +133,7 @@ $virtualNetwork = Get-AzVirtualNetwork -ResourceGroupName  $ResourceGroupName -N
  
 $subnet = $virtualNetwork | Select -ExpandProperty subnets | Where-Object  {$_.Name -eq $SubnetName}  
  
-$privateEndpoint = New-AzPrivateEndpoint -ResourceGroupName $ResourceGroupName -Name $PrivateEndpointName -Location "westcentralus" -Subnet  $subnet -PrivateLinkServiceConnection $privateEndpointConnection
+$privateEndpoint = New-AzPrivateEndpoint -ResourceGroupName $ResourceGroupName -Name $PrivateEndpointName -Location $Location -Subnet  $subnet -PrivateLinkServiceConnection $privateEndpointConnection
 ```
 
 ### Integrate the private endpoint with a private DNS zone
@@ -163,13 +163,13 @@ $networkInterface = Get-AzResource -ResourceId $pe.NetworkInterfaces[0].Id `
 
 $PrivateDnsZoneId = $zone.ResourceId
 
-$config = New-AzPrivateDnsZoneConfig -Name $zoneName`
+$config = New-AzPrivateDnsZoneConfig -Name $zoneName `
  -PrivateDnsZoneId $PrivateDnsZoneId
 
 ## Create a DNS zone group
-New-AzPrivateDnsZoneGroup -ResourceGroupName $ResourceGroupName`
- -PrivateEndpointName $PrivateEndpointName`
- -Name "MyPrivateZoneGroup"`
+New-AzPrivateDnsZoneGroup -ResourceGroupName $ResourceGroupName `
+ -PrivateEndpointName $PrivateEndpointName `
+ -Name "MyPrivateZoneGroup" `
  -PrivateDnsZoneConfig $config
 ```