Merge pull request #242777 from mbender-ms/lb-crlb-update

Load Balancer - typo

Author: prmerger-automator[bot]

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

@@ -7,7 +7,7 @@ author: mbender-ms
 ms.service: load-balancer
 ms.topic: conceptual
 ms.workload: infrastructure-services
-ms.date: 10/31/2022
+ms.date: 06/23/2023
 ms.author: mbender
 ms.custom: template-concept, references_regions
 ---
@@ -42,15 +42,15 @@ Configure regional redundancy by adding a global frontend public IP address to y
 
 If one region fails, the traffic is routed to the next closest healthy regional load balancer.  
 
-The health probe of the cross-region load balancer gathers information about availability of each regional load balancer every 20 seconds. If one regional load balancer drops its availability to 0, cross-region load balancer will detect the failure. The regional load balancer is then taken out of rotation. 
+The health probe of the cross-region load balancer gathers information about availability of each regional load balancer every 20 seconds. If one regional load balancer drops its availability to 0, cross-region load balancer detects the failure. The regional load balancer is then taken out of rotation. 
 
 :::image type="content" source="./media/cross-region-overview/global-region-view.png" alt-text="Diagram of global region traffic view." border="true":::
 
 ### Ultra-low latency
 
 The geo-proximity load-balancing algorithm is based on the geographic location of your users and your regional deployments. 
 
-Traffic started from a client will hit the closest participating region and travel through the Microsoft global network backbone to arrive at the closest regional deployment. 
+Traffic started from a client hits the closest participating region and travel through the Microsoft global network backbone to arrive at the closest regional deployment. 
 
 For example, you have a cross-region load balancer with standard load balancers in Azure regions:
 
@@ -65,7 +65,7 @@ The configured load distribution mode of the regional load balancers is used for
 
 For more information, see [Configure the distribution mode for Azure Load Balancer](./load-balancer-distribution-mode.md).
 
-Egress traffic will follow the routing preference set on the regional load balancers.
+Egress traffic follows the routing preference set on the regional load balancers.
 
 ### Ability to scale up/down behind a single endpoint
 
@@ -74,25 +74,29 @@ When you expose the global endpoint of a cross-region load balancer to customers
 <!---To learn about how to add or remove a regional deployment from the backend, read more [here](TODO: Insert CLI doc here).--->
 
 ### Static anycast global IP address
-Cross-region load balancer comes with a static public IP, which ensures the IP address remains the same. To learn more about static IP, read more [here](../virtual-network/ip-services/public-ip-addresses.md#ip-address-assignment)
 
+Cross-region load balancer comes with a static public IP, which ensures the IP address remains the same. To learn more about static IP, read more [here](../virtual-network/ip-services/public-ip-addresses.md#ip-address-assignment)
 
 ### Client IP Preservation
+
 Cross-region load balancer is a Layer-4 pass-through network load balancer. This pass-through preserves the original IP of the packet.  The original IP is available to the code running on the virtual machine. This preservation allows you to apply logic that is specific to an IP address.
 
 ### Floating IP
+
 Floating IP can be configured at both the global IP level and regional IP level. For more information, visit [Multiple frontends for Azure Load Balancer](./load-balancer-multivip-overview.md)
 
 ### Health Probes
-Azure cross-region Load Balancer utilizes the health of the backend regional load balancers when deciding where to distribute traffic to. These health checks by the cross-region load balancer are done automatically every 20 seconds, given that a user has set up health probes on their regional load balancer.  
+
+Azure cross-region Load Balancer utilizes the health of the backend regional load balancers when deciding where to distribute traffic to. Health checks by cross-region load balancer are done automatically every 20 seconds, given that a user has set up health probes on their regional load balancer.  
 
 ## Build cross region solution on existing Azure Load Balancer
+
 The backend pool of cross-region load balancer contains one or more regional load balancers. 
 
 Add your existing load balancer deployments to a cross-region load balancer for a highly available, cross-region deployment.
 
 **Home region** is where the cross-region load balancer or Public IP Address of Global tier is deployed. 
-This region doesn't affect how the traffic will be routed. If a home region goes down, traffic flow is unaffected.
+This region doesn't affect how the traffic is routed. If a home region goes down, traffic flow is unaffected.
 
 ### Home regions
 * East US 2
@@ -106,11 +110,11 @@ This region doesn't affect how the traffic will be routed. If a home region goes
 * West Europe
 
 > [!NOTE]
-> You can only deploy your cross-region load balancer or Public IP in Global tier in one of the regions above.
+> You can only deploy your cross-region load balancer or Public IP in Global tier in one of the listed Home regions.
 
 A **participating region** is where the Global public IP of the load balancer is being advertised.
 
-Traffic started by the user will travel to the closest participating region through the Microsoft core network. 
+Traffic started by the user travels to the closest participating region through the Microsoft core network. 
 
 Cross-region load balancer routes the traffic to the appropriate regional load balancer.
 
@@ -153,15 +157,12 @@ Cross-region load balancer routes the traffic to the appropriate regional load b
 
 * UDP traffic isn't supported on Cross-region Load Balancer.
 
-* Outbound rules aren't support on Cross-region Load Balancer. For outbound connections please utilize [outbound rules](./outbound-rules.md) on the regional load balancer or [NAT gateway](https://learn.microsoft.com/azure/nat-gateway/nat-overview).
-
-
+* Outbound rules aren't supported on Cross-region Load Balancer. For outbound connections, utilize [outbound rules](./outbound-rules.md) on the regional load balancer or [NAT gateway](../nat-gateway/nat-overview.md).
 
 ## Pricing and SLA
-Cross-region load balancer, shares the [SLA](https://azure.microsoft.com/support/legal/sla/load-balancer/v1_0/ ) of standard load balancer.
+Cross-region load balancer shares the [SLA](https://azure.microsoft.com/support/legal/sla/load-balancer/v1_0/ ) of standard load balancer.
 
- 
-## Next steps
+ ## Next steps
 
 - See [Tutorial: Create a cross-region load balancer using the Azure portal](tutorial-cross-region-portal.md) to create a cross-region load balancer.
 - Learn more about [cross-region load balancer](https://www.youtube.com/watch?v=3awUwUIv950).