Acrolinx fixes, fix to redirect

Author: yousefi-msft

.openpublishing.redirection.json

@@ -4646,8 +4646,8 @@
       "redirect_document_id": false
     },
     {
-      "source_path_from_root": "/articles/modeling-simulation-workbench/get-started-modeling-simulation-workbench.md",
-      "redirect_url": "/azure/modeling-simulation-workbench/quickstart-create-portal",
+      "source_path_from_root": "/articles/modeling-simulation-workbench/quickstart-create-portal",
+      "redirect_url": "/azure/modeling-simulation-workbench/get-started-modeling-simulation-workbench.md",
       "redirect_document_id": false
     },
     {

articles/modeling-simulation-workbench/quickstart-add-users.md

@@ -12,7 +12,7 @@ ms.date: 09/25/2024
 
 # Quickstart: Add users to a chamber
 
-After you have created your Modeling and Simulation Workbench, you will need to add users and assign roles.  In this quickstart, you will learn how to add users a chamber as either a *Chamber Admin* or *Chamber User* along with the correct Azure Entra role assignments to enable them to do tasks.
+After you create your Modeling and Simulation Workbench, you'll need to add users and assign roles. In this quickstart, you'll learn how to add users a chamber as either a *Chamber Admin* or *Chamber User* along with the correct Microsoft Entra role assignments to enable them to do tasks.
 
 If you don't have a service subscription, [create a free
 trial account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
@@ -31,7 +31,7 @@ trial account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
 
 Users are added to chambers as either **Chamber Admin** or **Chamber User** roles. You can learn more about [user personas in Modeling and Simulation Workbench](concept-user-personas.md) to pick the most fitting role.
 
-If the user is not already an **Owner** of either the subscription or the resource group, they must be assigned the following roles in addition to a chamber role.  Microsoft recommends using least privilege to protect your environment by assigning the lowest level of privilege needed to effectively perform tasks.
+If the user isn't already an **Owner** of either the subscription or the resource group, they must be assigned the following roles in addition to a chamber role. Microsoft recommends using least privilege to protect your environment by assigning the lowest level of privilege needed to effectively perform tasks.
 
 | Setting          | Value                                   |
 | :--------------- | :-------------------------------------- |
@@ -52,25 +52,25 @@ If the user is not already an **Owner** of either the subscription or the resour
 1. The **Add role assignment** pane opens. In the **Role** list, search for or scroll to find the **Reader** role. Select **Next**.
    :::image type="content" source="./media/quickstart-create-portal/chamber-iam-03.png" alt-text="Screenshot of the Add role assignment page showing where you select the Role.":::
 1. Leave the **Assign access to** as the default of **User, group, or service principal**. Choose **+ Select members**.
-1. On the **Select members** panel, search for and click on the users to be added, and then choose **Select**.
+1. On the **Select members** panel, search for and select on the users to be added, and then choose **Select**.
    :::image type="content" source="./media/quickstart-create-portal/chamber-iam-04.png" alt-text="Screenshot of the pane for adding a role assignment and selecting a security principal.":::
 1. Select **Review + assign** to assign the selected role.
 1. Repeat these same steps, but assign the **Classic Storage Account Contributor** role for the same users.
 
 ### Assign Chamber Admin or Chamber User role
 
-Resource group level privileges allow users to perform infrastructure level tasks in the environment, but don't define the user's privilege level. Users must be assigned a role for each chamber they are to have access to. The role assigned determines whether they will have `root` privileges across that chamber. **Chamber Admin** has `sudo` privileges in all virtual machines (VM) in the chamber, whereas **Chamber User** does not.
+Resource group level privileges allow users to perform infrastructure level tasks in the environment, but don't define the user's privilege level. Users must be assigned a role for each chamber they're to have access to. The role assigned determines whether users have `root` privileges across that chamber. **Chamber Admin** has `sudo` privileges in all virtual machines (VM) in the chamber, whereas **Chamber User** doesn't.
 
-1. Navigate to the chamber where the role is to be assigned. Be sure you are at the chamber level, as chamber roles do not inherit.
+1. Navigate to the chamber where the role is to be assigned. Be sure you are at the chamber level, as chamber roles don't inherit.
 1. Select **Access Control (IAM)** from the left menu.
 1. From the roles screen, select **Add** > **Add role assignment**.
    :::image type="content" source="./media/quickstart-create-portal/chamber-iam-02.png" alt-text="Screenshot that shows selections for adding a role assignment.":::
 1. The **Add role assignment** pane opens. In the **Role** list, search for or scroll to find either the **Chamber User** or the **Chamber Admin** role. Select the appropriate role and then select **Next**.
    :::image type="content" source="./media/quickstart-create-portal/chamber-iam-03.png" alt-text="Screenshot of the Add role assignment page showing where you select the Role.":::
 1. Leave the **Assign access to** as the default of **User, group, or service principal**. Choose **+ Select members**.
-1. On the **Select members** panel, search for and click on the users to be added, and then choose **Select**.
+1. On the **Select members** panel, search for and select on the users to be added, and then choose **Select**.
    :::image type="content" source="./media/quickstart-create-portal/chamber-iam-04.png" alt-text="Screenshot of the pane for adding a role assignment and selecting a security principal.":::
-1. After you have selected all the users for that role, select **Review + assign** to assign the selected role.
+1. After you select all the users for that role, select **Review + assign** to assign the selected role.
 
    > [!NOTE]
    > Allow at least five minutes for the provisioning of the users to propagate throughout the chamber, so they have a successful login experience.

articles/modeling-simulation-workbench/quickstart-connect-desktop.md

@@ -13,7 +13,7 @@ ms.date: 09/27/2024
 
 # Quickstart: Connect to desktop
 
-Once a workbench has been created, users can connect directly to the dashboard without visiting the portal. In this quickstart, you will connect to your Modeling and Simulation Workbench desktops and learn how to manage the desktop dashboard URLs.
+After you create a workbench, users can connect directly to the dashboard without visiting the portal. In this quickstart, you'll learn how to connect to your Modeling and Simulation Workbench desktops and learn how to manage the desktop dashboard URLs.
 
 If you don't have a service subscription, [create a free
 trial account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F)
@@ -22,11 +22,11 @@ trial account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F)
 
 [!INCLUDE [prerequisite-mswb-chamber](includes/prerequisite-chamber.md)]
 
-* If using a public IP connector, your current public facing IP address must be on the allow-list.
+* If using a public IP connector, your current public facing IP address must be on the allowlist.
 
 ## Locate the desktop dashboard URL
 
-Each [connector](concept-connector.md) has a **Desktop dashboard** URL that opens the dashboard of all created VMs. The dashboard URL can be distributed to users directly so that they don't have to visit the Azure portal and navigate to the connector. You will need to navigate to the connector to obtain the dashboard URL.
+Each [connector](concept-connector.md) has a **Desktop dashboard** URL that opens the dashboard of all created VMs. The dashboard URL can be distributed to users directly so that they don't have to visit the Azure portal and navigate to the connector. You need to navigate to the connector to obtain the dashboard URL.
 
 > [!TIP]
 > From the resource group listing, you can select **Manage view** / **Show hidden types** to directly show all the nested resources of the workbench and select the connector from there without having to navigate the workbench hierarchy.
@@ -41,10 +41,10 @@ Each [connector](concept-connector.md) has a **Desktop dashboard** URL that open
 
 ## Open the desktop
 
-1. In the connector overview screen, the **Desktop dashboard** link is in the right column. Select the *copy* icon to copy the URL to your clipboard or click on it. Clicking the link will open a new tab or window.
+1. In the connector overview screen, the **Desktop dashboard** link is in the right column. Select the *copy* icon to copy the URL to your clipboard or select on it. Clicking the link opens a new tab or window.
     :::image type="content" source="media/quickstart-connect-desktop/connector-dashboard-url.png" alt-text="Screenshot of connector overview page with desktop dashboard URL highlighted in a red rectangle.":::
-1. The dashboard screen will open presenting all available VMs.
-1. Select a VM. If you have not previously installed the desktop client, you will be prompted to do so. There is also a web client which does not require a local client to be installed.
+1. The dashboard screen opens presenting all available VMs.
+1. Select a virtual machine (VM). If you don't have the desktop client installed, you're prompted to do so. There's also a web client which doesn't require a local client to be installed.
 
 ## Next step