acrolinx

Author: sipastak

articles/virtual-desktop/azure-extended-zones.md

@@ -32,24 +32,24 @@ Before you can use Azure Virtual Desktop with Azure Extended Zones, you need:
 
 - [Access](#gaining-access-to-an-azure-extended-zone) to an Azure Extended Zone.
 
-- An existing [Azure Load Balancer](../load-balancer/load-balancer-outbound-connections.md) on the virtual network that the session hosts are being deployed to. You will need to use the frontend IP address(es) of a load balancer for outbound connectivity to the internet in order for the session hosts to join a host pool.  
+- An existing [Azure Load Balancer](../load-balancer/load-balancer-outbound-connections.md) on the virtual network that the session hosts are being deployed to. You'll need to use the frontend IP address(es) of a load balancer for outbound connectivity to the internet in order for the session hosts to join a host pool.  
 
 ## Gaining access to an Azure Extended Zone 
 
-To deploy Azure Virtual Desktop in Azure Extended Zone locations, you will need to explicitly register your subscription with the respective Azure Extended Zone using an account that is a subscription owner. By default, this capability is not enabled. Registration of an Azure Extended Zone is always scoped to a specific subscription, ensuring control and management over the resources deployed in these locations. Once the subscription is registered with the Azure Extended Zone, you can deploy and manage your virtual desktop and applications within that specific Azure Extended Zone.
+To deploy Azure Virtual Desktop in Azure Extended Zone locations, you'll need to explicitly register your subscription with the respective Azure Extended Zone using an account that is a subscription owner. By default, this capability isn't enabled. Registration of an Azure Extended Zone is always scoped to a specific subscription, ensuring control and management over the resources deployed in these locations. Once the subscription is registered with the Azure Extended Zone, you can deploy and manage your virtual desktop and applications within that specific Azure Extended Zone.
 
-For more information, see ....
+For more information, see....
 
 
 ## Limitations
 
 Azure Virtual Desktop with Azure Extended Zones has the following limitations:
 
-- With Azure Extended Zones, there is no default outbound internet access. The default outbound route is being retired across all Azure regions in September 2025. As Extended Zones will become generally available shortly prior to this date, they will start without this default outbound internet route. For more information, see [Default outbound access for VMs in Azure will be retired— transition to a new method of internet access.](https://azure.microsoft.com/updates/default-outbound-access-for-vms-in-azure-will-be-retired-transition-to-a-new-method-of-internet-access/)
+- With Azure Extended Zones, there's no default outbound internet access. The default outbound route is being retired across all Azure regions in September 2025. As Extended Zones will become generally available shortly prior to this date, they'll start without this default outbound internet route. For more information, see [Default outbound access for VMs in Azure will be retired— transition to a new method of internet access.](https://azure.microsoft.com/updates/default-outbound-access-for-vms-in-azure-will-be-retired-transition-to-a-new-method-of-internet-access/)
 
-- Azure Extended Zones do not support NAT Gateways. You will need to use an Azure Load Balancer with outbound rules enabled for outbound connectivity.
+- Azure Extended Zones don't support NAT Gateways. You'll need to use an Azure Load Balancer with outbound rules enabled for outbound connectivity.
 
-- There is a reduced set of supported VM SKUs (list to be provided, or will need to inform customers to check availability before deploying).
+- There's a reduced set of supported virtual machine SKUs.
 
 
 ## Next steps