lb updates

Author: mbender-ms

articles/virtual-network/ip-services/configure-public-ip-load-balancer.md

@@ -7,8 +7,7 @@ ms.author: mbender
 ms.service: azure-virtual-network
 ms.subservice: ip-services
 ms.topic: how-to 
-ms.date: 08/24/2023
-ms.custom: template-how-to, engagement-fy23
+ms.date: 01/07/2025
 ---
 
 # Manage a public IP address with a load balancer
@@ -27,7 +26,7 @@ In this article, you learn how to:
 > [!div class="checklist"]
 > * Create a load balancer with an existing public IP address in your subscription. 
 > * Change the current public IP associated to a load balancer. 
-> * Change the frontend configuration of a load balancer from a public IP address to a public IP prefix.  
+> * Change the frontend configuration of a load balancer from a public IP address to a public IP prefix. 
 
 Finally, the article reviews unique aspects of using public IPs and public IP prefixes with a load balancer. 
 
@@ -54,13 +53,13 @@ In this section, you create a standard SKU load balancer. You select the IP addr
 
 4. Select **+ Create**.
 
-5. In the **Basics** tab of **Create Load balancer**, enter or select the following information:
+5. In the **Basics** tab of **Create Load balancer**, enter, or select the following information:
 
     | Setting | Value |
     | ------- | ----- |
     | **Project details** |   |
     | Subscription | Select your subscription. |
-    | Resource group | Select **Create new**. </br> Enter **myResourceGroupIP**. </br> Select **OK**. |
+    | Resource group | Select **Create new**.</br> Enter **myResourceGroupIP**.</br> Select **OK**. |
     | **Instance details** |   |
     | Name | Enter **myLoadBalancer**. |
     | Region | Select **(US) West US 2**. |
@@ -114,7 +113,7 @@ To change the IP, you associate a new public IP address previously created with
     :::image type="content" source="./media/configure-public-ip-load-balancer/verify-new-ip.png" alt-text="Screenshot of the load balancer Frontend I P configuration page showing the new public I P address.":::
 
 > [!NOTE]
-> This technique can be utilized when transitioning from a non-zonal frontend to a zone-redundant frontend in regions that support availability zones.  See [Load Balancer and Availability Zones](../../load-balancer/load-balancer-standard-availability-zones.md)
+> This technique can be utilized when transitioning from a non-zonal frontend to a zone-redundant frontend in regions that support availability zones. See [Load Balancer and Availability Zones](../../load-balancer/load-balancer-standard-availability-zones.md)
 
 ## Add public IP prefix
 
@@ -156,9 +155,9 @@ In this section, you change the frontend configuration used for outbound connect
 
 ## Caveats
 
-* Standard public load balancers can use standard SKU static IPv6 addresses as their frontend public IPs or public IP prefixes.  Every deployment must be dual-stack with both IPv4 and IPv6 frontends. NAT64 translation is unavailable. For more information, see [Deploy an IPv6 dual stack application in Azure - PowerShell](../../load-balancer/virtual-network-ipv4-ipv6-dual-stack-standard-load-balancer-powershell.md) (Basic public load balancers can use basic SKU dynamic IPv6 addresses as their frontend public IPs.).
+* Standard public load balancers can use standard SKU static IPv6 addresses as their frontend public IPs or public IP prefixes. Every deployment must be dual-stack with both IPv4 and IPv6 frontends. NAT64 translation is unavailable. For more information, see [Deploy an IPv6 dual stack application in Azure - PowerShell](../../load-balancer/virtual-network-ipv4-ipv6-dual-stack-standard-load-balancer-powershell.md) (Basic public load balancers can use basic SKU dynamic IPv6 addresses as their frontend public IPs.).
 
-* When multiple frontends are assigned to a public load balancer, there isn't a method to assign flows from particular backend instances to egress on a specific IP.  For more information, see [Multiple frontends for Azure Load Balancer](../../load-balancer/load-balancer-multivip-overview.md).
+* When multiple frontends are assigned to a public load balancer, there isn't a method to assign flows from particular backend instances to egress on a specific IP. For more information, see [Multiple frontends for Azure Load Balancer](../../load-balancer/load-balancer-multivip-overview.md).
 
 ## Next steps