Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into us297322-content-curation

Author: asudbring

articles/vpn-gateway/tutorial-site-to-site-portal.md

@@ -125,7 +125,7 @@ Site-to-site connections to an on-premises network require a VPN device. In this
 
 ## <a name="CreateConnection"></a>Create VPN connections
 
-Create a site-to-site VPN connection between your virtual network gateway and your on-premises VPN device. If you're using an active-active mode gateway (recommended), each gateway VM instance has a separate assigned IP address object. To properly configure [highly available connectivity](vpn-gateway-highlyavailable.md), you must connect each VM instance to your VPN device.
+Create a site-to-site VPN connection between your virtual network gateway and your on-premises VPN device. If you're using an active-active mode gateway (recommended), each gateway VM instance has a separate IP address. To properly configure [highly available connectivity](vpn-gateway-highlyavailable.md), you must establish a tunnel between each VM instance and your VPN device. Both tunnels are part of the same connection.
 
 Create a connection by using the following values:
 

includes/vpn-gateway-active-active-tunnel.md

@@ -6,4 +6,4 @@ ms.service: azure-vpn-gateway
 ms.topic: include
 ---
 
-For S2S connections with an active-active mode VPN gateway, if you only configure your VPN device to accept or establish a tunnel to one gateway VM instance (instead of both instances), the tunnel will go down during maintenance. If your VPN device doesn't support this type of configuration, we don't recommend that you configure your gateway for active-active mode.
+For S2S connections with an active-active mode VPN gateway, ensure tunnels are established to each gateway VM instance. If you establish a tunnel to only one gateway VM instance, the connection will go down during maintenance. If your VPN device doesn't support this setup, configure your gateway for active-standby mode instead.