Merge pull request #186461 from ChaitanyaNaykodi-MSFT/patch-78

(AzureCXP) fixed typo

Author: PRMerger15

articles/virtual-network/virtual-network-disaster-recovery-guidance.md

@@ -34,7 +34,7 @@ A: The virtual network and the resources in the affected region remains inaccess
 
 ![Simple Virtual Network Diagram](./media/virtual-network-disaster-recovery-guidance/vnet.png)
 
-**Q: What can I to do re-create the same virtual network in a different region?**
+**Q: What can I do to re-create the same virtual network in a different region?**
 
 A: Virtual networks are fairly lightweight resources. You can invoke Azure APIs to create a VNet with the same address space in a different region. To recreate the same environment that was present in the affected region, you make API calls to redeploy the Cloud Services web and worker roles, and the virtual machines that you had. If you have on-premises connectivity, such as in a hybrid deployment, you have to deploy a new VPN Gateway, and connect to your on-premises network.