Learn Editor: Update http-response-codes.md

Author: Yunus-MSFT

articles/application-gateway/http-response-codes.md

@@ -60,10 +60,10 @@ For more information about troubleshooting mutual authentication, see [Error cod
 An HTTP 401 unauthorized response can be returned when backend pool is configured with [NTLM](/windows/win32/secauthn/microsoft-ntlm?redirectedfrom=MSDN) authentication.
 There are several ways to resolve this:
 - Allow anonymous access on backend pool.
-- or configure the probe to send the request to another “fake” site that doesn’t require NTLM.
-   - Not recommend, as this will not tell us if the actual site behind the Application Gateway is active or not.
-- or configure Application gateway to allow 401 responses as valid for the probes: [Probe matching conditions](/azure/application-gateway/application-gateway-probe-overview).
-#### 403 – Forbidden
+- Configure the probe to send the request to another “fake” site that doesn’t require NTLM.
+- Not recommended, as this will not tell us if the actual site behind the application aateway is active or not.
+- Configure application gateway to allow 401 responses as valid for the probes: [Probe matching conditions](/azure/application-gateway/application-gateway-probe-overview).
+   #### 403 – Forbidden
 
 HTTP 403 Forbidden is presented when customers are utilizing WAF skus and have WAF configured in Prevention mode.  If enabled WAF rulesets or custom deny WAF rules match the characteristics of an inbound request, the client will be presented a 403 forbidden response.
 
@@ -112,3 +112,4 @@ HTTP 504 errors are presented if a request is sent to application gateways using
 If the information in this article doesn't help to resolve the issue, [submit a support ticket](https://azure.microsoft.com/support/options/).
 
 
+