Merge pull request #78940 from twooley/twblockblobfix

updating block blob info

Author: PRMerger9

articles/storage/common/storage-account-overview.md

@@ -6,7 +6,7 @@ author: tamram
 
 ms.service: storage
 ms.topic: article
-ms.date: 05/06/2019
+ms.date: 06/07/2019
 ms.author: tamram
 ms.subservice: common
 ---
@@ -58,7 +58,11 @@ While general-purpose v2 accounts are recommended in most cases, general-purpose
 
 ### Block blob storage accounts
 
-A block blob storage account is a specialized storage account for storing unstructured object data as block blobs or append blobs. Block blob storage accounts offer multiple access tiers for storing data based on your usage patterns. For more information, see [Access tiers for block blob data](#access-tiers-for-block-blob-data).
+A block blob storage account is a specialized storage account for storing unstructured object data as block blobs. This storage account type supports block blobs and append blobs, but not page blobs, tables or queues.
+
+Compared with general-purpose v2 and blob storage accounts, block blob storage accounts provide low and consistent latency, and higher transaction rates.
+
+Block blob storage accounts do not currently support tiering to hot, cool, or archive access tiers.
 
 ### FileStorage (preview) storage accounts
 
@@ -71,22 +75,26 @@ When naming your storage account, keep these rules in mind:
 - Storage account names must be between 3 and 24 characters in length and may contain numbers and lowercase letters only.
 - Your storage account name must be unique within Azure. No two storage accounts can have the same name.
 
-## General-purpose performance tiers
+## Performance tiers
 
 General-purpose storage accounts may be configured for either of the following performance tiers:
 
 * A standard performance tier for storing blobs, files, tables, queues, and Azure virtual machine disks.
 * A premium performance tier for storing unmanaged virtual machine disks only.
 
+Block blob storage accounts provide a premium performance tier for storing block blobs and append blobs.
+
+FileStorage (preview) storage accounts provide a premium performance tier for Azure file shares.
+
 ## Access tiers for block blob data
 
 Azure Storage provides different options for accessing block blob data based on usage patterns. Each access tier in Azure Storage is optimized for a particular pattern of data usage. By selecting the right access tier for your needs, you can store your block blob data in the most cost-effective manner.
 
 The available access tiers are:
 
-* The **Hot** access tier, which is optimized for frequent access of objects in the storage account. Accessing data in the Hot tier is most cost-effective, while storage costs are higher. New storage accounts are created in the Hot tier by default.
-* The **Cool** access tier, which is optimized for storing large amounts of data that is infrequently accessed and stored for at least 30 days. Storing data in the Cool tier is more cost-effective, but accessing that data may be more expensive than accessing data in the Hot tier.
-* The **Archive** tier, which is available only for individual block blobs. The Archive tier is optimized for data that can tolerate several hours of retrieval latency and will remain in the Archive tier for at least 180 days. The Archive tier is the most cost-effective option for storing data, but accessing that data is more expensive than accessing data in the Hot or Cool tiers.
+* The **Hot** access tier, which is optimized for frequent access of objects in the storage account. Accessing data in the hot tier is most cost-effective, while storage costs are higher. New storage accounts are created in the hot tier by default.
+* The **Cool** access tier, which is optimized for storing large amounts of data that is infrequently accessed and stored for at least 30 days. Storing data in the cool tier is more cost-effective, but accessing that data may be more expensive than accessing data in the hot tier.
+* The **Archive** tier, which is available only for individual block blobs. The archive tier is optimized for data that can tolerate several hours of retrieval latency and will remain in the Archive tier for at least 180 days. The archive tier is the most cost-effective option for storing data, but accessing that data is more expensive than accessing data in the hot or cool tiers.
 
 If there is a change in the usage pattern of your data, you can switch between these access tiers at any time. For more information about access tiers, see [Azure Blob storage: hot, cool, and archive access tiers](../blobs/storage-blob-storage-tiers.md).
 
@@ -115,7 +123,7 @@ For example, if your general-purpose storage account is named *mystorageaccount*
 * Azure Files: http://*mystorageaccount*.file.core.windows.net
 
 > [!NOTE]
-> A Blob storage account exposes only the Blob service endpoint.
+> Block blob and blob storage accounts expose only the blob service endpoint.
 
 The URL for accessing an object in a storage account is constructed by appending the object's location in the storage account to the endpoint. For example, a blob address might have this format: http://*mystorageaccount*.blob.core.windows.net/*mycontainer*/*myblob*.
 
@@ -173,5 +181,6 @@ The Import/Export service can also be used to transfer data from Azure Blob stor
 
 ## Next steps
 
-* To learn how to create an Azure storage account, see [Create a storage account](storage-quickstart-create-account.md).
+* To learn how to create a general-purpose Azure storage account, see [Create a storage account](storage-quickstart-create-account.md).
+* To learn how to create a block blob storage account, see [Create a block blob storage account](../blobs/storage-blob-create-account-block-blob.md).
 * To manage or delete an existing storage account, see [Manage Azure storage accounts](storage-account-manage.md).