Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr

Author: maud-lv

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/azure-functions/functions-create-maven-eclipse.md

@@ -19,7 +19,7 @@ This article shows you how to create a [serverless](https://azure.microsoft.com/
 
 To develop a functions app with Java and Eclipse, you must have the following installed:
 
--  [Java Developer Kit](/java/openjdk/download#openjdk-17), version 8, 11, 17 or 21. (Java 21 is currently supported in preview only on Linux)
+-  [Java Developer Kit](/java/openjdk/download#openjdk-17), version 8, 11, 17 or 21. (Java 21 is currently supported only on Linux)
 -  [Apache Maven](https://maven.apache.org), version 3.0 or above.
 -  [Eclipse](https://www.eclipse.org/downloads/packages/), with Java and Maven support.
 -  [Azure CLI](/cli/azure)

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/frontdoor/health-probes.md

@@ -65,29 +65,6 @@ Azure Front Door uses a three-step process across all algorithms to determine he
 > [!NOTE]
 > If a single endpoint is a member of multiple origin groups, Front Door optimizes the number of health probes sent to the origin to reduce the load on the origin. Health probe requests are sent based on the lowest configured sample interval. The responses from same health probes determine the health of the endpoint in all origin groups.
 
-## Adjusting probe settings for long-starting containers
-
-When you deal with long-starting containers, adjusting the probe settings can prevent premature failure. Increasing the `ProbeTimeout` and `Interval` values gives your containers more time to start before Front Door marks them as unhealthy.
-
-### Values for long-starting containers
-- **ProbeTimeout**: Increase the timeout period to 10–30 seconds.
-- **Interval**: Set a longer interval (for example, 30–60 seconds) between probes.
-- **UnhealthyThreshold**: Increase the number of consecutive failed probes before the container is considered unhealthy (for example, 3-5 retries).
-
-> [!NOTE]
-> The values provided for `ProbeTimeout`, `Interval`, and `UnhealthyThreshold` are sample ranges for example purposes. You can adjust these values based on your specific container's startup behavior and requirements.
-
-> [!NOTE] 
-> These changes might cause a delay in detecting real failures, so balance these values carefully according to your container's startup behavior.
-
-## Probe interaction during container lifecycle phases
-
-1. **Container Start Phase**: During this phase, the container might not be fully ready to serve traffic. Health probes help detect when a container isn't responding by checking for specific HTTP status codes (for example, `200 OK`). If the probe frequency is too high or the timeout is too short, the container is marked as unhealthy before initialization. Increase probe timeouts or intervals during this phase.
-
-1. **Running Phase**: Once the container is running, probes continue checking for health responses. If health checks consistently return `200 OK`, Front Door keeps the origin in rotation for traffic. If probes consistently fail (for example, due to a container crashing), Front Door marks the origin as unhealthy.
-
-1. **Failure Phase**: If health probes fail for the configured threshold (for example, `UnhealthyThreshold`), the origin is considered unhealthy, and traffic is routed to other healthy origins.
-
 ## Complete health probe failure
 
 If health probes fail for every origin in an origin group, then Front Door considers all origins unhealthy and routes traffic in a round robin distribution across all of them.