make v6 ga

Author: Tanu Balla

articles/expressroute/expressroute-howto-set-global-reach.md

@@ -25,10 +25,6 @@ Before you start configuration, confirm the following:
 * Azure private peering is configured on your ExpressRoute circuits.
 * If you want to run PowerShell locally, verify that the latest version of Azure PowerShell is installed on your computer.
 
-> [!NOTE]
-> Global Reach does **not** support configuration updates at this time. This means that if you create a Global Reach connection using the following instructions, you must delete and recreate the connection with any configuration updates. Attempting to update an existing Global Reach connection will put your ExpressRoute circuit in a failed state.
->
-
 ### Working with Azure PowerShell
 
 [!INCLUDE [updated-for-az](../../includes/hybrid-az-ps.md)]
@@ -71,7 +67,7 @@ Enable connectivity between your on-premises networks. There are separate sets o
      ```
      
      > [!NOTE]
-     > IPv6 support for ExpressRoute Global Reach is now in Public Preview. To add an IPv6 Global Reach connection, you must specify a /125 IPv6 subnet for *-AddressPrefix* and an *-AddressPrefixType* of *IPv6*.
+     > If you wish to enable IPv6 support for ExpressRoute Global Reach, you must specify a /125 IPv6 subnet for *-AddressPrefix* and an *-AddressPrefixType* of *IPv6*.
      
      ```azurepowershell-interactive
      Add-AzExpressRouteCircuitConnectionConfig -Name 'Your_connection_name' -ExpressRouteCircuit $ckt_1 -PeerExpressRouteCircuitPeering $ckt_2.Peerings[0].Id -AddressPrefix '__.__.__.__/125' -AddressPrefixType IPv6
@@ -104,8 +100,8 @@ If the two circuits are not in the same Azure subscription, you need authorizati
    Add-AzExpressRouteCircuitConnectionConfig -Name 'Your_connection_name' -ExpressRouteCircuit $ckt_1 -PeerExpressRouteCircuitPeering "circuit_2_private_peering_id" -AddressPrefix '__.__.__.__/29' -AuthorizationKey '########-####-####-####-############'
    ```
 
-   > [!NOTE]
-   > IPv6 support for ExpressRoute Global Reach is now in Public Preview. To add an IPv6 Global Reach connection, you must specify a /125 IPv6 subnet for *-AddressPrefix* and an *-AddressPrefixType* of *IPv6*.
+     > [!NOTE]
+     > If you wish to enable IPv6 support for ExpressRoute Global Reach, you must specify a /125 IPv6 subnet for *-AddressPrefix* and an *-AddressPrefixType* of *IPv6*.
 
    ```azurepowershell-interactive
    Add-AzExpressRouteCircuitConnectionConfig -Name 'Your_connection_name' -ExpressRouteCircuit $ckt_1 -PeerExpressRouteCircuitPeering $ckt_2.Peerings[0].Id -AddressPrefix '__.__.__.__/125' -AddressPrefixType IPv6 -AuthorizationKey '########-####-####-####-############'
@@ -139,7 +135,7 @@ Set-AzExpressRouteCircuit -ExpressRouteCircuit $ckt_1
 ```
 
 > [!NOTE]
-> IPv6 support for ExpressRoute Global Reach is now in Public Preview. To delete an IPv6 Global Reach connection, you must specify an *-AddressPrefixType* of *IPv6* like in the following command.
+> To delete an IPv6 Global Reach connection, you must specify an *-AddressPrefixType* of *IPv6* like in the following command.
 
 ```azurepowershell-interactive
 $ckt_1 = Get-AzExpressRouteCircuit -Name "Your_circuit_1_name" -ResourceGroupName "Your_resource_group"