Merge pull request #196965 from LouisBerner/v-lberner-ADO_1945290

updated artwork in add-local-share-4.png

Author: v-regandowner

articles/databox-online/azure-stack-edge-gpu-manage-shares.md

@@ -7,7 +7,7 @@ author: alkohli
 ms.service: databox
 ms.subservice: edge
 ms.topic: how-to
-ms.date: 02/26/2021
+ms.date: 05/03/2022
 ms.author: alkohli
 ---
 # Use Azure portal to manage shares on your Azure Stack Edge Pro
@@ -38,11 +38,11 @@ Do the following steps in the Azure portal to create a share.
 
 3. Select a **Type** for the share. The type can be **SMB** or **NFS**, with SMB being the default. SMB is the standard for Windows clients, and NFS is used for Linux clients. Depending upon whether you choose SMB or NFS shares, options presented are slightly different.
 
-4. Provide a **Storage account** where the share lives. A container is created in the storage account with the share name if the container already does not exist. If the container already exists, then the existing container is used.
+4. Provide a **Storage account** where the share lives. A container is created in the storage account with the share name if the container already doesn't exist. If the container already exists, then the existing container is used.
 
 5. From the dropdown list, choose the **Storage service** from block blob, page blob, or files. The type of the service chosen depends on which format you want the data to reside in Azure. For example, in this instance, we want the data to reside as block blobs in Azure, hence we select **Block Blob**. If choosing **Page Blob**, you must ensure that your data is 512 bytes aligned. Use **Page blob** for VHDs or VHDX that are always 512 bytes aligned.
 
-6. This step depends on whether you are creating an SMB or an NFS share.
+6. This step depends on whether you're creating an SMB or an NFS share.
     - **If creating an SMB share** - In the **All privilege local user** field, choose from **Create new** or **Use existing**. If creating a new local user, provide the **username**, **password**, and then confirm password. This assigns the permissions to the local user. After you have assigned the permissions here, you can then use File Explorer to modify these permissions.
 
         ![Add SMB share](media/azure-stack-edge-gpu-manage-shares/add-smb-share.png)
@@ -52,9 +52,9 @@ Do the following steps in the Azure portal to create a share.
 
         ![Add NFS share](media/azure-stack-edge-gpu-manage-shares/add-nfs-share.png)
 
-7. To easily access the shares from Edge compute modules, use the local mount point. Select **Use the share with Edge compute** so that the share is automatically mounted after it is created. When this option is selected, the Edge module can also use the compute with the local mount point.
+7. To easily access the shares from Edge compute modules, use the local mount point. Select **Use the share with Edge compute** so that the share is automatically mounted after it's created. When this option is selected, the Edge module can also use the compute with the local mount point.
 
-8. Click **Create** to create the share. You are notified that the share creation is in progress. After the share is created with the specified settings, the **Shares** blade updates to reflect the new share.
+8. Select **Create** to create the share. You're notified that the share creation is in progress. After the share is created with the specified settings, the **Shares** blade updates to reflect the new share.
 
 ## Add a local share
 
@@ -69,7 +69,7 @@ Do the following steps in the Azure portal to create a share.
 3. Select a **Type** for the share. The type can be **SMB** or **NFS**, with SMB being the default. SMB is the standard for Windows clients, and NFS is used for Linux clients. Depending upon whether you choose SMB or NFS shares, options presented are slightly different.
 
    > [!IMPORTANT]
-   > Make sure that the Azure Storage account that you use does not have immutability policies set on it if you are using it with a Azure Stack Edge Pro or Data Box Gateway device. For more information, see [Set and manage immutability policies for blob storage](../storage/blobs/immutable-policy-configure-version-scope.md).
+   > Make sure that the Azure Storage account that you use doesn't have immutability policies set on it if you're using it with a Azure Stack Edge Pro or Data Box Gateway device. For more information, see [Set and manage immutability policies for blob storage](../storage/blobs/immutable-policy-configure-version-scope.md).
 
 4. To easily access the shares from Edge compute modules, use the local mount point. Select **Use the share with Edge compute** so that the Edge module can use the compute with the local mount point.
 
@@ -91,7 +91,7 @@ Do the following steps in the Azure portal to create a share.
 
 ## Mount a share
 
-If you created a share before you configured compute on your Azure Stack Edge Pro device, you will need to mount the share. Take the following steps to mount a share.
+If you created a share before you configured compute on your Azure Stack Edge Pro device, you'll need to mount the share. Take the following steps to mount a share.
 
 
 1. In the Azure portal, go to your Azure Stack Edge resource and then go to **Cloud storage gateway > Shares**. From the list of the shares, select the share you want to mount. The **Used for compute** column will show the status as **Disabled** for the selected share.
@@ -118,7 +118,7 @@ If you created a share before you configured compute on your Azure Stack Edge Pr
 
 Do the following steps in the Azure portal to unmount a share.
 
-1. In the Azure portal, go to your Azure Stack Edge resource and then go to **Cloud storage gateway > Shares**. From the list of the shares, select the share that you want to unmount. You want to make sure that the share you unmount is not used by any modules. If the share is used by a module, then you will see issues with the corresponding module.
+1. In the Azure portal, go to your Azure Stack Edge resource and then go to **Cloud storage gateway > Shares**. From the list of the shares, select the share that you want to unmount. You want to make sure that the share you unmount isn't used by any modules. If the share is used by a module, then you'll see issues with the corresponding module.
 
     ![Select share 2](media/azure-stack-edge-gpu-manage-shares/unmount-share-1.png)
 
@@ -136,17 +136,17 @@ Do the following steps in the Azure portal to unmount a share.
 
 ## Delete a share
 
-Do the following steps in the Azure portal to delete a share.
+Use the following steps in the Azure portal to delete a share.
 
 1. From the list of shares, select and click the share that you want to delete.
 
-    ![Select share 3](media/azure-stack-edge-gpu-manage-shares/delete-share-1.png)
+    ![Screenshot of select share 3](media/azure-stack-edge-gpu-manage-shares/delete-share-1.png)
 
-2. Click **Delete**.
+2. Select **Delete**.
 
-    ![Click delete](media/azure-stack-edge-gpu-manage-shares/delete-share-2.png)
+    ![Screenshot of select delete](media/azure-stack-edge-gpu-manage-shares/delete-share-2.png)
 
-3. When prompted for confirmation, click **Yes**.
+3. When prompted for confirmation, select **Yes**.
 
     ![Confirm delete](media/azure-stack-edge-gpu-manage-shares/delete-share-3.png)
 
@@ -158,29 +158,29 @@ The refresh feature allows you to refresh the contents of a share. When you refr
 
 > [!IMPORTANT]
 > - You can't refresh local shares.
-> - Permissions and access control lists (ACLs) are not preserved across a refresh operation. 
+> - Permissions and access control lists (ACLs) aren't preserved across a refresh operation. 
 
 Do the following steps in the Azure portal to refresh a share.
 
 1.  In the Azure portal, go to **Shares**. Select and click the share that you want to refresh.
 
     ![Select share 4](media/azure-stack-edge-gpu-manage-shares/refresh-share-1.png)
 
-2.  Click **Refresh**. 
+2.  Select **Refresh**. 
 
-    ![Click refresh](media/azure-stack-edge-gpu-manage-shares/refresh-share-2.png)
+    ![Screenshot of select refresh](media/azure-stack-edge-gpu-manage-shares/refresh-share-2.png)
 
-3.  When prompted for confirmation, click **Yes**. A job starts to refresh the contents of the on-premises share.
+3.  When prompted for confirmation, select **Yes**. A job starts to refresh the contents of the on-premises share.
 
     ![Confirm refresh](media/azure-stack-edge-gpu-manage-shares/refresh-share-3.png)
 
-4.   While the refresh is in progress, the refresh option is grayed out in the context menu. Click the job notification to view the refresh job status.
+4.   While the refresh is in progress, the refresh option is grayed out in the context menu. Select the job notification to view the refresh job status.
 
-5.   The time to refresh depends on the number of files in the Azure container as well as the files on the device. Once the refresh has successfully completed, the share timestamp is updated. Even if the refresh has partial failures, the operation is considered successful and the timestamp is updated. The refresh error logs are also updated.
+5.   The time to refresh depends on the number of files in the Azure container and the files on the device. Once the refresh has successfully completed, the share timestamp is updated. Even if the refresh has partial failures, the operation is considered successful and the timestamp is updated. The refresh error logs are also updated.
 
 ![Updated timestamp](media/azure-stack-edge-gpu-manage-shares/refresh-share-4.png)
 
-If there is a failure, an alert is raised. The alert details the cause and the recommendation to fix the issue. The alert also links to a file that has the complete summary of the failures including the files that failed to update or delete.
+If there's a failure, an alert is raised. The alert details the cause and the recommendation to fix the issue. The alert also links to a file that has the complete summary of the failures including the files that failed to update or delete.
 
 ## Sync pinned files 
 
@@ -203,7 +203,7 @@ To automatically sync up pinned files, do the following steps in the Azure porta
 
     ![Automated sync for pinned files 3](media/azure-stack-edge-gpu-manage-shares/image-3.png)
 
-5. From the Azure portal, browse to the container which you created. Upload the file which you want to be pinned into the newcontainer which has the metadata set to pinned. 
+5. From the Azure portal, browse to the container that you created. Upload the file that you want to be pinned into the new container, that has the metadata set to pinned. 
 
 6. Select **Refresh data** in Azure portal for the device to download the pinning policy for that particular Azure Storage container.  
 
@@ -220,11 +220,11 @@ If your storage account keys have been rotated, then you need to sync the storag
 
 Do the following steps in the Azure portal to sync your storage access key.
 
-1. Go to **Overview** in your resource. From the list of shares, choose and click a share associated with the storage account that you need to sync.
+1. Go to **Overview** in your resource. From the list of shares, select a share associated with the storage account that you need to sync.
 
     ![Select share with relevant storage account](media/azure-stack-edge-gpu-manage-shares/sync-storage-key-1.png)
 
-2. Click **Sync storage key**. Click **Yes** when prompted for confirmation.
+2. Select **Sync storage key**. Select **Yes** when prompted for confirmation.
 
      ![Select Sync storage key](media/azure-stack-edge-gpu-manage-shares/sync-storage-key-2.png)