Merge pull request #267996 from normesta/normesta-reg-updates-13

Fixing high-throughput block blob limits in an include file

Author: v-shils

includes/storage-blob-scale-targets.md

@@ -20,7 +20,7 @@ ms.author: tamram
 | Target throughput for a single page blob | Up to 60 MiB per second<sup>2</sup> |
 | Target throughput for a single block blob | Up to storage account ingress/egress limits<sup>1</sup> |
 
-<sup>1</sup> Throughput for a single blob depends on several factors. These factors include but aren't limited to: concurrency, request size, performance tier, speed of source for uploads, and destination for downloads. To take advantage of the performance enhancements of [high-throughput block blobs](https://azure.microsoft.com/blog/high-throughput-with-azure-blob-storage/), upload larger blobs or blocks. Specifically, call the [Put Blob](/rest/api/storageservices/put-blob) or [Put Block](/rest/api/storageservices/put-block) operation with a blob or block size that is greater than 4 MiB for standard storage accounts. For premium block blob or for Data Lake Storage Gen2 storage accounts, use a block or blob size that is greater than 256 KiB.
+<sup>1</sup> Throughput for a single blob depends on several factors. These factors include but aren't limited to: concurrency, request size, performance tier, speed of source for uploads, and destination for downloads. To take advantage of the performance enhancements of [high-throughput block blobs](https://azure.microsoft.com/blog/high-throughput-with-azure-blob-storage/), upload larger blobs or blocks. Specifically, call the [Put Blob](/rest/api/storageservices/put-blob) or [Put Block](/rest/api/storageservices/put-block) operation with a blob or block size that is greater than 256 KiB.
 
 <sup>2</sup> Page blobs aren't yet supported in accounts that have a hierarchical namespace enabled.