Skip to content

Commit aa0bc39

Browse files
authored
pencil edit
1 parent 6b6eb15 commit aa0bc39

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

articles/virtual-network-manager/concept-connectivity-configuration.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -160,7 +160,7 @@ To enforce peering, you must enable the peering enforcement option when creating
160160

161161
After creating and deploying this configuration:
162162

163-
- All peerings created by Azure Virtual Network Manager or pre-existing customer peerings inside the topology become enforced.
163+
- All peerings created by Azure Virtual Network Manager or preexisting customer peerings inside the topology become enforced.
164164
- If a peering belongs to more than one topology, any configuration marked as enforced enforces that peering.
165165

166166
### How to remove enforcement on peering
@@ -179,4 +179,4 @@ To remove enforcement:
179179
- [Learn how to deploy a hub-and-spoke topology with Azure Firewall](how-to-deploy-hub-spoke-topology-with-azure-firewall.md).
180180
- [Understand configuration deployments](concept-deployments.md) to effectively manage your network settings.
181181
- [Block unwanted network traffic](how-to-block-network-traffic-portal.md) using security admin configurations.
182-
- [Deploy Azure Virtual Network Manager using Terraform](create-virtual-network-manager-terraform.md) to quickly set up your environment.
182+
- [Deploy Azure Virtual Network Manager using Terraform](create-virtual-network-manager-terraform.md) to quickly set up your environment.

0 commit comments

Comments
 (0)