Merge pull request #282291 from saurabh0501/patch-3

Update use-container-storage-with-elastic-san.md

Author: prmerger-automator[bot]

articles/storage/container-storage/use-container-storage-with-elastic-san.md

@@ -9,9 +9,9 @@ ms.author: kendownie
 ms.custom: references_regions
 ---
 
-# Use Azure Container Storage with Azure Elastic SAN
+# Use Azure Container Storage with Azure Elastic SAN (Preview)
 
-[Azure Container Storage](container-storage-introduction.md) is a cloud-based volume management, deployment, and orchestration service built natively for containers. This article shows you how to configure Azure Container Storage to use Azure Elastic SAN as back-end storage for your Kubernetes workloads. At the end, you'll have a pod that's using Elastic SAN as its storage.
+[Azure Container Storage](container-storage-introduction.md) is a cloud-based volume management, deployment, and orchestration service built natively for containers. This article shows you how to configure Azure Container Storage to use Azure Elastic SAN (Preview) as back-end storage for your Kubernetes workloads. At the end, you'll have a pod that's using Elastic SAN as its storage.
 
 ## Prerequisites
 
@@ -20,7 +20,7 @@ ms.custom: references_regions
 - Ensure you have either an [Azure Container Storage Owner](../../role-based-access-control/built-in-roles/containers.md#azure-container-storage-owner) role or [Azure Container Storage Contributor](../../role-based-access-control/built-in-roles/containers.md#azure-container-storage-contributor) role on your subscription. Either of these roles will grant permissions that allow Azure Container Storage to communicate with the Elastic SAN resource. To make this change, go to your subscription page on the Azure portal. Select **Access control (IAM) > Add role assignment** and search for either "Azure Container Storage Owner" or "Azure Container Storage Contributor" in the **Job function roles** tab. Select **View > Assignments > Add assignment** and add your account.
 
 > [!NOTE]
-> To use Azure Container Storage with Azure Elastic SAN, your AKS cluster should have a node pool of at least three [general purpose VMs](../../virtual-machines/sizes-general.md) such as **standard_d4s_v5** for the cluster nodes, each with a minimum of four virtual CPUs (vCPUs).
+> To use Azure Container Storage with Azure Elastic SAN (Preview), your AKS cluster should have a node pool of at least three [general purpose VMs](../../virtual-machines/sizes-general.md) such as **standard_d4s_v5** for the cluster nodes, each with a minimum of four virtual CPUs (vCPUs).
 
 ## Limitations
 
@@ -43,7 +43,7 @@ First, create a storage pool, which is a logical grouping of storage for your Ku
 
 If you enabled Azure Container Storage using `az aks create` or `az aks update` commands, you might already have a storage pool. Use `kubectl get sp -n acstor` to get the list of storage pools. If you have a storage pool already available that you want to use, you can skip this section and proceed to [Display the available storage classes](#2-display-the-available-storage-classes).
 
-Follow these steps to create a storage pool with Azure Elastic SAN.
+Follow these steps to create a storage pool with Azure Elastic SAN (Preview).
 
 1. Use your favorite text editor to create a YAML manifest file such as `code acstor-storagepool.yaml`.