Skip to content

Commit ae50fcc

Browse files
committed
acrolinx tweaks
1 parent 61d69a1 commit ae50fcc

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

articles/route-server/quickstart-configure-route-server-cli.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -49,7 +49,7 @@ az network vnet create \
4949

5050
### Add a dedicated subnet
5151

52-
Azure Route Server requires a dedicated subnet named *RouteServerSubnet*. The subnet size has to be at least /27 or shorter prefix (such as /26 or /25), otherwise you may receive an error message when deploying the Route Server. Create a subnet configuration named **RouteServerSubnet** with [az network vnet subnet create](/cli/azure/network/vnet/subnet#az-network-vnet-subnet-create):
52+
Azure Route Server requires a dedicated subnet named *RouteServerSubnet*. The subnet size has to be at least /27 or shorter prefix (such as /26 or /25), otherwise you might receive an error message when deploying the Route Server. Create a subnet configuration named **RouteServerSubnet** with [az network vnet subnet create](/cli/azure/network/vnet/subnet#az-network-vnet-subnet-create):
5353

5454
1. Run the following command to add the *RouteServerSubnet* to your virtual network.
5555

@@ -101,7 +101,7 @@ Azure Route Server requires a dedicated subnet named *RouteServerSubnet*. The su
101101
102102
Use [az network routeserver peering create](/cli/azure/network/routeserver/peering#az-network-routeserver-peering-create) to establish BGP peering between the Route Server and the NVA:
103103
104-
The `peer-ip` is the virtual network IP assigned to the NVA. The `peer-asn` is the Autonomous System Number (ASN) configured in the NVA. The ASN can be any 16-bit number other than the ones in the range of 65515-65520. This range of ASNs are reserved by Microsoft.
104+
The `peer-ip` is the virtual network IP assigned to the NVA. The `peer-asn` is the Autonomous System Number (ASN) configured in the NVA. The ASN can be any 16-bit number other than the ones in the range of 65515-65520. This range of ASNs is reserved by Microsoft.
105105
106106
```azurecli-interactive
107107
az network routeserver peering create \
@@ -124,7 +124,7 @@ az network routeserver show \
124124
--resource-group myRouteServerRG
125125
```
126126

127-
The output will look like the following:
127+
The output will look like the following example:
128128

129129
```
130130
RouteServerAsn : 65515
@@ -151,7 +151,7 @@ If you have a virtual network gateway (ExpressRoute or VPN) in the same virtual
151151

152152
[!INCLUDE [downtime note](../../includes/route-server-note-vng-downtime.md)]
153153

154-
1. To enable route exchange between Azure Route Server and the gateway(s), use [az network routerserver update](/cli/azure/network/routeserver#az-network-routeserver-update) with the `--allow-b2b-traffic` flag set to **true**:
154+
1. To enable route exchange between Azure Route Server and the gateways, use [az network routerserver update](/cli/azure/network/routeserver#az-network-routeserver-update) with the `--allow-b2b-traffic` flag set to **true**:
155155

156156
```azurecli-interactive
157157
az network routeserver update \
@@ -160,7 +160,7 @@ If you have a virtual network gateway (ExpressRoute or VPN) in the same virtual
160160
--allow-b2b-traffic true
161161
```
162162
163-
2. To disable route exchange between Azure Route Server and the gateway(s), use [az network routerserver update](/cli/azure/network/routeserver#az-network-routeserver-update) with the `--allow-b2b-traffic` flag set to **false**:
163+
2. To disable route exchange between Azure Route Server and the gateways, use [az network routerserver update](/cli/azure/network/routeserver#az-network-routeserver-update) with the `--allow-b2b-traffic` flag set to **false**:
164164
165165
```azurecli-interactive
166166
az network routeserver update \
@@ -212,9 +212,9 @@ If you no longer need the Azure Route Server, use the first command to remove th
212212
--resource-group myRouteServerRG
213213
```
214214
215-
## Next steps
215+
## Next step
216216
217-
After you've created the Azure Route Server, continue on to learn more about how Azure Route Server interacts with ExpressRoute and VPN Gateways:
217+
Continue to learn more about how Azure Route Server interacts with ExpressRoute and VPN Gateways:
218218
219219
> [!div class="nextstepaction"]
220220
> [Azure ExpressRoute and Azure VPN support](expressroute-vpn-support.md)

0 commit comments

Comments
 (0)