Incorporate feedback.

Author: TimShererWithAquent

articles/application-gateway/application-gateway-metrics.md

@@ -28,7 +28,7 @@ Application Gateway provides several built‑in timing metrics related to the re
 
 > [!NOTE]
 >
-> If there are more than one listener in the Application Gateway, then always filter by *Listener* dimension while comparing different latency metrics in order to get meaningful inference.
+> If there is more than one listener in the Application Gateway, then always filter by *Listener* dimension while comparing different latency metrics in order to get meaningful inference.
 
 You can use timing metrics to determine whether the observed slowdown is due to the client network, Application Gateway performance, the backend network and backend server TCP stack saturation, backend application performance, or large file size. For more information, see [Timing metrics](monitor-application-gateway-reference.md#timing-metrics).
 

articles/application-gateway/monitor-application-gateway-reference.md

@@ -19,15 +19,15 @@ See [Monitor Azure Application Gateway](monitor-application-gateway.md) for deta
 
 ### Supported metrics for Microsoft.Network/applicationGateways
 
-The following table lists the metrics available for the Microsoft.Network/applicationGateways resource type.
+The following table lists the all metrics available for the Microsoft.Network/applicationGateways resource type. Additional description details for many metrics are included after this table.
 
 [!INCLUDE [horz-monitor-ref-metrics-tableheader](~/reusable-content/ce-skilling/azure/includes/azure-monitor/horizontals/horz-monitor-ref-metrics-tableheader.md)]
 
 [!INCLUDE[Microsoft.Network/applicationgateways](~/reusable-content/ce-skilling/azure/includes/azure-monitor/reference/metrics/microsoft-network-applicationgateways-metrics-include.md)]
 
 ### Timing metrics
 
-Application Gateway provides several built‑in timing metrics related to the request and response, which are all measured in milliseconds. For details, see the [metrics table](#supported-metrics-for-microsoftnetworkapplicationgateways).
+Application Gateway provides many built‑in timing metrics related to the request and response, which are all measured in milliseconds. What follows is an expanded description of the timing metrics already listed in the previous metrics table [metrics table](#supported-metrics-for-microsoftnetworkapplicationgateways).
 
 - **Backend connect time**. This value includes the network latency and the time taken by the backend server's TCP stack to establish new connections. For TLS, it also includes the time spent on handshake.
 - **Backend first byte response time**. This value approximates the sum of *Backend connect time*, time taken by the request to reach the backend from Application Gateway, time taken by backend application to respond, which is the time the server takes to generate content and potentially fetch database queries, and the time taken by first byte of the response to reach the Application Gateway from the backend.
@@ -55,7 +55,7 @@ For Application Gateway, the following metrics are available. For details, see t
 
 ### Backend metrics
 
-The following metrics are available. For details, see the [metrics table](#supported-metrics-for-microsoftnetworkapplicationgateways).
+The following backend metrics are available. What follows is a list and expanded descriptions of the backend metrics already listed in the previous [metrics table](#supported-metrics-for-microsoftnetworkapplicationgateways).
 
 - **Backend response status**. Count of HTTP response status codes returned by the backends, not including any response codes generated by the Application Gateway. The response status code distribution can be categorized to show responses in 2xx, 3xx, 4xx, and 5xx categories.|
 - **Healthy host count**. The number of hosts that are determined healthy by the health probe. You can filter on a per backend pool basis to show the number of healthy hosts in a specific backend pool.