Merge pull request #1858 from adamkimsft/main

Corrected warmup path status code info and added references for customizing warmup path

Author: genlin

support/azure/app-service/faqs-app-service-linux.yml

@@ -250,16 +250,19 @@ sections:
       - question: |
           How does the container warmup request work?
         answer: |
-          When Azure App Services starts your container, the warmup request sends an HTTP request to the [/robots933456.txt](/azure/app-service/configure-custom-container?pivots=container-linux#robots933456-in-logs) endpoint of your application. This is simply a dummy endpoint, but your application needs to reply with any non-5XX status code. If your application logic doesn't reply with any HTTP status code to nonexistent endpoints, the warmup request can't receive a response and it perpetually restarts your container.
-          The warmup request also might fail due to port misconfiguration. 
+          When Azure App Services starts your container, the warmup request sends an HTTP request to the [/robots933456.txt](/azure/app-service/configure-custom-container?pivots=container-linux#robots933456-in-logs) endpoint of your application. This is simply a dummy endpoint, but your application must reply by returning any status code (including 5*xx*). If your application logic doesn't reply by sending an HTTP status code to nonexistent endpoints, the warmup request can't receive a response. Therefore, it perpetually restarts your container. 
           
-          To ensure that the port is correctly configured on Azure App Services, see the question *How do I specify port in my Linux container?*
+          To change from the default behavior, you can customize the warmup endpoint path and status codes that consider the site to be warmed up. To do this, set the [WEBSITE_WARMUP_PATH](/azure/app-service/reference-app-settings?tabs=kudu%2Cdotnet#app-environment) and [WEBSITE_WARMUP_STATUSES](/azure/app-service/reference-app-settings?tabs=kudu%2Cdotnet#app-environment) application settings.
+
+          The warmup request also might fail because of port misconfiguration.
+          
+          To make sure that the port is correctly configured on Azure App Services, see the question, *How do I specify the port in my Linux container?*
       - question: |
           Is it possible to increase the container warmup request timeout?
         answer:
           The warmup request by default fails after waiting 240 seconds for a reply from the container. You may increase the container warmup request timeout by adding the application setting `WEBSITES_CONTAINER_START_TIME_LIMIT` with a value between 240 and 1800 seconds.
       - question: |    
-          How do I specify port in my Linux container?
+          How do I specify the port in my Linux container?
         answer: |
           | Container type | Description | How to set/use port |
           |----------------|-------------|---------------------|