Update troubleshooting steps for HTTP error codes

Author: aartig13

support/developer/webapps/iis/site-behavior-performance/troubleshoot-http-error-code.md

@@ -11,9 +11,9 @@ This article provides troubleshooting steps for resolving [4xx](../health-diagno
 
 ## Identify 4xx errors
 
-[4xx](../health-diagnostic-performance/http-status-code.md#4xx---client-error) HTTP status codes indicate that an error occurred due to a client-side issue. For example, the client browser might have requested a page without providing valid authentication information.
+The 4xx HTTP status codes indicate that an error occurred due to a client-side issue. For example, For example, the client browser might have requested a page that doesn't exist, or the client browser might not have provided valid authentication information.
 
-To identify [4xx](../health-diagnostic-performance/http-status-code.md#4xx---client-error) errors, see the [IIS logs](#examine-the-iis-logs) and the [HTTPERR logs](#examine-the-httperr-logs):
+To identify 4xx errors, examine the [IIS logs](#examine-the-iis-logs) and the [HTTPERR logs](#examine-the-httperr-logs):
 
 - The HTTP status code is recorded in the IIS logs. This file is usually stored in **C:\inetpub\logs\Logfiles** but can be configured via IIS **Logging** in IIS Manager.
 - A 4*xx* error code can be generated by the **HTTP.sys** kernel driver, which means these requests might not reach IIS and thus won't be logged in IIS logs. **HTTP.sys** logs these errors in separate files called [HTTPERR logs](/windows/win32/http/error-logging-in-the-http-server-api). This file is usually stored in **C:\Windows\System32\LogFiles\HTTPERR** but can be configured via the registry `HKEY\LOCAL\MACHINE\System\CurrentControlSet\Services\HTTP\Parameters\ErrorLoggingDir`.
@@ -33,7 +33,7 @@ If you find errors in the HTTPERR logs, note the reason (`s-reason`) and see [Ty
 
 ## Identify 5xx errors
 
-[5xx](../health-diagnostic-performance/http-status-code.md#5xx---server-error) HTTP status codes indicate that the server couldn't complete the request because the server encountered an error when processing the request. Use the following instructions based on your application type.
+The 5xx HTTP status codes indicate that the server couldn't complete the request because the server encountered an error when processing the request. Use the following instructions based on your application type.
 
 ### 500 errors in classic ASP
 
@@ -43,9 +43,9 @@ For more information, capture and examine [Failed Request Trace (FREB) logs](#st
 
 ### 500 errors in general IIS
 
-If a 500 error occurs in general IIS, examine the IIS logs, note `sc-status` and `sc-substatus`, and look for the status code in [HTTP status code overview](../health-diagnostic-performance/http-status-code.md#5xx---server-error) for more information on the failure. Enable detailed error messages if feasible to get more details.
+If a 500 error occurs in general IIS, examine the IIS logs, note `sc-status` and `sc-substatus`, and look for the status code in [HTTP status code overview](../health-diagnostic-performance/http-status-code.md#5xx---server-error) for more information on the failure. 
 
-To enable detailed error messages, follow these steps:
+Enable detailed error messages if feasible to get more details. To enable detailed error messages, follow these steps:
 
 1. Open the **Run** command window.
 1. Launch **inetmgr**.