Update load-balancer-standard-diagnostics.md

Author: erichrt

articles/load-balancer/load-balancer-standard-diagnostics.md

@@ -126,11 +126,11 @@ To get SNAT connection statistics:
 
 #### How do I check my SNAT port usage and allocation?
 
-The SNAT Usage metric indicates how many unique flows are established between an internet source and a backend VM or VMSS that is behind a load balancer and does not have a pubic IP address. By comparing this to the SNAT Allocation metric, you can determine if your service is experiencing or at risk of SNAT exhaustion and resulting outbound flow failure. 
+The SNAT Usage metric indicates how many unique flows are established between an internet source and a backend VM or VMSS that is behind a load balancer and does not have a pubic IP address. By comparing this with the SNAT Allocation metric, you can determine if your service is experiencing or at risk of SNAT exhaustion and resulting outbound flow failure. 
 
 If your metrics indicate risk of [outbound flow](https://aka.ms/lboutbound) failure, reference the article and take steps to mitigate this to ensure service health.
 
-To get SNAT usage and allocation:
+To view SNAT port usage and allocation:
 1. Set the time aggregation of the graph to 1 minute to ensure desired data is displayed.
 1. Select **SNAT Usage** and/or **SNAT Allocation** as the metric type and **Average** as the aggregation
     * By default this is the average number of SNAT ports allocated to or used by each backend VMs or VMSSes, corresponding to all frontend public IPs mapped to the Load Balancer, aggregated over TCP and UDP.