Minor change from server to appgw

Author: jaesoni

articles/application-gateway/application-gateway-diagnostics.md

@@ -219,7 +219,7 @@ The access log is generated only if you've enabled it on each Application Gatewa
 If the application gateway can't complete the request, it stores one of the following reason codes in the error_info field of the access log. 
 
 
-|4XX Errors  |The 4xx error codes indicate that there was an issue with the client's request, and the server can't fulfill it |
+|4XX Errors  | (The 4xx error codes indicate that there was an issue with the client's request, and the Application Gateway can't fulfill it.) |
 |---------|---------|
 |    ERRORINFO_INVALID_METHOD|	The client has sent a request  which is non-RFC compliant.  Possible reasons: client using HTTP method not supported by server, misspelled method, incompatible HTTP protocol version etc.|
   |  ERRORINFO_INVALID_REQUEST	| The server can't fulfill the request because of incorrect syntax.|
@@ -235,7 +235,7 @@ If the application gateway can't complete the request, it stores one of the foll
    | ERRORINFO_HTTPS_NO_CERT | 	Indicates client is not sending a valid and properly configured TLS certificate during Mutual TLS authentication.    |
 
 
-|5XX Errors  |Description  |
+|5XX Errors  | Description  |
 |---------|---------|
   |  ERRORINFO_UPSTREAM_NO_LIVE	| The application gateway is unable to find any active or reachable backend servers to handle incoming requests       |
   |  ERRORINFO_UPSTREAM_CLOSED_CONNECTION	| The backend server closed the connection unexpectedly or before the request was fully processed. This could happen due to backend server reaching its limits, crashing etc.|