Update public-ip-basic-upgrade-guidance.md

Removed "LB" acronym as it is only used once and spelt out Load Balancer - As per Microsoft Writing Style guide on acronyms that are used once:

https://learn.microsoft.com/en-us/style-guide/acronyms#dont-introduce-acronyms-that-are-used-just-once

Author: huffmatt

articles/virtual-network/ip-services/public-ip-basic-upgrade-guidance.md

@@ -38,7 +38,7 @@ We recommend the following approach to upgrade to Standard SKU public IP address
  | Resource using Basic SKU public IP addresses | Decision path |
   | ------ | ------ |
   | Virtual Machine or Virtual Machine Scale Sets (flex model) | Disassociate IP(s) and utilize the upgrade options detailed after the table. For virtual machines, you can use the [upgrade script](public-ip-upgrade-vm.md). |
-  | Load Balancer (Basic SKU) | New LB SKU required. Use the upgrade script [Upgrade Basic Load Balancer to Standard SKU](../../load-balancer/upgrade-basic-standard-with-powershell.md) to upgrade to Standard Load Balancer |
+  | Load Balancer (Basic SKU) | New Load Balancer SKU required. Use the upgrade script [Upgrade Basic Load Balancer to Standard SKU](../../load-balancer/upgrade-basic-standard-with-powershell.md) to upgrade to Standard Load Balancer |
 | VPN Gateway (using Basic IPs) |At this time, it's not necessary to upgrade. When an upgrade is necessary, we'll update this decision path with migration information and send out a service health alert. |
 |  ExpressRoute Gateway (using Basic IPs) | New ExpressRoute Gateway is required. Follow the [ExpressRoute Gateway migration guidance](../../expressroute/gateway-migration.md) for upgrading from Basic to Standard SKU.  |
   | Application Gateway (v1 SKU) | New AppGW SKU required. Use this [migration script to migrate from v1 to v2](../../application-gateway/migrate-v1-v2.md).  |