Merge pull request #294801 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/app-service/configure-common.md

@@ -443,7 +443,7 @@ Here, you can configure some common settings for the app. Some settings require
     > [!NOTE]
     > Most modern browsers support HTTP/2 protocol over TLS only, while non-encrypted traffic continues to use HTTP/1.1. To ensure that client browsers connect to your app with HTTP/2, secure your custom DNS name. For more information, see [Secure a custom DNS name with a TLS/SSL binding in Azure App Service](configure-ssl-bindings.md).
     - **Web sockets**: For [ASP.NET SignalR] or [socket.io](https://socket.io/), for example.
-    - **Always On**: Keeps the app loaded even when there's no traffic. When **Always On** isn't turned on (default), the app is unloaded after 20 minutes without any incoming requests. The unloaded app can cause high latency for new requests because of its warm-up time. When **Always On** is turned on, the front-end load balancer sends a GET request to the application root every five minutes. It's important to ensure this request receives a 200 OK response to ensure any re-imaging operations are performed correctly. The continuous ping prevents the app from being unloaded.
+    - **Always On**: Keeps the app loaded even when there's no traffic. When **Always On** isn't turned on (default), the app is unloaded after 20 minutes without any incoming requests. The unloaded app can cause high latency for new requests because of its warm-up time. When **Always On** is turned on, the front-end load balancer sends a GET request to the application root every five minutes. The continuous ping prevents the app from being unloaded.
 
         Always On is required for continuous WebJobs or for WebJobs that are triggered using a CRON expression.
     - **Session affinity**: In a multi-instance deployment, ensure that the client is routed to the same instance for the life of the session. You can set this option to **Off** for stateless applications.

articles/cloud-shell/get-started/classic.md

@@ -20,7 +20,7 @@ To see all resource providers, and the registration status for your subscription
 
 1. Sign in to the [Azure portal][04].
 1. On the Azure portal menu, search for **Subscriptions**. Select it from the available options.
-1. On the **Subscriptions** page, select the subscription your subscription.
+1. On the **Subscriptions** page, select your subscription.
 1. On your subscription page, expand **Settings** in left menu and select **Resource providers**.
 1. In the **Filter by name...** box, enter `cloudshell` to search for the resource provider.
 1. Select the **Microsoft.CloudShell** resource provider from the provider list.

articles/storage/blobs/secure-file-transfer-protocol-support-authorize-access.md

@@ -196,7 +196,7 @@ If you want to authorize access at the file and directory level, you can enable
    > [!IMPORTANT]
    > The local user must have at least one container permission or ACL permission to the home directory of that container. Otherwise a connection attempt to that container will fail.
 
-2. If you want to authorize access by using the access control lists (ACLs) associated with files and directories in this container, then select the **Allow ACL authorization** checkbox. To learn more about using ACLS to authorize SFTP clients, see [ACLs](secure-file-transfer-protocol-support.md#access-control-lists-acls).
+2. If you want to authorize access by using the access control lists (ACLs) associated with files and directories in this container, then select the **Allow ACL authorization** checkbox. To learn more about using ACLs to authorize SFTP clients, see [ACLs](secure-file-transfer-protocol-support.md#access-control-lists-acls).
 
    You can also add this local user to a group by assigning that user to a group ID. That ID can be any number or number scheme that you want. Grouping users allow you to add and remove users without the need to reapply ACLs to an entire directory structure. Instead, you can just add or remove users from the group.
 

articles/virtual-wan/connect-virtual-network-gateway-vwan.md

@@ -132,7 +132,7 @@ In this section, you create a connection between the VPN Gateway local network g
 1. On the **Add connection** page, configure the following values for your connection:
 
    * **Name:** Name your connection.
-   * **Connection type:** Select **Site-to-site(IPSec)**
+   * **Connection type:** Select **Site-to-site(IPsec)**
    * **Virtual network gateway:** The value is fixed because you're connecting from this gateway.
    * **Local network gateway:** This connection will connect the virtual network gateway to the local network gateway. Choose one of the local network gateways that you created earlier.
    * **Shared Key:** Enter the shared key from earlier.

articles/virtual-wan/monitor-virtual-wan-reference.md

@@ -53,7 +53,7 @@ These tables contain more information about some of the metrics in the preceding
 | **Tunnel Egress TS Mismatch Packet Drop** | Outgoing packet drop count from traffic selector mismatch of a tunnel.|
 | **Tunnel Ingress TS Mismatch Packet Drop** | Incoming packet drop count from traffic selector mismatch of a tunnel.|
 
-#### IPSec metrics
+#### IPsec metrics
 
 | Metric | Description |
 |:-------|:------------|

includes/azure-stack-edge-iot-troubleshoot-compute-error-detail.md

@@ -94,7 +94,7 @@ You can use the create options via the K8s-experimental section. The following s
 
 When configuring the IoT device during setup, you may see the following error: 
 
->*(Http status code: 400) Could not create or update IoT role on \<YourDeviceName>\. An error occurred with the error code {NO_PARAM}. For more information, refer to the error code details (https://aka.ms/dbe-error-codes). If the error persists, contact Microsoft Support*.
+>*(HTTP status code: 400) Could not create or update IoT role on \<YourDeviceName>\. An error occurred with the error code {NO_PARAM}. For more information, refer to the error code details (https://aka.ms/dbe-error-codes). If the error persists, contact Microsoft Support*.
 
 #### Suggested solution