Skip to content

Commit 5bcabb0

Browse files
Typo fixes
1 parent 9132662 commit 5bcabb0

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

articles/documentdb/how-to-migrate-vs-code-extension.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -226,7 +226,7 @@ The following table summarizes the supported migration sources:
226226

227227
### Public connectivity
228228

229-
In public connectivity mode, the Azure Database Migration Service (DMS) connects to your source and target servers over the public internet. DMS provides static IP addresses that you add to the firewall allow lists on both the source and target servers. DMS uses a shared public virtual network (VNet) for all migrations within a given region. While this VNet is shared across customers, each migration job runs on its own isolated private worker node to ensure job-level isolation.
229+
In public connectivity mode, the Azure Database Migration Service (DMS) connects to your source and target servers over the public internet. DMS provides static IP addresses that you add to the firewall allow lists on both the source and target servers. DMS uses a shared public virtual network for all migrations within a given region. While this virtual network is shared across customers, each migration job runs on its own isolated private worker node to ensure job-level isolation.
230230

231231
Use public connectivity when:
232232
- Your source and target servers are accessible through public IP addresses.
@@ -247,11 +247,11 @@ To enable public connectivity:
247247

248248
### Private connectivity
249249

250-
In private connectivity mode, DMS provisions a dedicated private VNet for each migration job and peers it with your source and target VNets. This means every job gets both isolated worker nodes and an isolated network, ensuring that no traffic crosses between jobs and no shared network paths exist between customers.
250+
In private connectivity mode, DMS provisions a dedicated private virtual network for each migration job and peers it with your source and target virtual networks. This means every job gets both isolated worker nodes and an isolated network, ensuring that no traffic crosses between jobs and no shared network paths exist between customers.
251251

252252
The extension supports up to two virtual networks:
253-
- **Source VNet**: The virtual network where your source MongoDB server is accessible.
254-
- **Target VNet**: The virtual network where your Azure DocumentDB cluster is accessible.
253+
- **Source virtual network**: The virtual network where your source MongoDB server is accessible.
254+
- **Target virtual network**: The virtual network where your Azure DocumentDB cluster is accessible.
255255

256256
Use private connectivity when:
257257
- Your source or target servers aren't accessible over the public internet.

0 commit comments

Comments
 (0)