Merge pull request #271962 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/aks/learn/quick-kubernetes-deploy-portal.md

@@ -400,7 +400,7 @@ To deploy the application, you use a manifest file to create all the objects req
 
 When the application runs, a Kubernetes service exposes the application front end to the internet. This process can take a few minutes to complete.
 
-1. Check the status of the deployed pods using the [kubectl get pods][kubectl-get] command. Make all pods are `Running` before proceeding.
+1. Check the status of the deployed pods using the [kubectl get pods][kubectl-get] command. Make sure all pods are `Running` before proceeding.
 
     ```console
     kubectl get pods

articles/api-management/virtual-network-reference.md

@@ -52,6 +52,7 @@ When an API Management service instance is hosted in a VNet, the ports in the fo
 | * / 4290              | Inbound & Outbound | UDP                | VirtualNetwork / VirtualNetwork     | Sync Counters for [Rate Limit](rate-limit-policy.md) policies between machines (optional)        | External & Internal  |
 | * / 6390                       | Inbound            | TCP                | AzureLoadBalancer / VirtualNetwork | **Azure Infrastructure Load Balancer**                          | External & Internal  |
 | * / 443                       | Inbound            | TCP                | AzureTrafficManager / VirtualNetwork | **Azure Traffic Manager**  routing for multi-region deployment                        | External |
+| * / 6391                       | Inbound            | TCP                | AzureLoadBalancer / VirtualNetwork | Monitoring of individual machine health (Optional)                          | External & Internal  |
 
 ### [stv1](#tab/stv1)
 

articles/app-service/deploy-best-practices.md

@@ -80,7 +80,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
     # checkout the repo
-    - name: 'Checkout Github Action'
+    - name: 'Checkout GitHub Action'
       uses: actions/checkout@main
 
     - uses: azure/docker-login@v1

articles/app-service/tutorial-dotnetcore-sqldb-app.md

@@ -60,7 +60,7 @@ Sign in to the [Azure portal](https://portal.azure.com/) and follow these steps
         1. *Runtime stack* → **.NET 7 (STS)**.
         1. *Add Azure Cache for Redis?* → **Yes**.
         1. *Hosting plan* → **Basic**. When you're ready, you can [scale up](manage-scale-up.md) to a production pricing tier later.
-        1. **SQLAzure** is selected by default as the database engine. Azure SQL Database is a fully managed platform as a service (PaaS) database engine that's always running on the latest stable version of the SQL Server.
+        1. Select **SQLAzure** as the database engine. Azure SQL Database is a fully managed platform as a service (PaaS) database engine that's always running on the latest stable version of the SQL Server.
         1. Select **Review + create**.
         1. After validation completes, select **Create**.
     :::column-end:::

articles/azure-web-pubsub/quickstarts-push-messages-from-server.md

@@ -85,7 +85,7 @@ client.on("server-message", (e) => {
 
 // Before a client can receive a message, 
 // you must invoke start() on the client object.
-await client.start();
+client.start();
 ```
 
 #### Run the program

articles/networking/azure-network-latency.md

@@ -22,7 +22,7 @@ The latency measurements are collected from Azure cloud regions worldwide, and c
 
 The monthly Percentile P50 round trip times between Azure regions for a 30-day window are shown in the following tabs. The latency is measured in milliseconds (ms).
 
-The current dataset was taken on *April 9th, 20247*, and it covers the 30-day period ending on *April 9th, 2024*.
+The current dataset was taken on *April 9th, 2024*, and it covers the 30-day period ending on *April 9th, 2024*.
 
 For readability, each table is split into tabs for groups of Azure regions. The tabs are organized by regions, and then by source region in the first column of each table. For example, the *East US* tab also shows the latency from all source regions to the two *East US* regions: *East US* and *East US 2*.