Skip to content

Commit 153066d

Browse files
committed
typo fixes
1 parent 4b03de7 commit 153066d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/modeling-simulation-workbench/how-to-guide-private-network.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -31,10 +31,10 @@ Before you create a [connector](./concept-connector.md) for private IP networkin
3131
| Setting | Value |
3232
|:---------------------|:--------------------------------------------|
3333
| **Role** | **Network Contributor** |
34-
| **Assign access to** | **User, group, or service principal** |
34+
| **Assign access to** | **Resource group** |
3535
| **Members** | **Azure Modeling and Simulation Workbench** |
3636

37-
[!INCLUDE [azure-hpc-workbench-alert](includes/azure-hpc-workbench-alert.md)]
37+
[!INCLUDE [azure-hpc-workbench-alert](includes/azure-hpc-workbench-alert.md)]
3838

3939
## Create the private network connector
4040

@@ -48,7 +48,7 @@ Each chamber can have only one connector. If you have a public IP connector or o
4848
1. Choose whether the copy/paste permission should be enabled for the chamber. You can learn about security boundary implications copy and paste in the [Enable copy/paste in Azure Modeling and Simulation Workbench](how-to-guide-enable-copy-paste.md) article.
4949
1. Under **Network Access**, select **VPN** in **Connect on-premises network**.
5050
1. In **Virtual Network**, select the virtual network you designated or created in [Create or designate a virtual network](#create-or-designate-a-virtual-network) earlier.
51-
1. Select the *default* **Subnet.
51+
1. Select the *default* **Subnet**.
5252
:::image type="content" source="media/howtoguide-private-network/create-private-network.png" alt-text="Screenshot of chamber connector with VPN and Review+Create button highlighted in red.":::
5353
1. Select **Review + create**.
5454
1. If validation passes, select **Create**. Private networking connectors take approximately 30 minutes to deploy.

0 commit comments

Comments
 (0)