Skip to content

Commit a0ed629

Browse files
Address comment for fixes
1 parent 682fea7 commit a0ed629

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/virtual-network-manager/common-issues.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ This article describes common issues with Azure Virtual Network Manager and prov
1818
These are some common reasons why your configuration changes aren't applied:
1919

2020

21-
### The configuration isn't applied to the regions where virtual networks are located.
21+
### The configuration isn't applied to the regions where virtual networks are located
2222

2323
You need to check the regions where the virtual networks are located. The configuration is only applied to the regions where the virtual networks are located. If you have a virtual network in a region that isn't included in the configuration, the configuration isn't applied to that virtual network.
2424

@@ -48,7 +48,7 @@ In a hub-and-spoke topology, if you enable the option to *use the hub as a gatew
4848

4949
### Members in the network group can't communicate with each other
5050

51-
If you want to have members in the network group to communicate with each other across regions in a hub and spoke topology configuration, you need to enable the global mesh option.
51+
If you want to have members in the network group communicate with each other across regions in a hub and spoke topology configuration, you need to enable the global mesh option.
5252

5353
## Next steps
5454

0 commit comments

Comments
 (0)