Skip to content

Commit 8618d5b

Browse files
committed
typos
1 parent 8ffb695 commit 8618d5b

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/api-management/migrate-stv1-to-stv2.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ Update the configuration of the VNet in each location (region) where the API Man
7777

7878
#### Prerequisites
7979

80-
* A new subnet in the current virtual network. (Alternatively, set up a subnet in a different virtual network in the same region and subscription as your API Management instance). A network security group must be attached to the subnet, and [NSG rules](api-management-using-with-vnet.ms#configure-nsg-rules) for API Management must be configured.
80+
* A new subnet in the current virtual network. (Alternatively, set up a subnet in a different virtual network in the same region and subscription as your API Management instance). A network security group must be attached to the subnet, and [NSG rules](api-management-using-with-vnet.md#configure-nsg-rules) for API Management must be configured.
8181

8282
* A Standard SKU [public IPv4 address](../virtual-network/ip-services/public-ip-addresses.md#sku) resource in the same region and subscription as your API Management instance.
8383

@@ -101,11 +101,11 @@ The virtual network configuration is updated, and the instance is migrated to th
101101

102102
### (Optional) Migrate back to original VNet and subnet
103103

104-
You may optionally reuse the original VNet and subnet in each region you used before migration to the `stv2` platform. To do so, update the VNet configuration again, this time specifying the original VNet and subnet. As in the preceding migration, expect a long-running operation, and expect the VIP address to change.
104+
You may optionally migrate back to the original VNet and subnet you used in each region before migration to the `stv2` platform. To do so, update the VNet configuration again, this time specifying the original VNet and subnet. As in the preceding migration, expect a long-running operation, and expect the VIP address to change.
105105

106106
#### Prerequisites
107107

108-
* The original subnet and VNet. A network security group must be attached to the subnet, and [NSG rules](api-management-using-with-vnet.ms#configure-nsg-rules) for API Management must be configured.
108+
* The original subnet and VNet. A network security group must be attached to the subnet, and [NSG rules](api-management-using-with-vnet.md#configure-nsg-rules) for API Management must be configured.
109109

110110
* A new Standard SKU [public IPv4 address](../virtual-network/ip-services/public-ip-addresses.md#sku) resource in the same region and subscription as your API Management instance.
111111

0 commit comments

Comments
 (0)