Skip to content

Commit 0b72dae

Browse files
authored
Typos
1 parent e02e85b commit 0b72dae

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/virtual-network-manager/create-virtual-network-manager-cli.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -147,7 +147,7 @@ az network vnet subnet create \
147147
```
148148
## Define membership for a mesh configuration
149149

150-
Azure Virtual Network manager allows you two methods for adding membership to a network group. Static membership involves manually adding virtual networks, and dynamic membership involves using Azure Policy to dynamically add virtual networks based on conditions. Choose the option you wish to complete for your mesh configuration membership
150+
Azure Virtual Network manager allows you two methods for adding membership to a network group. Static membership involves manually adding virtual networks, and dynamic membership involves using Azure Policy to dynamically add virtual networks based on conditions. Choose the option you wish to complete for your mesh configuration membership:
151151

152152
### Static membership option
153153

@@ -181,7 +181,7 @@ az network manager group static-member create \
181181
```
182182
### Dynamic membership option
183183

184-
Using Azure Policy, you'll dynamically add the three VNets with a tag **networkType** value of *Prod* to the Network Group. These are the three virtual networks to become part of the mesh configuration
184+
Using Azure Policy, you'll dynamically add the three VNets with a tag **networkType** value of *Prod* to the Network Group. These are the three virtual networks to become part of the mesh configuration.
185185

186186
> [!NOTE]
187187
> Policies can be applied to a subscription or management group, and must always be defined *at or above* the level they're created. Only virtual networks within a policy scope are added to a Network Group.

0 commit comments

Comments
 (0)