incorporating feedback

Author: Larry Franks

articles/machine-learning/how-to-monitor-online-endpoints.md

@@ -104,25 +104,25 @@ There are three logs that can be enabled for online endpoints:
 
 * **AMLOnlineEndpointTrafficLog**: You could choose to enable traffic logs if you want to check the information of your request. Below are some cases: 
 
-    * If the response isn't 200, you could check the value of the column “ResponseCodeReason” to see what might happen. And check the reason following the below link https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_conn_man/response_code_details 
+    * If the response isn't 200, check the value of the column “ResponseCodeReason” to see what happened. Also check the reason in the "HTTPS status codes" section of the [Troubleshoot online endpoints](how-to-troubleshoot-online-endpoints.md#http-status-codes) article.
 
     * You could check the response code and response reason of your model from the column “ModelStatusCode” and “ModelStatusReason”. 
 
     * You want to check the duration of the request like total duration, the request/response duration, and the delay caused by the network throttling. You could check it from the logs to see the breakdown latency. 
 
     * If you want to check how many requests or failed requests recently. You could also enable the logs. 
 
-* **AMLOnlineEndpointConsoleLog**: Contains logs that the user containers output to the console. Below are some cases: 
+* **AMLOnlineEndpointConsoleLog**: Contains logs that the containers output to the console. Below are some cases: 
 
-    * If the user container fails to start, the console log may be useful for debugging. 
+    * If the container fails to start, the console log may be useful for debugging. 
 
-    * Monitor user container behavior, and make sure that all requests are correctly handled. 
+    * Monitor container behavior and make sure that all requests are correctly handled. 
 
     * Write request IDs in the console log. Joining the request ID, the AMLOnlineEndpointConsoleLog, and AMLOnlineEndpointTrafficLog in the Log Analytics workspace, you can trace a request from the network entry point of an online endpoint to the container.  
 
-    * Users may also use this log for performance analysis in determining the time required by the model to process each request. 
+    * You may also use this log for performance analysis in determining the time required by the model to process each request. 
 
-* **AMLOnlineEndpointEventLog**: Contains event information regarding the user container’s life cycle. Currently, we provide information on the following types of events: 
+* **AMLOnlineEndpointEventLog**: Contains event information regarding the container’s life cycle. Currently, we provide information on the following types of events: 
 
     | Name | Message |
     | ----- | ----- | 
@@ -185,17 +185,17 @@ The following tables provide details on the data stored in each log:
 | EndpointName | The name of the online endpoint. 
 | DeploymentName | The name of the online deployment. 
 | Protocol | The protocol of the request. 
-| ResponseCode | The final response code returned to the user. 
-| ResponseCodeReason | The final response code reason returned to the user. 
+| ResponseCode | The final response code returned to the client. 
+| ResponseCodeReason | The final response code reason returned to the client. 
 | ModelStatusCode | The response status code from model. 
 | ModelStatusReason | The response status reason from model. 
-| RequestPayloadSize | The total bytes received from the user client. 
-| ResponsePayloadSize | The total bytes sent back to the user client. 
+| RequestPayloadSize | The total bytes received from the client. 
+| ResponsePayloadSize | The total bytes sent back to the client. 
 | UserAgent | The user-agent header of the request. 
 | XRequestId | The request ID generated by Azure Machine Learning for internal tracing. 
-| XMSClientRequestId | The tracking ID generated by user client. 
-| TotalDurationMs | Duration in milliseconds from the request start time to the last response byte sent back to the user client. If the user client disconnected, it measures from the start time to client disconnect time. 
-| RequestDurationMs | Duration in milliseconds from the request start time to the last byte of the request received from the user client. 
+| XMSClientRequestId | The tracking ID generated by the client. 
+| TotalDurationMs | Duration in milliseconds from the request start time to the last response byte sent back to the client. If the client disconnected, it measures from the start time to client disconnect time. 
+| RequestDurationMs | Duration in milliseconds from the request start time to the last byte of the request received from the client. 
 | ResponseDurationMs | Duration in milliseconds from the request start time to the first response byte read from the model. 
 | RequestThrottlingDelayMs | Delay in milliseconds in request data transfer due to network throttling. 
 | ResponseThrottlingDelayMs | Delay in milliseconds in response data transfer due to network throttling.