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

Author: Padmalathas

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

@@ -50,11 +50,11 @@ 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 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. |
+| [**Azure Standard Blob**](/azure/storage/blobs/) | Good for 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) | IOPS and latency better than Standard Blob. Good for datasets 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/) | Capacity and bandwidth suited for smaller scale (<1k cores). IOPS and 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/) | Capacity and bandwidth good for midrange jobs (1k-10k cores). IOPS and 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/) | Bandwidth to support all job sizes (1k - >10k cores). IOPS and latency good for thousands of medium-sized files (>512 KiB). Best for bandwidth-intensive read and 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