Merge pull request #295225 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-functions/functions-deployment-technologies.md

@@ -85,7 +85,7 @@ The Functions host also performs a background trigger sync after the application
 
 You can request Azure Functions to perform a remote build of your code project during deployment. In these scenarios, you should request a remote build instead of building locally:
 
-+ You're deploying an app to a Linux-based function app that was developed on a Windows computer. This is commonly the case for Python app development. You can end up with in incorrect libraries being used when building the deployment package locally on Windows.
++ You're deploying an app to a Linux-based function app that was developed on a Windows computer. This is commonly the case for Python app development. You can end up with incorrect libraries being used when building the deployment package locally on Windows.
 + Your project has dependencies on a [custom package index](functions-reference-python.md#remote-build-with-extra-index-url).
 + You want to reduce the size of your deployment package.
 

articles/iot-edge/includes/iot-edge-install-linux.md

@@ -24,7 +24,7 @@ Run the following commands to add the package repository and then add the Micros
 
 Installing can be done with a few commands.  Open a terminal and run the following commands:
 
-::: moniker range=">=iotedge-1.5"
+
 
 * **24.04**:
 
@@ -34,7 +34,7 @@ Installing can be done with a few commands.  Open a terminal and run the followi
    rm packages-microsoft-prod.deb
    ```
 
-::: moniker-end
+
 
 * **22.04**:
 
@@ -56,7 +56,7 @@ Installing can be done with a few commands.  Open a terminal and run the followi
 
 Installing with APT can be done with a few commands.  Open a terminal and run the following commands:
 
-::: moniker range=">=iotedge-1.5"
+
 
 * **12 - Bookworm (arm32v7)**:
 
@@ -65,7 +65,7 @@ Installing with APT can be done with a few commands.  Open a terminal and run th
     sudo apt install ./packages-microsoft-prod.deb
     ```
 
-::: moniker-end
+
 
 * **11 - Bullseye (arm32v7)**:
 

articles/iot-operations/connect-to-cloud/howto-configure-fabric-real-time-intelligence.md

@@ -62,8 +62,7 @@ Azure Key Vault is the recommended way to sync the connection string to the Kube
     | Host                  | The hostname of the Event Stream Custom Endpoint in the format `*.servicebus.windows.net:9093`. Use the bootstrap server address noted previously. |
     | Authentication method | *SASL* is the currently the only supported authentication method. |
     | SASL type             | Choose *Plain* |
-    | Synced secret name    | Name of secret that will be synced to the Kubernetes cluster. You can choose any name. |
-    | Username reference of token secret | Create a new or choose an existing Key Vault reference. The secret value must be the literal string *$ConnectionString*. It isn't an environment variable. |
+    | Synced secret name    | Create or select a Key Vault secret where the secret's value is exactly the text **$ConnectionString** (literal string, not an environment variable reference). |
     | Password reference of token secret | Create a new or choose an existing Key Vault reference. The secret value must be the Custom Endpoint connection string noted earlier. |
 
 1. Select **Apply** to provision the endpoint.

articles/virtual-network/how-to-multiple-prefixes-subnet.md

@@ -20,7 +20,7 @@ Currently, Virtual Machine Scale Sets allows you to specify only one subnet. The
 
 The following limitations apply during the public preview:
 
-- The feature only supports virtual machines and virtual machine scale sets and doesn't support Bare Metal or SWIFT resources. Any delegated subnet can't use this feature.
+- The feature only supports virtual machines and virtual machine scale sets and doesn't support Bare Metal or PodSubnet scenario in AKS. Any delegated subnet can't use this feature.
 
 - This feature doesn't support multiple customer address (CA) configurations. When using multiple prefixes on a subnet, you're only able to use a single customer address (CA) configuration. A single IPv4 (Internet Protocol version 4) and single IPv6 (Internet Protocol Version 6) address per NIC (network interface card) is supported.