minor updates

Author: sevend2

.openpublishing.redirection.developer.json

@@ -5824,6 +5824,11 @@
       "source_path": "support/developer/webapps/iis/www-authentication-authorization/401-error-preauthentication-header.md",
       "redirect_url": "/troubleshoot/developer/webapps/iis/site-behavior-performance/401-error-preauthentication-header",
       "redirect_document_id": true
+    },
+    {
+      "source_path": "support/developer/webapps/iis/www-authentication-authorization/information-associated-iis-site-is-not-deleted.md",
+      "redirect_url": "/troubleshoot/developer/webapps/iis/www-administration-management/information-associated-iis-site-is-not-deleted",
+      "redirect_document_id": true
     }
   ]
 }

support/developer/webapps/iis/site-behavior-performance/troubleshoot-502-2-bad-gateway-error-in-cgi-apps.md

@@ -78,7 +78,7 @@ HTTP: Data: Number of data bytes remaining = 232 (0x00E8)
 001A0: 3E 3C 2F 68 74 6D 6C 3E ></html>
 ```
 
-Capture [FREB](troubleshoot-php-with-failed-request-tracing.md) log for the HTTP error message and locate which module is throwing this error message.
+Capture [FREB](../health-diagnostic-performance/troubleshoot-php-with-failed-request-tracing.md) log for the HTTP error message and locate which module is throwing this error message.
 
 Troubleshoot the CGI process executable file to determine why the CGI process terminates unexpectedly. You might have to generate a memory dump file of the CGI process when the access violation occurs.
 

support/developer/webapps/iis/site-behavior-performance/troubleshoot-http-400-errors-in-iis.md

@@ -38,7 +38,7 @@ The next data item you use is the **C:\Windows\System32\LogFiles\HTTPERR\httperr
 It's technically possible, although not very likely, that a client might receive an HTTP 400 response, which doesn't have an associated log entry in the **httperr.log** file. It could happen if an ISAPI filter or extension, or an HTTP module in IIS, sets the 400 status, in which case you could look at the IIS log for more information. It could also happen if an entity between the client and the server, such as a proxy server or other network device, intercepts a response from IIS and overrides it with its own 400 status and/or "Bad Request" error.
 
 > [!NOTE]
-> This article mainly discusses the common HTTP 400 errors before reaching your website. In some scenarios, your website might also return HTTP 400 errors to clients due to custom code logic or runtime (such as ASP.NET) configuration. If you still can't resolve the HTTP 400 errors after performing the steps in the following sections, try to troubleshoot using the [Failed Requests Tracing feature](./troubleshoot-failed-requests-using-tracing-in-iis-85.md) in IIS. If you find the HTTP 400 errors are actually set by your website's corresponding runtime handler, such as ASP.NET, you might need to inspect the details of the requests and responses, along with your website's related code logic and runtime configuration, to understand the cause of the HTTP 400 errors.
+> This article mainly discusses the common HTTP 400 errors before reaching your website. In some scenarios, your website might also return HTTP 400 errors to clients due to custom code logic or runtime (such as ASP.NET) configuration. If you still can't resolve the HTTP 400 errors after performing the steps in the following sections, try to troubleshoot using the [Failed Requests Tracing feature](../health-diagnostic-performance/troubleshoot-failed-requests-using-tracing-in-iis-85.md) in IIS. If you find the HTTP 400 errors are actually set by your website's corresponding runtime handler, such as ASP.NET, you might need to inspect the details of the requests and responses, along with your website's related code logic and runtime configuration, to understand the cause of the HTTP 400 errors.
 
 ## Sample scenario