edit pass: three-load-balancer-articles

Author: ShawnJackson

articles/load-balancer/load-balancer-overview.md

@@ -16,9 +16,9 @@ ms.custom: template-overview, engagement-fy23
 
 *Load balancing* refers to efficiently distributing incoming network traffic across a group of backend servers or resources.
 
-Azure Load Balancer operates at layer 4 of the Open Systems Interconnection (OSI) model. It's the single point of contact for clients. The service distributes inbound flows that arrive at the load balancer's frontend to backend pool instances. These flows are distributed according to configured load-balancing rules and health probes. The backend pool instances can be Azure virtual machines (VMs) or instances in a virtual machine scale set.
+Azure Load Balancer operates at layer 4 of the Open Systems Interconnection (OSI) model. It's the single point of contact for clients. The service distributes inbound flows that arrive at the load balancer's frontend to backend pool instances. These flows are distributed according to configured load-balancing rules and health probes. The backend pool instances can be Azure virtual machines (VMs) or virtual machine scale sets.
 
-A [public load balancer](./components.md#frontend-ip-configurations) can provide outbound connections for VMs inside your virtual network. The service accomplishes these connections by translating the VMs' private IP addresses to public IP addresses. It uses public load balancers to load balance internet traffic to your VMs.
+A [public load balancer](./components.md#frontend-ip-configurations) can provide outbound connections for VMs inside your virtual network. Azure Load Balancer accomplishes these connections by translating the VMs' private IP addresses to public IP addresses. The service uses public load balancers to load balance internet traffic to your VMs.
 
 Azure Load Balancer uses an [internal (or private) load balancer](./components.md#frontend-ip-configurations) in scenarios where private IPs are needed at the frontend only. The service uses internal load balancers to load balance traffic inside a virtual network. Users can access a load balancer frontend from an on-premises network in a hybrid scenario.
 
@@ -48,7 +48,9 @@ Key scenarios that you can accomplish by using Azure Standard Load Balancer incl
 
 - Enable support for [load balancing](./virtual-network-ipv4-ipv6-dual-stack-standard-load-balancer-powershell.md) of [IPv6](../virtual-network/ip-services/ipv6-overview.md).
 
-- Use multidimensional metrics through [Azure Monitor](/azure/azure-monitor/overview). You can filter, group, and break out these metrics for a particular dimension. They provide current and historic insights into performance and health of your service. [Insights for Azure Load Balancer](./load-balancer-insights.md) offer a preconfigured dashboard with useful visualizations for these metrics. Resource Health is also supported. For more details, review [Standard load balancer diagnostics](load-balancer-standard-diagnostics.md).
+- Use multidimensional metrics through [Azure Monitor](/azure/azure-monitor/overview). You can filter, group, and break out these metrics for a particular dimension. They provide current and historic insights into performance and health of your service.
+
+  [Insights for Azure Load Balancer](./load-balancer-insights.md) offer a preconfigured dashboard with useful visualizations for these metrics. Resource Health is also supported. For more details, review [Standard load balancer diagnostics](load-balancer-standard-diagnostics.md).
 
 - Load balance services on [multiple ports, multiple IP addresses, or both](./load-balancer-multivip-overview.md).
 
@@ -72,7 +74,7 @@ Key scenarios that you can accomplish by using Azure Standard Load Balancer incl
 
 ## Pricing and SLA
 
-For Standard Load Balancer pricing information, see [Load Balancer pricing](https://azure.microsoft.com/pricing/details/load-balancer/). For service-level agreements, see the [Microsoft licensing information for online services](https://aka.ms/lbsla).
+For Standard Load Balancer pricing information, see [Load Balancer pricing](https://azure.microsoft.com/pricing/details/load-balancer/). For service-level agreements (SLAs), see the [Microsoft licensing information for online services](https://aka.ms/lbsla).
 
 Basic Load Balancer is offered at no charge and has no SLA.
 
@@ -82,5 +84,5 @@ Subscribe to the RSS feed and view the latest Azure Load Balancer updates on the
 
 ## Related content
 
-- [Create a public standard load balancer](quickstart-load-balancer-standard-public-portal.md)
+- [Create a public load balancer](quickstart-load-balancer-standard-public-portal.md)
 - [Azure Load Balancer components](./components.md)

articles/load-balancer/load-balancer-troubleshoot.md

@@ -26,15 +26,15 @@ When the external clients to the backend VMs go through the load balancer, the I
 
 ### Validation and resolution
 
-Standard internal load balancers (ILBs) have default security features. Basic ILBs allow connecting to the internet via a hidden public IP address called the *default outbound access IP*. Connecting via default outbound access IP isn't recommended for production workloads, because the IP address isn't static or locked down via network security groups that you own.
+Standard internal load balancers (ILBs) have default security features. Basic ILBs allow connecting to the internet via a hidden public IP address called the *default outbound access IP*. We don't recommend connecting via default outbound access IP for production workloads, because the IP address isn't static or locked down via network security groups that you own.
 
 If you recently moved from a Basic ILB to a Standard ILB, you should create a public IP explicitly by using an [outbound only](egress-only.md) configuration. This configuration locks down the IP via network security groups. You can also use [Azure NAT Gateway](../virtual-network/nat-gateway/nat-overview.md) on your subnet. We recommend NAT Gateway as the solution for outbound access.
 
 ## Problem: No inbound connectivity to Standard external load balancers
 
 ### Cause
 
-Standard load balancers and standard public IP addresses are closed to inbound connections unless network security groups open them. You use NSGs to explicitly permit allowed traffic. If you don't have an NSG on a subnet or network interface card (NIC) of your virtual machine resource, traffic isn't allowed to reach the resource.
+Standard load balancers and standard public IP addresses are closed to inbound connections unless network security groups open them. You use NSGs to explicitly permit allowed traffic. If you don't have an NSG on a subnet or network interface card (NIC) of your VM resource, traffic isn't allowed to reach the resource.
 
 ### Resolution
 
@@ -64,10 +64,10 @@ To verify, you can conduct a network trace. The properties of each storage accou
 
 ### Resolution
 
-- Go to [Azure Resource Explorer](https://resources.azure.com/) and identify the resource that's in a failed state.
-- Update the toggle in the upper-right corner to **Read/Write**.
-- Select **Edit** for the resource in failed state.
-- Select **PUT** followed by **GET** to ensure that the provisioning state changed to **Succeeded**.
+1. Go to [Azure Resource Explorer](https://resources.azure.com/) and identify the resource that's in a failed state.
+1. Update the toggle in the upper-right corner to **Read/Write**.
+1. Select **Edit** for the resource in failed state.
+1. Select **PUT** followed by **GET** to ensure that the provisioning state changed to **Succeeded**.
 
 You can then proceed with other actions, because the resource is out of a failed state.
 

articles/load-balancer/troubleshoot-rhc.md

@@ -59,7 +59,7 @@ You can take the same steps to investigate the failure that you see in any Healt
 
 1. Go to the tab for frontend and backend availability, and review a 30-minute window of the time period when the degraded or unavailable state occurred. If the Data Path Availability value is 0%, you know that something is preventing traffic for all of your load-balancing rules. You can also see how long this problem has lasted.
 
-1. Check your Health Probe Status metric to determine whether your data path is unavailable because you have no healthy backend instances to serve traffic. If you have at least one healthy backend instance for all of your load-balancing and inbound rules, you know it isn't your configuration that's causing your data paths to be unavailable. This scenario indicates an Azure platform problem. Although platform problems are rare, they trigger an automated alert to our team for rapid resolution.
+1. Check your Health Probe Status metric to determine whether your data path is unavailable because you have no healthy backend instances to serve traffic. If you have at least one healthy backend instance for all of your load-balancing and inbound rules, you know that your configuration isn't what's causing your data paths to be unavailable. This scenario indicates an Azure platform problem. Although platform problems are rare, they trigger an automated alert to our team for rapid resolution.
 
 ## Diagnose health probe failures
 
@@ -71,7 +71,7 @@ If your Health Probe Status metric indicates that your backend instances are unh
 * If you're using an HTTP or HTTPS probe, check if the application is healthy and responsive.
 
   Validate that your application is functional by directly accessing it through the private IP address or instance-level public IP address that's associated with your backend instance.
-* Review the network security groups applied to your backend resources. Ensure that no rules have a higher priority than `AllowAzureLoadBalancerInBound` that block the health probe.
+* Review the network security groups (NSGs) applied to your backend resources. Ensure that no rules have a higher priority than `AllowAzureLoadBalancerInBound` that block the health probe.
 
   You can do this task by visiting the network settings of your backend VMs or virtual machine scale sets. If you find that this NSG problem is the case, move the existing `Allow` rule or create a new high-priority rule to allow Azure Load Balancer traffic.
 * Check your OS. Ensure that your VMs are listening on the probe port. Also review the OS firewall rules for the VMs to ensure that they aren't blocking the probe traffic originating from IP address `168.63.129.16`.