Merge pull request #227472 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: huypub

articles/azure-cache-for-redis/cache-web-app-howto.md

@@ -68,7 +68,7 @@ Because the file *CacheSecrets.config* isn't deployed to Azure with your applica
 
      :::image type="content" source="media/cache-web-app-howto/cache-web-config.png" alt-text="Web.config":::
 
-1. In the *web.config* file, you can how to set the `<appSetting>` element for running the application locally.
+1. In the *web.config* file, you can set the `<appSettings>` element for running the application locally.
 
     `<appSettings file="C:\AppSecrets\CacheSecrets.config">`
 

articles/azure-sql-edge/release-notes.md

@@ -14,6 +14,14 @@ services: sql-edge
 
 This article describes what's new and what has changed with every new build of Azure SQL Edge.
 
+## Azure SQL Edge 1.0.7
+
+SQL engine build 15.0.2000.1574
+
+### What's new?
+
+- Security bug fixes
+
 ## Azure SQL Edge 1.0.6
 
 SQL engine build 15.0.2000.1565

articles/dns/private-dns-autoregistration.md

@@ -24,7 +24,6 @@ To enable auto registration, select the checkbox for "Enable auto registration"
 * Auto registration works only for virtual machines. For all other resources like internal load balancers, you can create DNS records manually in the private DNS zone linked to the virtual network.
 * DNS records are created automatically only for the primary virtual machine NIC. If your virtual machines have more than one NIC, you can manually create the DNS records for other network interfaces.
 * DNS records are created automatically only if the primary virtual machine NIC is using DHCP. If you're using static IPs, such as a configuration with [multiple IP addresses in Azure](../virtual-network/ip-services/virtual-network-multiple-ip-addresses-portal.md#os-config), auto registration doesn't create records for that virtual machine.
-* Auto registration for IPv6 (AAAA records) isn't supported.
 * A specific virtual network can be linked to only one private DNS zone when automatic VM DNS registration is enabled. You can, however, link multiple virtual networks to a single DNS zone.
 
 ## Next steps

articles/dns/private-dns-scenarios.md

@@ -1,6 +1,6 @@
 ---
-title: Scenarios for Private Zones - Azure DNS
-description: In this article, learn about common scenarios for using Azure DNS Private Zones.
+title: Scenarios for Azure Private DNS zones
+description: In this article, learn about common scenarios for using Azure Private DNS zones.
 services: dns
 author: greg-lindsay
 ms.service: dns
@@ -9,9 +9,9 @@ ms.date: 09/27/2022
 ms.author: greglin
 ---
 
-# Azure DNS private zones scenarios
+# Azure Private DNS zones scenarios
 
-Azure DNS Private Zones provide name resolution within a virtual network and between virtual networks. In this article, we'll look at some common scenarios that can benefit using this feature.
+Azure Private DNS zones provide name resolution within a virtual network and between virtual networks. In this article, we'll look at some common scenarios that can benefit using this feature.
 
 ## Scenario: Name resolution scoped to a single virtual network
 
@@ -44,9 +44,9 @@ Now when an internet client does a DNS query for `VNETA-VM1.contoso.com`, Azure
 ![Split Brian resolution](./media/private-dns-scenarios/split-brain-resolution.png)
 
 ## Next steps
-To learn more about private DNS zones, see [Using Azure DNS for private domains](private-dns-overview.md).
+To learn more about Private DNS zones, see [Using Azure DNS for private domains](private-dns-overview.md).
 
-Learn how to [create a private DNS zone](./private-dns-getstarted-powershell.md) in Azure DNS.
+Learn how to [create a Private DNS zone](./private-dns-getstarted-powershell.md) in Azure DNS.
 
 Learn about DNS zones and records by visiting: [DNS zones and records overview](dns-zones-records.md).