docs: fix typos and grammar in analytics page

x-ads-api/analytics.mdx

@@ -64,7 +64,7 @@ End time is exclusive. For example, a request with `start_time=2026-01-01T00:00:
 
 **Segmentation**
 
-Available only through our asynchronous analytics endpoints, segmentation allows partners and advertisers to retrieve metrics broken out particular targeting values. To request segmented metrics, use the `segmentation_type` request parameter. For more details on segmentation options, see [Metrics and Segmentation](/x-ads-api/analytics#metrics-and-segmentation).
+Available only through our asynchronous analytics endpoints, segmentation allows partners and advertisers to retrieve metrics broken out by particular targeting values. To request segmented metrics, use the `segmentation_type` request parameter. For more details on segmentation options, see [Metrics and Segmentation](/x-ads-api/analytics#metrics-and-segmentation).
 
 ## FAQs
 
@@ -84,7 +84,7 @@ How can I determine which entity IDs to request for a specific time period?
 
 Why are all of the values in the analytics response `null`?
 
-- It's likely that the campaign did not serve during during the requested time period
+- It's likely that the campaign did not serve during the requested time period
 - Use the [Active Entities endpoint](/x-ads-api/analytics#active-entities-2) to determine which entities to fetch analytics for and for what time period
 
 Why does the API show `null` values while the UI shows 0s?
@@ -147,7 +147,7 @@ Some best practices when collecting [analytics](/x-ads-api/analytics) data from
 
 ### Fetching Historical Data
 
-- When backfilling data (i.e. adding a new advertiser account), you may need make several requests in smaller `start_time` and `end_time` chunks.
+- When backfilling data (i.e. adding a new advertiser account), you may need to make several requests in smaller `start_time` and `end_time` chunks.
 - Limit your fetches to 30-day date windows.
 - Throttle these requests and distribute over time so as not to exhaust your rate limits for these fetches.
 
@@ -230,7 +230,7 @@ Which metrics are applicable for an entity depends on the [campaign objective](/
 
 ## Metrics and Segmentation
 
-This document is an overview of the metrics available from our [Analytics](/x-ads-api/analytics) for each entity type, as well as the available segmentation for each metrics.
+This document is an overview of the metrics available from our [Analytics](/x-ads-api/analytics) for each entity type, as well as the available segmentation for each metric.
 
 |  |  |  |  |  |  |  |
 | :-- | :-- | :-- | :-- | :-- | :-- | :-- |
@@ -375,9 +375,9 @@ As of May 2026, only the following segmentation types are enabled. METROS return
 
 ## Derived Metrics
 
-Campaign metrics depend on their [campaign objective](/x-ads-api/campaign-management). Use this guide to determine how to calculcate derived metrics for use based on the objectives in place.
+Campaign metrics depend on their [campaign objective](/x-ads-api/campaign-management). Use this guide to determine how to calculate derived metrics for use based on the objectives in place.
 
-Any `metric` without curly brackets is one that is returned by the Ads API [analytics](/x-ads-api/analytics#synchronous-analytics) endpoints. Any name surrounded by `{curley brackets}` indicates a derived metric for that category.
+Any `metric` without curly brackets is one that is returned by the Ads API [analytics](/x-ads-api/analytics#synchronous-analytics) endpoints. Any name surrounded by `{curly brackets}` indicates a derived metric for that category.
 
 ### ENGAGEMENTS