Fixing some blocking issues

normesta · normesta · commit 1431835951c1 · 2024-09-10T16:44:56.000-07:00
diff --git a/articles/storage/blobs/TOC.yml b/articles/storage/blobs/TOC.yml
@@ -136,7 +136,7 @@ items:
       - name: Troubleshoot AzCopy issues
         href: /troubleshoot/azure/azure-storage/storage-use-azcopy-troubleshoot?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json
       - name: Map of AzCopy commands to REST operations
-        href: ../common/storage-ref-azcopy-map-commands-to-rest-operations.md?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json
+        href: ../common/storage-reference-azcopy-map-commands-to-rest-operations.md?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json
     - name: Azure Data Factory
       href: ../../data-factory/connector-azure-blob-storage.md?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json
       items:
@@ -486,7 +486,7 @@ items:
         href: storage-blob-scalable-app-create-vm.md
       - name: 2 - Upload large data to an Azure storage account
         href: storage-blob-scalable-app-upload-files.md
-      - name: 3- Download large data from an Azure storage account
+      - name: 3 - Download large data from an Azure storage account
         href: storage-blob-scalable-app-download-files.md
       - name: 4 - Verify throughput and latency metrics
         href: storage-blob-scalable-app-verify-metrics.md
diff --git a/articles/storage/blobs/azcopy-cost-estimation.md b/articles/storage/blobs/azcopy-cost-estimation.md
@@ -127,7 +127,7 @@ The following table calculates the number of write operations required to upload
 |-------------------------------------------------------------|---------------|
 | Number of MiB in 5 GiB                                      | 5,120         |
 | Path - Update operations per blob (5,120 MiB / 4-MiB block) | 1,280         |
-| Total read operations (1000* 1,280)                         | **1,280,000** |
+| Total read operations (1000 * 1,280)                         | **1,280,000** |
 
 Using the [Sample prices](#sample-prices) that appear in this article, the following table calculates the cost to download these blobs.
 
@@ -235,6 +235,6 @@ The following table contains all of the estimates presented in this article. All
 ## See also
 
 - [Plan and manage costs for Azure Blob Storage](../common/storage-plan-manage-costs.md)
-- [Map each AzCopy command to a REST operation](../common/storage-ref-azcopy-map-commands-to-rest-operations.md?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json)
+- [Map each AzCopy command to a REST operation](../common/storage-reference-azcopy-map-commands-to-rest-operations.md?toc=/azure/storage/blobs/toc.json&bc=/azure/storage/blobs/breadcrumb/toc.json)
 - [Map each REST operation to a price](map-rest-apis-transaction-categories.md)
 - [Get started with AzCopy](../common/storage-use-azcopy-v10.md)
diff --git a/articles/storage/blobs/blob-storage-estimate-costs.md b/articles/storage/blobs/blob-storage-estimate-costs.md
@@ -17,7 +17,7 @@ This article helps you estimate the cost to store, upload, download, and work wi
 All calculations are based on a fictitious price. You can find each price in the [sample prices](#sample-prices) section at the end of this article. 
 
 > [!IMPORTANT]
-> These prices are meant only as examples, and shouldn't be used to calculate your costs. For official prices, see the [Azure Blob Storage pricing](https://azure.microsoft.com/pricing/details/storage/blobs/) or [Azure Data Lake Storage pricing](https://azure.microsoft.com/pricing/details/storage/data-lake/) pricing pages. For more information about how to choose the correct pricing page, see [Understand the full billing model for Azure Blob Storage](../common/storage-plan-manage-costs.md).
+> These prices are meant only as examples, and shouldn't be used to calculate your costs. For official prices, see the [Azure Blob Storage pricing](https://azure.microsoft.com/pricing/details/storage/blobs/) or [Azure Data Lake Storage pricing](https://azure.microsoft.com/pricing/details/storage/data-lake/) pages. For more information about how to choose the correct pricing page, see [Understand the full billing model for Azure Blob Storage](../common/storage-plan-manage-costs.md).
 
 ## The cost to store data
 
@@ -65,7 +65,7 @@ Using the [Sample prices](#sample-prices) that appear in this article, and assum
 | Number of MiB in 5 GiB                                   | 5,120          |
 | Write operations per blob (5,120 MiB / 8-MiB block)      | 640            |
 | Write operation to commit the blocks                     | 1              |
-| Total write operations (1,000 * 641)**                   | 641,000        |
+| **Total write operations (1,000 * 641)**                   | 641,000        |
 | Price of a single write operation (price / 10,000)       | $0.0000055     |
 | **Cost of write operations (641,000 * operation price)** | **$3.5255**    |
 | **Total cost (write + properties)**                      | **$3.5250055** |
diff --git a/articles/storage/common/storage-plan-manage-costs.md b/articles/storage/common/storage-plan-manage-costs.md
@@ -51,7 +51,7 @@ At the end of your billing cycle, the charges for each meter are summed. Your bi
 
 #### Data storage and index meters
 
-Data storage and metadata are billed per GB on a monthly basis. Most metadata is stored as part of the blob and includes properties and key-value pairs. The metadata that is associated with blobs in the archive tier is stored separately in the cold tier. That way, users can list the blob and its properties, metadata, and index tags. Because the size of metadata doesn't exceed 8 KB in size, it's cost is relatively insignificant as a percent of total storage capacity. 
+Data storage and metadata are billed per GB on a monthly basis. Most metadata is stored as part of the blob and includes properties and key-value pairs. The metadata that is associated with blobs in the archive tier is stored separately in the cold tier. That way, users can list the blob and its properties, metadata, and index tags. Because the size of metadata doesn't exceed 8 KB in size, its cost is relatively insignificant as a percent of total storage capacity. 
 
 Blob index tags are stored as a sub resource in the hot tier, and have their own billing meter. The **Index** meter applies only to accounts that have a hierarchical namespace as a means to bill for the space required to facilitate a hierarchical file structure including the access control lists (ACLs) associated with objects in that structure. Data associated with the index is always stored in the hot tier.
 
@@ -72,7 +72,7 @@ For more information about how to calculate the cost of storage, see [The cost t
 
 Each request made by a client arrives to the service in the form of a REST operation. You can monitor your resource logs to see which operations are executing against your data. 
 
-The pricing pages don't list a price for each individual operation but instead lists the price of an operation _type_. To determine the price of an operation, you must first determine how that operation is classified in terms of it's type. To trace a _logged operation_ to a _REST operation_ and then to an operation _type_, see [Map each REST operation to a price](../blobs/map-rest-apis-transaction-categories.md). 
+The pricing pages don't list a price for each individual operation but instead lists the price of an operation _type_. To determine the price of an operation, you must first determine how that operation is classified in terms of its type. To trace a _logged operation_ to a _REST operation_ and then to an operation _type_, see [Map each REST operation to a price](../blobs/map-rest-apis-transaction-categories.md). 
 
 The price that appears beside an operation type isn't the price you pay for each operation. In most cases, it's the price of `10,000` operations. To obtain the price of an individual operation, divide the price by `10,000`. For example, if the price for write operations is `$0.055`, then the price of an individual operation is `$.0555` / `10,000` = `$0.0000055`. You can estimate the cost to upload a file by multiplying the number write operations required to complete the upload by the cost of an individual transaction. To learn more, see [Estimate the cost of using Azure Blob Storage](../blobs/blob-storage-estimate-costs.md).
 
@@ -138,7 +138,7 @@ Use the [Azure pricing calculator](https://azure.microsoft.com/pricing/calculato
 
    As you modify the value of these drop-down lists, the cost estimate changes. That estimate appears in the upper corner as well as the bottom of the estimate.
 
-   ![Screenshot showing your estimate](media/storage-plan-manage-costs/price-calculator-storage-type.png)
+   ![Screenshot showing your estimate.](media/storage-plan-manage-costs/price-calculator-storage-type.png)
 
    As you change the value of the **Type** drop-down list, other options that appear on this worksheet change as well. Use the links in the **More Info** section to learn more about what each option means and how these options affect the price of storage-related operations.
 
@@ -171,7 +171,7 @@ You can also reduce costs by placing blob data into the most cost effective acce
 - [Best practices for using blob access tiers](../blobs/access-tiers-best-practices.md)
 - [Estimate the cost of archiving data](../blobs/archive-cost-estimation.md)
 
-Use lifecycle management policies to periodically move data between tiers to save the most money. These policies can move data to by using rules that you specify. For example, you might create a rule that moves blobs to the archive tier if that blob hasn't been modified in 90 days. By creating policies that adjust the access tier of your data, you can design the least expensive storage options for your needs. To learn more, see [Manage the Azure Blob Storage lifecycle](../blobs/lifecycle-management-overview.md?tabs=azure-portal)
+Use lifecycle management policies to periodically move data between tiers to save the most money. These policies can move data to by using rules that you specify. For example, you might create a rule that moves blobs to the archive tier if that blob hasn't been modified in 90 days. By creating policies that adjust the access tier of your data, you can design the least expensive storage options for your needs. To learn more, see [Manage the Azure Blob Storage lifecycle](../blobs/lifecycle-management-overview.md?tabs=azure-portal).
 
 ## Create budgets
 
@@ -230,7 +230,7 @@ See [Managing costs FAQ](../blobs/storage-blob-faq.yml#managing-costs).
 - Learn more on how pricing works with Azure Storage. See [Azure Storage Overview pricing](https://azure.microsoft.com/pricing/details/storage/).
 - Understanding how your blobs and containers are stored, organized, and used in production so that you better optimize the tradeoffs between cost and performance. See [Tutorial: Analyze blob inventory reports](../blobs/storage-blob-inventory-report-analytics.md).
 - [Optimize costs for Blob Storage with reserved capacity](../blobs/storage-blob-reserved-capacity.md).
-- Learn [how to optimize your cloud investment with Azure Cost Management](../../cost-management-billing/costs/cost-mgt-best-practices.md?WT.mc_id=costmanagementcontent_docsacmhorizontal_-inproduct-learn).
+- Learn [how to optimize your cloud investment with Microsoft Cost Management](../../cost-management-billing/costs/cost-mgt-best-practices.md?WT.mc_id=costmanagementcontent_docsacmhorizontal_-inproduct-learn).
 - Learn more about managing costs with [cost analysis](../../cost-management-billing/costs/quick-acm-cost-analysis.md?WT.mc_id=costmanagementcontent_docsacmhorizontal_-inproduct-learn).
 - Learn about how to [prevent unexpected costs](../../cost-management-billing/cost-management-billing-overview.md?WT.mc_id=costmanagementcontent_docsacmhorizontal_-inproduct-learn).
 - Take the [Cost Management](/training/paths/control-spending-manage-bills?WT.mc_id=costmanagementcontent_docsacmhorizontal_-inproduct-learn) guided learning course.
diff --git a/articles/storage/common/storage-reference-azcopy-map-commands-to-rest-operations.md b/articles/storage/common/storage-reference-azcopy-map-commands-to-rest-operations.md
diff --git a/includes/azure-blob-storage-sample-prices.md b/includes/azure-blob-storage-sample-prices.md
@@ -9,7 +9,7 @@
 The following table includes sample (fictitious) prices for each request to the Blob Service endpoint (`blob.core.windows.net`). 
 
 > [!IMPORTANT]
-> These prices are meant only as examples, and shouldn't be used to calculate your costs. For official prices, see the [Azure Blob Storage pricing](https://azure.microsoft.com/pricing/details/storage/blobs/) or [Azure Data Lake Storage pricing](https://azure.microsoft.com/pricing/details/storage/data-lake/) pricing pages. For more information about how to choose the correct pricing page, see [Understand the full billing model for Azure Blob Storage](../articles/storage/common/storage-plan-manage-costs.md).
+> These prices are meant only as examples, and shouldn't be used to calculate your costs. For official prices, see the [Azure Blob Storage pricing](https://azure.microsoft.com/pricing/details/storage/blobs/) or [Azure Data Lake Storage pricing](https://azure.microsoft.com/pricing/details/storage/data-lake/) pages. For more information about how to choose the correct pricing page, see [Understand the full billing model for Azure Blob Storage](../articles/storage/common/storage-plan-manage-costs.md).
 
 | Price factor                                                    | Hot            | Cool           | Cold           | Archive |
 |-----------------------------------------------------------------|----------------|----------------|----------------|---------|
