Skip to content

Commit 508780a

Browse files
authored
Pencil edit: Id > ID
1 parent e07e27e commit 508780a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/virtual-wan/expressroute-powershell.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ $expressroutegatewayinhub = New-AzExpressRouteGateway -MaxScaleUnits <UInt32> -M
9595

9696
The next step is to get the private peering ID of the ExpressRoute circuit. You can either create a new circuit, or get the ID from an existing circuit. Use one of the following examples.
9797

98-
**New circuit** - This example creates a new ExpressRoute circuit and gets its private peering Id.
98+
**New circuit** - This example creates a new ExpressRoute circuit and gets its private peering ID.
9999

100100
```azurepowershell-interactive
101101
$ExpressRouteCircuit = New-AzExpressRouteCircuit -ResourceGroupName "testRG" -Name "testExpressRouteCircuit" -Location "West Central US" -SkuTier Premium -SkuFamily MeteredData -ServiceProviderName "Equinix" -PeeringLocation "Silicon Valley" -BandwidthInMbps 200
@@ -107,7 +107,7 @@ The next step is to get the private peering ID of the ExpressRoute circuit. You
107107
$ExpressRouteCircuitPeeringId = $ExpressRouteCircuit.Peerings[0].Id
108108
```
109109

110-
**Existing circuit** - This example gets the details and Private Peering Id from an existing ExpressRoute circuit.
110+
**Existing circuit** - This example gets the details and Private Peering ID from an existing ExpressRoute circuit.
111111

112112
```azurepowershell-interactive
113113

0 commit comments

Comments
 (0)