Merge pull request #217514 from KapilAnanth-MSFT/patch-10

(AzureCXP) fixed typo error

Author: prmerger-automator[bot]

articles/application-gateway/application-gateway-backend-health-troubleshooting.md

@@ -195,7 +195,7 @@ az network application-gateway start -n <appgw_name> -g <rg_name>
 
 **Message:** Status code of the backend's HTTP response did not match the probe setting. Expected:{HTTPStatusCode0} Received:{HTTPStatusCode1}.
 
-**Cause:** After the TCP connection has been established and a TLS handshake is done (if TLS is enabled), Application Gateway will send the probe as an HTTP GET request to the backend server. As described earlier, the default probe will be to `<protocol>://127.0.0.1:<port>/`, and it considers response status codes in the rage 200 through 399 as Healthy. If the server returns any other status code, it will be marked as Unhealthy with this message.
+**Cause:** After the TCP connection has been established and a TLS handshake is done (if TLS is enabled), Application Gateway will send the probe as an HTTP GET request to the backend server. As described earlier, the default probe will be to `<protocol>://127.0.0.1:<port>/`, and it considers response status codes in the range 200 through 399 as Healthy. If the server returns any other status code, it will be marked as Unhealthy with this message.
 
 **Solution:** Depending on the backend server's response code, you can take the following steps. A few of the common status codes are listed here:
 
@@ -411,4 +411,4 @@ This behavior can occur for one or more of the following reasons:
 
 ## Next steps
 
-Learn more about [Application Gateway diagnostics and logging](./application-gateway-diagnostics.md).
+Learn more about [Application Gateway diagnostics and logging](./application-gateway-diagnostics.md).