Merge pull request #192633 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/iot-edge/how-to-connect-downstream-iot-edge-device.md

@@ -576,13 +576,13 @@ Learn more about the [Defender for IoT micro agent](../defender-for-iot/device-b
 
 1. Open a terminal on the leaf device.
 
-1. Use the following command to place the connection string encoded in utf-8 in the Defender for Cloud agent directory into the file `connection_string.txt` in the following path: `/var/defender_iot_micro_agent/connection_string.txt`:
+1. Use the following command to place the connection string encoded in utf-8 in the Defender for Cloud agent directory into the file `connection_string.txt` in the following path: `/etc/defender_iot_micro_agent/connection_string.txt`:
 
     ```bash
-    sudo bash -c 'echo "<connection string>" > /var/defender_iot_micro_agent/connection_string.txt'
+    sudo bash -c 'echo "<connection string>" > /etc/defender_iot_micro_agent/connection_string.txt'
     ```
 
-    The `connection_string.txt` should now be located in the following path location `/var/defender_iot_micro_agent/connection_string.txt`.
+    The `connection_string.txt` should now be located in the following path location `/etc/defender_iot_micro_agent/connection_string.txt`.
 
 1. Restart the service using this command:  
 

articles/machine-learning/how-to-enable-studio-virtual-network.md

@@ -71,7 +71,7 @@ In this article, you learn how to:
 * When the storage account is in the VNet, there are extra validation requirements when using studio:
 
     * If the storage account uses a __service endpoint__, the workspace private endpoint and storage service endpoint must be in the same subnet of the VNet.
-    * If the storage account uses a __private endpoint__, the workspace private endpoint and storage service endpoint must be in the same VNet. In this case, they can be in different subnets.
+    * If the storage account uses a __private endpoint__, the workspace private endpoint and storage private endpoint must be in the same VNet. In this case, they can be in different subnets.
 
 ### Designer sample pipeline
 

articles/virtual-network-manager/concept-network-manager-scope.md

@@ -37,7 +37,7 @@ In this article, you'll learn about how Azure Virtual Network Manager uses the c
 A *scope* within Azure Virtual Network Manager is a set of resources where features can be applied to. When specifying a scope, you're limiting the access to which Network Manager can manage resources for. The value for the scope can be at the management group level or at the subscription level. See [Azure management groups](../governance/management-groups/overview.md), to learn how to manage your resource hierarchy. When you select a management group as the scope, all child resources are included within the scope. 
 
 > [!NOTE]
-> You can't create multiple Azure Virtual Network Manager with an overlapping scope of the same hierarchy and the same features selected.
+> You can't create multiple Azure Virtual Network Manager instances with an overlapping scope of the same hierarchy and the same features selected.
 > 
 
 ## Features

includes/front-door-limits.md

@@ -87,5 +87,6 @@
 * Maximum rules engine action header value character: 640 characters.
 * Maximum rules engine condition header value character: 256 characters.
 * Maximum ETag header size: 128 bytes
+* Maximum endhpoint name for Standard and Premium: 46 characters.
 
 For more information about limits that apply to Rules Engine configurations, see [Rules Engine terminology](../articles/frontdoor/front-door-rules-engine.md#terminology)