Revise VPN Gateway Basic SKU recommendation

Updated the note regarding the Basic SKU for VPN Gateways to recommend using availability zone SKUs for new gateways.

Author: staleycyn

learn-pr/wwl-azure/design-implement-hybrid-networking/includes/2-design-implement-vpn-gateway.md

@@ -27,8 +27,7 @@ Creating a virtual network gateway can take some time to complete, so it's vital
 When you create a VPN Gateway, you must select the [gateway SKU](/azure/vpn-gateway/about-gateway-skus). You can select a SKU that satisfies your requirements based on the workload, throughput, feature, and SLAs. 
 
 > [!TIP]
-> The Basic SKU has feature and performance limitations and shouldn't be used in  production environments. 
-
+> The Basic SKU has feature and performance limitations and shouldn't be used in production environments. For new gateways, use availability zone (AZ) SKUs. The following table summarizes the current production SKUs.
 
 ## VPN Gateway types
 
@@ -77,4 +76,4 @@ You can create an Azure VPN gateway in an active-standby configuration. Active-s
 
 You can create an Azure VPN gateway in an active-active configuration. In the active-active configuration, both instances of the gateway establish VPN tunnels to your on-premises VPN device. The traffic from your Azure virtual network to your on-premises network is routed through both tunnels simultaneously. If an outage occurs, Azure automatically switches to the other tunnel. 
 
-:::image type="content" source="../media/vpn-active-active-89241ba7.png" alt-text="Diagram of an Azure VPN Gateway in active-active configuration.":::
+:::image type="content" source="../media/vpn-active-active-89241ba7.png" alt-text="Diagram of an Azure VPN Gateway in active-active configuration.":::