Update workload-guidelines-best-practices-storage.md

Author: Padmalathas

articles/virtual-machines/workload-guidelines-best-practices-storage.md

@@ -23,7 +23,7 @@ Storage for HPC workloads consists of core storage and in some cases, an acceler
 
 Core storage acts as the permanent home for your data. It contains rich data management features and is durable, available, scalable, elastic, and secure. An accelerator enhances core storage by providing high-performance data access. An accelerator can be provisioned on demand and gives your computational workload much faster access to data.
 
-:::image type="content" source="media/hpc/core-accelarator-model-for-hpc-storage.png" alt-text="Diagram depicting storage options for HPC workloads." lightbox="media/hpc/core-accelarator-model-for-hpc-storage.png":::
+<!--- :::image type="content" source="media/hpc/core-accelarator-model-for-hpc-storage.png" alt-text="Diagram depicting storage options for HPC workloads." lightbox="media/hpc/core-accelarator-model-for-hpc-storage.png"::: --->
 
 ## Initial consideration
 
@@ -34,13 +34,13 @@ If you are starting from scratch, see [Understand data store models](/azure/arch
 Start with the amount of data that you plan to store. Then, consider the size of your files and number of CPU cores used by your workload. These factors help you to narrow down which core storage service best suits your workload and whether to use an accelerator to enhance performance.
 
 
-|Configuration  |CPU cores  |Sizes of files  |Core Storage Recommendation  |Accelarator Reccomendation  |
+|Configuration  |CPU cores  |Sizes of files  |Core Storage Recommendation  |Accelerator Reccomendation  |
 |---------|---------|---------|---------|---------|
-|Under 50 TiB     |N/A |N/A        | [Azure Files](/azure/storage/files/) or [Azure NetApp Files](/azure/azure-netapp-files/).        |No Accelarator  |
-|50 TiB - 5,000 TiB |Less than 500 |N/A|[Azure Files](/azure/storage/files/) or [Azure NetApp Files](/azure/azure-netapp-files/).        |No Accelarator  |
-|50 TiB - 5,000 TiB |Over 500      |1 MiB and larger| [Azure Standard Blob](/azure/storage/blobs/). | [Azure Managed Lustre](/azure/azure-managed-lustre/).    |
+|Under 50 TiB     |N/A |N/A        | [Azure Files](/azure/storage/files/) or [Azure NetApp Files](/azure/azure-netapp-files/).        |No accelerator  |
+|50 TiB - 5,000 TiB |Less than 500 |N/A|[Azure Files](/azure/storage/files/) or [Azure NetApp Files](/azure/azure-netapp-files/).        |No accelerator  |
+|50 TiB - 5,000 TiB |Over 500      |1 MiB and larger| [Azure Standard Blob](/azure/storage/blobs/). It’s supported by all accelerators, supports many protocols, and is cost-effective. | [Azure Managed Lustre](/azure/azure-managed-lustre/).    |
 |50 TiB - 5,000 TiB |Over 500      |Smaller than 1 MiB| Azure Premium Blob](/azure/storage/blobs/storage-blob-block-blob-premium) or [Azure Standard Blob](/azure/storage/blobs/). | [Azure Managed Lustre](/azure/azure-managed-lustre/).     |
-|50 TiB - 5,000 TiB |Over 500      |Smaller than 512 kiB| [Azure NetApp Files](/azure/azure-netapp-files/).    |No Accelarator  |
+|50 TiB - 5,000 TiB |Over 500      |Smaller than 512 KiB| [Azure NetApp Files](/azure/azure-netapp-files/).    |No accelerator  |
 |Over 5,000 TiB |N/A      |N/A|    |Talk to your field or account team.   |
 <!---|     |[Use ZRS disks when sharing disks between VMs](#use-zrs-disks-when-sharing-disks-between-vms).         |Prevents a shared disk from becoming a single point of failure.         | --->
 
@@ -50,22 +50,17 @@ If you are still stuck between options after using the decision trees, here are
 
 |Solution |Optimal Performance & Scale |Data Access (Access Protocol) |Billing Model |Core Storage or Accelerator |
 |---|---|---|---|---|
-| [**Azure Standard Blob**](/azure/storage/blobs/) | Large file, bandwidth intensive workloads | Good for traditional (file) and cloud-native (REST) HPC appsEasy to access, share, manage datasetsWorks with all accelerators | Pay for what you use | Core Storage |
-| [**Azure Premium Blob**](/azure/storage/blobs/storage-blob-block-blob-premium) | Data sets with many medium-sized files and mixed file sizes | Good for traditional (file) and cloud-native (REST) HPC appsEasy to access, share, manage datasetsWorks with all accelerators | Pay for what you use | Core Storage |
-| [**Azure Premium Files**](/azure/storage/files/) | Smaller scale (<1k cores), IOPS/latency good for medium sized files (>512 KiB) | Easy integration with Linux (NFS) and Windows (SMB), but can't use both NFS+SMB to access the same data | Pay for what you provision | Core Storage |
-| [**Azure NetApp Files**](/azure/azure-netapp-files/) | Midrange jobs (1k-10k cores), IOPS+latency good for small-file datasets (<512 KiB), excellent for small, many-file workloads | Easy to integrate for Linux and Windows, supports multiprotocol for workflows using both Linux + Windows | Pay what you provision | Either |
-| [**Azure Managed Lustre**](/azure/azure-managed-lustre/) | All job sizes (1k - >10k cores) IOPS/latency for 1000s of medium-sized files (>512 KiB), best for bandwidth-intensive read + write workloads | Lustre, CSI | Pay for what you provision | Durable enough to run as standalone (core) storage, most cost-effective as an accelerator |
+| [**Azure Standard Blob**](/azure/storage/blobs/) | Large file, bandwidth intensive workloads. | Good for traditional (file) and cloud-native (REST) HPC apps. Easy to access, share, manage datasets. Works with all accelerators. | Pay for what you use. | Core Storage. |
+| [**Azure Premium Blob**](/azure/storage/blobs/storage-blob-block-blob-premium) | Data sets with many medium-sized files and mixed file sizes | Good for traditional (file) and cloud-native (REST) HPC apps. Easy to access, share, manage datasets. Works with all accelerators. | Pay for what you use. | Core Storage. |
+| [**Azure Premium Files**](/azure/storage/files/) | Smaller scale (<1k cores), IOPS/latency good for medium sized files (>512 KiB). | Easy integration with Linux (NFS) and Windows (SMB), but can't use both NFS+SMB to access the same data | Pay for what you provision. | Core Storage. |
+| [**Azure NetApp Files**](/azure/azure-netapp-files/) | Midrange jobs (1k-10k cores), IOPS+latency good for small-file datasets (<512 KiB), excellent for small, many-file workloads | Easy to integrate for Linux and Windows, supports multiprotocol for workflows using both Linux + Windows. | Pay what you provision. | Either. |
+| [**Azure Managed Lustre**](/azure/azure-managed-lustre/) | All job sizes (1k - >10k cores) IOPS/latency for 1000s of medium-sized files (>512 KiB), best for bandwidth-intensive read + write workloads. | Lustre, CSI | Pay for what you provision. | Durable enough to run as standalone (core) storage, most cost-effective as an accelerator. |
 
 ## Core storage price comparison
 
-In order of most to least expensive, the core storage option prices are: Azure NetApp Files > Azure Premium Blob and Azure Premium Files > Azure Standard Blob.
+In order of most to least expensive, the core storage option prices are: 
+- Azure NetApp Files
+- Azure Premium Blob and Azure Premium Files
+- Azure Standard Blob
 
-## Next steps
-
-To learn more, see the other articles in this best practices series:
-
-- [Cloud storage on Azure](/azure/storage/common/storage-introduction/)
-- [Azure Storage](/azure/storage/files/)
-- [Azure NetApp files](/azure/azure-netapp-files/)
-- [Azure Blob Storage](/azure/storage/blobs/)
-- [Azure Managed Lustre](/azure/azure-managed-lustre/)
+For more info on the pricing, see [Azure product pricing](https://azure.microsoft.com/en-us/pricing/#product-pricing).