Final this time

Author: normesta

articles/storage/blobs/cost-estimate-archive-retrieval.md

@@ -19,20 +19,23 @@ This sample estimates the cost to retrieve a portion of data from the archive ti
 
 ## Scenario
 
-Your company has an account that is located in the West US region, is configured for locally-redundant storage (LRS), and does not have hierarchical namespaces. The company has stored 20 TB of data in the archive tier for long term retention. However, after only 3 months in archive storage, 20% of that data must be retrieved for analysis. You've been asked to estimate what it will cost to get that data from archive storage and then download that data to clients for analysis. 
+Your company stores 20 TB of data in the archive tier for long term retention. However, after only three months in archive storage, 20% of that data must be retrieved for analysis. You've been asked to estimate what it will cost to get that data from archive storage and then download that data to clients for analysis. 
+
+The storage account is located in the West US region, is configured for locally-redundant storage (LRS), and does not have hierarchical namespaces.
 
 ## Costs
 
-The following table describes each cost that is applied in this scenario.
+The following table describes each cost.
 
-| Cost component | Explanation |
+| Cost | Description |
 |----|----|
-| **Change tier to hot** | First, blobs must be moved out of archive storage for analysis.To do this, administrators will change the tier of each blob from `archive` to `hot`. All tools and SDKs use the [Set Blob Tier](/rest/api/storageservices/set-blob-tier) operation on each blob to accomplish this task. That operation is billed as a read operation on the archive tier. |
+| **Change tier to hot** | First, blobs must be moved out of archive storage for analysis. To do this, administrators will change the tier of each blob from `archive` to `hot`. All tools and SDKs use the [Set Blob Tier](/rest/api/storageservices/set-blob-tier) operation to accomplish this task. That operation is billed as a read operation on the archive tier. |
 | **Data retrieval fee** | This meter applies to each GB moved from the archive tier and into an online tier such as the hot tier. |
 | **Early deletion fee** | If data is moved out of the archive tier before 180 days have transpired, a prorated early deletion fee is applied to the bill. |
-| **Read from the hot tier** | Once data is moved into the hot tier, clients will need to read that data. Each blob read is billed as a read operation on the hot tier. |
+| **Read from the hot tier** | Once data is moved into the hot tier, clients will need to download that data. Each download is billed as a read operation. |
 
-Rehydration time at standard priority can take up to 15 hours to complete.
+> [!NOTE] 
+> Rehydration time at standard priority can take up to 15 hours to complete.
 
 ## Estimate
 

articles/storage/blobs/cost-estimate-multi-region-access.md

@@ -19,17 +19,19 @@ This sample estimates the cost to upload and download data from multiple Azure r
 
 ## Scenario
 
-Your company has a storage account that is located in the West US region, is configured for Geo-redundant storage (GRS) and does not have hierarchical namespaces enabled. This year, a new client application is being distributed to users located in multiple Azure regions across the continent. Users are distributed across the continent and will upload log files and download them for diagnostic analysis. Files are stored as blobs in the hot access tier. Based on expected usage patterns, you've been asked to create a rough estimate of costs.
+Your company plans to distribute a new client application to users located in multiple Azure regions across the continent. This application will be used to upload log files and download them for diagnostic analysis. Files are stored as blobs in the hot access tier. Based on expected usage patterns, you've been asked to create a rough estimate of costs.
+
+The storage account is located in the West US region, is configured for Geo-redundant storage (GRS) and does not have hierarchical namespaces enabled. 
 
 ## Costs
 
-The clients will generate and upload an estimated **50,000** log files (roughly 1 GB each in size) this quarter. During this time, your company estimates that client applications will download about half of those log files for diagnostic analysis. You've been asked to create an estimate.
+The following table describes each cost.
 
-| Cost component | Explanation |
+| Cost | Description |
 |----|----|
-| **Cost to write** | Based on your estimates for this quarter, clients will upload an estimated **50,000** log files (roughly **1 GB** each in size). Clients are configured to upload those log files in 8 MiB blocks. Each block uploaded is billed as a write operation on the hot tier. A final operation is used by the clients to commit those blocks. That operation is also billed as a write operation. A smaller block size is very performant, but you know that a larger block size results in fewer write operations so you plan to include that suggestion along with your estimate. |
-| **Cost of replication** | Because the account is configured for Geo-redundant storage, all blobs uploaded are replicated to a secondary region. This replication process adds a data transfer fee and a network bandwidth fee. This fee is charged per GB.|
-| **Cost to read** | Any blob that is downloaded for diagnostic analysis is billed as a read operation on the hot tier. You believe that client applications will download about half of the files uploaded for diagnostic analysis. You also learn that **75%** of client applications are not located in the same region as the storage account so downloads from those clients incur a data transfer fee and a network bandwidth fee. |
+| **Cost to write** | During this quarter, clients will upload an estimated **50,000** log files (roughly **1 GB** each in size). Clients are configured to upload those log files in 8 MiB blocks. Each block  is billed as a write operation with one additional operation to commit those blocks. A smaller block size is very performant, but you know that a larger block size results in fewer write operations so you plan to include that suggestion along with your estimate. |
+| **Cost of replication** | Because the account is configured for geo-redundant storage, all blobs are replicated to a secondary region. This replication process adds a data transfer fee and a network bandwidth fee. These fees are charged per GB.|
+| **Cost to read** | Any blob that is downloaded for diagnostic analysis is billed as a read operation. You believe that client applications will download about half of the files uploaded for diagnostic analysis. You also learn that **75%** of client applications are not located in the same region as the storage account. Therefore, blobs downloaded by those clients incur a data transfer fee and a network bandwidth fee. |
 
 ## Estimate