Update cost-management-billing-faq.yml

Acro edits.

Author: v-stsavell

articles/cost-management-billing/cost-management-billing-faq.yml

@@ -139,7 +139,7 @@ sections:
           See [Migrate from Azure Enterprise Reporting to Microsoft Cost Management APIs](automate/migrate-ea-reporting-arm-apis-overview.md).
       - question: Why do I get Usage Details API timeouts?
         answer: |
-          The Usage Details dataset can often be very large (multiple GBs or more). The larger the size of the dataset that you request, the longer the service takes to compile the data before sending it to you. Because of the delay, synchronous API solutions like the paginated [JSON Usage Details API](/rest/api/consumption/usagedetails/list) might timeout before your data is provided. If you are encounter timeouts or have processes that frequently need to pull a large amount of usage details, see [Retrieve large usage datasets recurringly with Exports](costs/ingest-azure-usage-at-scale.md).
+          The Usage Details dataset can often be very large (multiple GBs or more). The larger the size of the dataset that you request, the longer the service takes to compile the data before sending it to you. Because of the delay, synchronous API solutions like the paginated [JSON Usage Details API](/rest/api/consumption/usagedetails/list) might timeout before your data is provided. If your encounter timeouts or has processes that frequently need to pull a large number of usage details, see [Retrieve large usage datasets recurringly with Exports](costs/ingest-azure-usage-at-scale.md).
       - question: How do I migrate from the EA Reporting APIs to the Microsoft Customer Agreement APIs?
         answer: |
           See [Migrate from Enterprise Agreement to Microsoft Customer Agreement APIs](costs/migrate-cost-management-api.md).
@@ -148,7 +148,7 @@ sections:
     questions:
       - question: Why do I get Usage Details API timeouts?
         answer: |
-          The Usage Details dataset can often be very large (multiple GBs or more). The larger the size of the dataset that you request, the longer the service takes to compile the data before sending it to you. Because of the delay, synchronous API solutions like the paginated JSON Usage Details API might timeout before your data is provided. If you encounter timeouts or have processes that frequently need to pull a large amount of usage details, see [Retrieve large usage datasets recurringly with Exports](costs/ingest-azure-usage-at-scale.md).
+          The Usage Details dataset can often be very large (multiple GBs or more). The larger the size of the dataset that you request, the longer the service takes to compile the data before sending it to you. Because of the delay, synchronous API solutions like the paginated JSON Usage Details API might timeout before your data is provided. If you encounter timeouts or have processes that frequently need to pull a large number of usage details, see [Retrieve large usage datasets recurringly with Exports](costs/ingest-azure-usage-at-scale.md).
       - question: What is the difference between legacy and modern usage details?
         answer: |
           A legacy versus modern usage details record is identified by the *kind* field in the [Usage Details API](/rest/api/consumption/usage-details). The field is used to distinguish between data that’s returned for different customer types. The call patterns to obtain legacy and modern usage details are essentially the same. The granularity of the data is the same. The main difference is the fields available in the usage details records themselves. If you’re an EA customer, you’ll always get legacy usage details records. If you’re a Microsoft Customer Agreement customer, you will always get modern usage details records.