Skip to content

Commit b598a4b

Browse files
committed
style: Fix Acrolinx issues
- Remove filler word 'just' from 'just created' - Expand acronyms on first use (VMs, IDs, NIC) - Add serial commas before 'or' in 'enter, or select' - Improve clarity and consistency per Microsoft style guide
1 parent 7ba085c commit b598a4b

1 file changed

Lines changed: 10 additions & 10 deletions

File tree

articles/virtual-network/tutorial-connect-virtual-networks.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ If you choose to install and use PowerShell locally, this article requires the A
6666

6767
1. Select **+ Create**.
6868

69-
1. In the **Basics** tab of **Create a resource group**, enter or select the following information:
69+
1. In the **Basics** tab of **Create a resource group**, enter, or select the following information:
7070

7171
| Setting | Value |
7272
| ------- | ----- |
@@ -84,7 +84,7 @@ If you choose to install and use PowerShell locally, this article requires the A
8484

8585
1. Select **+ Create**.
8686

87-
1. On the **Basics** tab of **Create virtual network**, enter or select the following information:
87+
1. On the **Basics** tab of **Create virtual network**, enter, or select the following information:
8888

8989
| Setting | Value |
9090
|---|---|
@@ -101,7 +101,7 @@ If you choose to install and use PowerShell locally, this article requires the A
101101

102102
1. In the address space box in **Subnets**, select the **default** subnet.
103103

104-
1. In **Edit subnet**, enter or select the following information:
104+
1. In **Edit subnet**, enter, or select the following information:
105105

106106
| Setting | Value |
107107
|---|---|
@@ -117,7 +117,7 @@ If you choose to install and use PowerShell locally, this article requires the A
117117

118118
## Deploy Azure Bastion
119119

120-
Azure Bastion uses your browser to connect to VMs in your virtual network over secure shell (SSH) or remote desktop protocol (RDP) by using their private IP addresses. The VMs don't need public IP addresses, client software, or special configuration. For more information about Azure Bastion, see [Azure Bastion](/azure/bastion/bastion-overview).
120+
Azure Bastion uses your browser to connect to virtual machines (VMs) in your virtual network over secure shell (SSH) or remote desktop protocol (RDP) by using their private IP addresses. The virtual machines don't need public IP addresses, client software, or special configuration. For more information about Azure Bastion, see [Azure Bastion](/azure/bastion/bastion-overview).
121121

122122
>[!NOTE]
123123
>[!INCLUDE [Pricing](~/reusable-content/ce-skilling/azure/includes/bastion-pricing.md)]
@@ -126,7 +126,7 @@ Azure Bastion uses your browser to connect to VMs in your virtual network over s
126126

127127
1. Select **+ Create**.
128128

129-
1. In the **Basics** tab of **Create a Bastion**, enter or select the following information:
129+
1. In the **Basics** tab of **Create a Bastion**, enter, or select the following information:
130130

131131
| Setting | Value |
132132
|---|---|
@@ -400,7 +400,7 @@ Resources in one virtual network can't communicate with resources in the other v
400400

401401
## Peer virtual networks
402402

403-
Peerings are established between virtual network IDs. Obtain the ID of each virtual network with [az network vnet show](/cli/azure/network/vnet#az-network-vnet-show) and store the IDs in their respective variables.
403+
Peerings are established between virtual network resource IDs. Obtain the ID of each virtual network with [az network vnet show](/cli/azure/network/vnet#az-network-vnet-show) and store the resource IDs in their respective variables.
404404

405405
```azurecli-interactive
406406
# Get the id for vnet-1.
@@ -455,15 +455,15 @@ Resources in one virtual network can't communicate with resources in the other v
455455

456456
## Create virtual machines
457457

458-
Test the communication between the virtual machines by creating a virtual machine in each virtual network. The virtual machines can communicate with each other over the virtual network peering you just created.
458+
Test the communication between the virtual machines by creating a virtual machine in each virtual network. The virtual machines can communicate with each other over the virtual network peering you created.
459459

460460
### [Portal](#tab/portal)
461461

462462
1. In the search box at the top of the portal, enter **Virtual machine**. Select **Virtual machines** in the search results.
463463

464464
1. Select **+ Create** then **Azure virtual machine**.
465465

466-
1. In **Create a virtual machine** enter or select the following information in the **Basics** tab:
466+
1. In **Create a virtual machine** enter, or select the following information in the **Basics** tab:
467467

468468
| Setting | Value |
469469
| ------- | ----- |
@@ -488,15 +488,15 @@ Test the communication between the virtual machines by creating a virtual machin
488488

489489
1. Select **Next: Disks** then **Next: Networking**.
490490

491-
1. In the Networking tab, enter or select the following information:
491+
1. In the Networking tab, enter, or select the following information:
492492

493493
| Setting | Value |
494494
| ------- | ----- |
495495
| **Network interface** | |
496496
| Virtual network | Select **vnet-1**. |
497497
| Subnet | Select **subnet-1 (10.0.0.0/24)**. |
498498
| Public IP | Select **None**. |
499-
| NIC network security group | Select **Advanced**. |
499+
| Network interface (NIC) network security group | Select **Advanced**. |
500500
| Configure network security group | Select **Create new**. </br> In **Name** enter **nsg-1**. </br> Select **OK**. |
501501

502502
1. Leave the rest of the options at the defaults and select **Review + create**.

0 commit comments

Comments
 (0)