Skip to content

Commit 705eec9

Browse files
Merge pull request #211408 from amirdahan72/patch-6
Changed a minor typo
2 parents a62215f + e612679 commit 705eec9

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/ddos-protection/ddos-disaster-recovery-guidance.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ A: The virtual network and the resources in the affected region remains inaccess
3030

3131
![Simple Virtual Network Diagram.](../virtual-network/media/virtual-network-disaster-recovery-guidance/vnet.png)
3232

33-
**Q: What can I to do re-create the same virtual network in a different region?**
33+
**Q: What can I do to re-create the same virtual network in a different region?**
3434

3535
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 resources in the VNets 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.
3636

@@ -44,4 +44,4 @@ To create a virtual network, see [Create a virtual network](../virtual-network/m
4444

4545
## Next steps
4646

47-
- Learn how to [create a DDoS protection plan](manage-ddos-protection.md).
47+
- Learn how to [create a DDoS protection plan](manage-ddos-protection.md).

0 commit comments

Comments
 (0)