Acrolinx edits

Author: sdwheeler

articles/cloud-shell/security/how-to-support-multiple-users.md

@@ -6,19 +6,18 @@ ms.date: 02/04/2025
 ---
 # Allow multiple users to use a single storage account and file share
 
-By default, the storage resources created by Azure Cloud Shell are designed to be used by a single
-user. A single-user deployment is the most secure configuration because each user can only access
-their own file share. However, you might have a need to allow multiple users access to a single
-deployment. To support access for multiple users, you need to make the following changes:
+By default, the storage resources created by Azure Cloud Shell are intended for a single user. A
+single-user deployment is the most secure configuration because each user can only access their own
+file share. However, you might have a need to allow multiple users access to a single deployment. To
+support access for multiple users, you need to make the following changes:
 
-- Increase File Share quota
+- Increase the Azure File share quota
 - Assign roles to the users that allow access to the storage resources
 
 > [!WARNING]
-> While it's possible to allow multiple users to share a single storage account and file share, it's
-> not recommended. Using the configuration steps in this article grants each of the configured users
-> access to the all the files in the file share. If you need to support multiple users, consider
-> creating a separate storage account and file share for each user.
+> Using the configuration steps in this article grants each user you configure access to the all the
+> files in the file share. For the best security, create separate storage accounts and file shares
+> for each user.
 
 ## Increase File Share quota
 
@@ -39,7 +38,7 @@ Use the following steps to change the file share quota:
    Cloud Shell environment and view the details.
 1. From the left-hand menu, expand **Data storage** and select **File shares**.
 1. Locate the file share that you're using for the Azure Cloud Shell environment.
-1. On the file share for Cloud Shell, select the 3-dots menu.
+1. On the file share for Cloud Shell, select the triple-dot menu.
 1. Select **Edit quota** from the menu.
 1. Change the **Quota** amount to the desired size.
 1. Select **OK** to save the change.

articles/cloud-shell/vnet/deployment.md

@@ -115,22 +115,26 @@ command line, see [Alternate way to get the Azure Container Instance ID][10].
    [![Screenshot of searching for Azure Container Instance Service.][95a]][95b]
 
 1. In the results, under **Enterprise applications**, select **Azure Container Instance Service**.
-1. On the **Overview** page for **Azure Container Instance Service**, find the **Object ID** value
-   that's listed as a property.
+1. On the **Overview** page for **Azure Container Instance Service**, locate the **Object ID** value
+   listed under **Properties**.
 
    You use this ID in the quickstart template for the virtual network.
 
    [![Screenshot of Azure Container Instance Service details.][96a]][96b]
 
 ## 3. Create the required network resources by using the ARM template
 
-Use the [Azure Cloud Shell - VNet][12] template to create Cloud Shell resources in a virtual
-network. The template creates three subnets under the virtual network that you created earlier. You
-might choose to change the supplied names of the subnets or use the defaults.
+To create Cloud Shell resources in a virtual network, use the ARM template named
+[Azure Cloud Shell - VNet][12]. The template creates three subnets under the virtual network that
+you created earlier. You might choose to change the supplied names of the subnets or use the
+defaults.
 
-The virtual network, along with the subnets, requires valid IP address assignments. You need at
-least one IP address for the Relay subnet and enough IP addresses in the container subnet to support
-the number of concurrent sessions that you expect to use.
+The virtual network and the subnets require valid IP address assignments. You need enough addresses
+to support the following resources:
+
+- At least one IP address for the Relay subnet
+- Enough IP addresses in the container subnet to support the number of concurrent sessions that you
+  expect to use
 
 The ARM template requires specific information about the resources that you created earlier, along
 with naming information for new resources. This information is filled out along with the prefilled
@@ -176,8 +180,9 @@ subscription.
 
 ## 4. Create the virtual network storage by using the ARM template
 
-Use the [Azure Cloud Shell - VNet storage][13] template to create Cloud Shell resources in a virtual
-network. The template creates the storage account and assigns it to the private virtual network.
+To create Cloud Shell resources in a virtual network, use the ARM template named
+[Azure Cloud Shell - VNet storage][13]. The template creates the storage account and assigns it to
+the private virtual network.
 
 The ARM template requires specific information about the resources that you created earlier, along
 with naming information for new resources.