fix: repair broken frontmatter and a typo in docs (#103)

mintlify[bot] · web-flow · commit 93da0e8db16c · 2026-05-21T17:49:59.000Z
Co-authored-by: mintlify[bot] &lt;109931778+mintlify[bot]@users.noreply.github.com&gt;
diff --git a/enterprise-api/direct-messages/manage/migrate.mdx b/enterprise-api/direct-messages/manage/migrate.mdx
@@ -3,7 +3,8 @@ title: Migration guide
 sidebarTitle: Migration guide
 keywords: ["manage direct messages migration", "DM management migration", "v1.1 to v2 manage DMs", "DM migration guide", "migrate DM management"]
 
-description: 1 and v2 versions of the Direct Messages endpoints provide methods for creating Direct Message messages.---
+description: 1 and v2 versions of the Direct Messages endpoints provide methods for creating Direct Message messages.
+---
 
 import { Button } from '/snippets/button.mdx';
 
diff --git a/enterprise-api/posts/search/integrate/paginate.mdx b/enterprise-api/posts/search/integrate/paginate.mdx
@@ -3,7 +3,8 @@ title: Pagination
 sidebarTitle: Pagination
 keywords: ["search pagination", "pagination guide", "page through results", "pagination tokens", "search pagination", "next token"]
 
-description: Search queries typically match on more Posts than can be returned in a single API response. When that happens, the data is returned in a series of 'pages'.---
+description: Search queries typically match on more Posts than can be returned in a single API response. When that happens, the data is returned in a series of 'pages'.
+---
 
 ### Recent search pagination
 
diff --git a/enterprise-api/spaces/introduction.mdx b/enterprise-api/spaces/introduction.mdx
@@ -3,7 +3,8 @@ title: Introduction
 sidebarTitle: Introduction
 keywords: ["spaces", "X spaces", "audio spaces", "live audio", "spaces API", "spaces lookup", "spaces search", "spaces discovery"]
 
-description: The following page describes the Spaces endpoints included in the X API. To learn more about Spaces in general, please visit [help.---
+description: The following page describes the Spaces endpoints included in the X API. To learn more about Spaces in general, please visit [help.
+---
 
 import { Button } from '/snippets/button.mdx';
 
diff --git a/fundamentals/authentication/guides/v2-authentication-mapping.mdx b/fundamentals/authentication/guides/v2-authentication-mapping.mdx
@@ -3,7 +3,8 @@ title: X API v2 authentication mapping
 sidebarTitle: Endpoint mapping
 keywords: ["authentication mapping", "v2 authentication", "endpoint mapping", "auth mapping", "v1 to v2 mapping", "authentication guide"]
 
-description: The following chart illustrates which v2 endpoints map to what authentication methods. | | | | | | :--- | :--- | :--- | :--- | | **Endpoint** | **OAuth 1.---
+description: The following chart illustrates which v2 endpoints map to what authentication methods. | | | | | | :--- | :--- | :--- | :--- | | **Endpoint** | **OAuth 1.
+---
 
 import { Button } from "/snippets/button.mdx";
 
diff --git a/fundamentals/authentication/oauth-1-0a/creating-a-signature.mdx b/fundamentals/authentication/oauth-1-0a/creating-a-signature.mdx
@@ -3,7 +3,8 @@ title: Creating a signature
 sidebarTitle: Creating a signature
 keywords: ["OAuth signature", "create signature", "OAuth 1.0a signature", "HMAC signature", "signature generation", "OAuth signing"]
 
-description: This page explains how to generate an OAuth 1. 0a HMAC-SHA1 signature for an HTTP request.---
+description: This page explains how to generate an OAuth 1. 0a HMAC-SHA1 signature for an HTTP request.
+---
 
 import { Button } from "/snippets/button.mdx";
 
diff --git a/fundamentals/authentication/oauth-1-0a/overview.mdx b/fundamentals/authentication/oauth-1-0a/overview.mdx
@@ -3,7 +3,8 @@ title: OAuth 1.0a
 sidebarTitle: Overview
 keywords: ["OAuth 1.0a", "OAuth 1.0", "OAuth 1.0a authentication", "OAuth 1.0a user context", "three-legged OAuth", "OAuth 1.0a flow"]
 
-description: Many endpoints on the X developer platform use the OAuth 1. 0a method to act, or make API requests, on behalf of a X account.---
+description: Many endpoints on the X developer platform use the OAuth 1. 0a method to act, or make API requests, on behalf of a X account.
+---
 
 import { Button } from "/snippets/button.mdx";
 
diff --git a/fundamentals/authentication/oauth-1-0a/percent-encoding-parameters.mdx b/fundamentals/authentication/oauth-1-0a/percent-encoding-parameters.mdx
@@ -3,7 +3,8 @@ title: Percent encoding parameters
 sidebarTitle: Percent encoding parameters
 keywords: ["percent encoding", "URL encoding", "OAuth encoding", "parameter encoding", "URL encode", "OAuth 1.0a encoding"]
 
-description: Parts of the X API, particularly those dealing with OAuth signatures, require strings to be encoded according to [RFC 3986, Section 2. 1](http://tools.---
+description: Parts of the X API, particularly those dealing with OAuth signatures, require strings to be encoded according to [RFC 3986, Section 2. 1](http://tools.
+---
 
 import { Button } from "/snippets/button.mdx";
 
diff --git a/fundamentals/authentication/oauth-2-0/bearer-tokens.mdx b/fundamentals/authentication/oauth-2-0/bearer-tokens.mdx
@@ -3,7 +3,8 @@ title: Using and generating an app-only Bearer Token
 sidebarTitle: Generating and using app-only Bearer Tokens
 keywords: ["Bearer token", "app-only token", "Bearer Token", "OAuth 2.0 Bearer", "app authentication", "generate Bearer token"]
 
-description: A bearer token allows developers to have a more secure point of entry for using the X APIs, and are one of the core features of OAuth 2.---
+description: A bearer token allows developers to have a more secure point of entry for using the X APIs, and are one of the core features of OAuth 2.
+---
 
 ### Using and generating an app-only Bearer Token
 
diff --git a/fundamentals/authentication/oauth-2-0/overview.mdx b/fundamentals/authentication/oauth-2-0/overview.mdx
@@ -3,7 +3,8 @@ title: OAuth 2.0
 sidebarTitle: Overview
 keywords: ["OAuth 2.0", "OAuth 2.0 authentication", "OAuth 2.0 PKCE", "Bearer token", "app-only auth", "OAuth 2.0 flow", "authorization code"]
 
-description: 0 Bearer Token authenticates requests on behalf of your [developer App](/resources/fundamentals/developer-apps).---
+description: 0 Bearer Token authenticates requests on behalf of your [developer App](/resources/fundamentals/developer-apps).
+---
 
 ### Bearer Token (also known as app-only)
 
diff --git a/fundamentals/authentication/overview.mdx b/fundamentals/authentication/overview.mdx
@@ -3,7 +3,8 @@ title: Authentication
 sidebarTitle: Overview
 keywords: ["authentication", "OAuth", "OAuth 1.0a", "OAuth 2.0", "API authentication", "bearer token", "access tokens", "API keys", "user context", "app only", "PKCE", "authorization code", "basic authentication"]
 
-description: X APIs handle enormous amounts of data. The way we ensure this data is secured for developers and users alike is through authentication.---
+description: X APIs handle enormous amounts of data. The way we ensure this data is secured for developers and users alike is through authentication.
+---
 
 import { Button } from "/snippets/button.mdx";
 
diff --git a/x-ads-api/creatives.mdx b/x-ads-api/creatives.mdx
@@ -35,7 +35,7 @@ The Ads API supports several card types that can be used in Tweets, which can th
 
 #### Image
 
-The following image specifications apply to assets used in [Cards](/x-ads-api/creatives/reference#cards-2). Images must be 3MB or less and have an a width of at least 800px. In addition, we support the following width:height aspect ratios.
+The following image specifications apply to assets used in [Cards](/x-ads-api/creatives/reference#cards-2). Images must be 3MB or less and have a width of at least 800px. In addition, we support the following width:height aspect ratios.
 
 - Website: 1:1 and 1.91:1
 - Image App Download: 1:1 and 1.91:1
diff --git a/x-ads-api/fundamentals/accessing-ads-accounts.mdx b/x-ads-api/fundamentals/accessing-ads-accounts.mdx
@@ -2,7 +2,8 @@
 title: Accessing Ads accounts
 keywords: ["ads accounts", "ad accounts", "access ads accounts", "account access", "ads account management", "account hierarchy"]
 
-description: There are two different types of accounts involved in using the Ads API: advertising accounts and X user accounts. Throughout Ads API documentation, the...---
+description: "There are two different types of accounts involved in using the Ads API: advertising accounts and X user accounts. Throughout Ads API documentation, the..."
+---
 
 # User accounts vs Ad accounts
 
diff --git a/x-ads-api/fundamentals/currency.mdx b/x-ads-api/fundamentals/currency.mdx
@@ -2,7 +2,8 @@
 title: Currency
 keywords: ["currency", "ISO-4217", "currency codes", "micros", "currency format", "money format", "currency values"]
 
-description: The type of a currency is identified using [ISO-4217](http://en.---
+description: The type of a currency is identified using [ISO-4217](http://en.
+---
 
 The type of a currency is identified using [ISO-4217](http://en.wikipedia.org/wiki/ISO_4217). This is a three-letter string like `USD` or `EUR`. The value of a currency is represented in micros. For USD, $5.50 is encoded as 5.50*1e6, or 5,500,000. To represent a “whole value”, you need to multiply the local micro by 1e6 (1\_000\_000) for all currencies.
 
diff --git a/x-ads-api/fundamentals/making-authenticated-requests.mdx b/x-ads-api/fundamentals/making-authenticated-requests.mdx
@@ -2,7 +2,8 @@
 title: Making Authenticated Requests
 keywords: ["Ads API authentication", "authenticated requests", "Ads API auth", "OAuth Ads API", "Ads API requests", "authentication"]
 
-description: Accessing the X Ads API endpoints requires your application to send authenticated web requests securely using TLS to https://ads-api.---
+description: Accessing the X Ads API endpoints requires your application to send authenticated web requests securely using TLS to https://ads-api.
+---
 Accessing the X Ads API endpoints requires your application to send authenticated web requests securely using TLS to https://ads-api.x.com.
 
 The following sections will provide an overview of making authenticated API requests, setting up [Twurl](https://github.com/twitter/twurl#getting-started) to interact with the API, and extending your application to support OAuth 1.0a and make requests against your Ads account.
diff --git a/x-ads-api/fundamentals/rate-limiting.mdx b/x-ads-api/fundamentals/rate-limiting.mdx
@@ -2,7 +2,8 @@
 title: Rate limiting
 keywords: ["Ads API rate limits", "rate limiting", "Ads API throttling", "rate limits", "request limits", "Ads API limits"]
 
-description: The Advertiser API is rate limited similarly to REST API v1. 1, as documented here: [REST API Rate Limiting in v1.---
+description: "The Advertiser API is rate limited similarly to REST API v1. 1, as documented here: [REST API Rate Limiting in v1."
+---
 
 The Advertiser API is rate limited similarly to REST API v1.1, as documented here: [REST API Rate Limiting in v1.1](https://developer.x.com/content/developer-twitter/en/docs/basics/rate-limits). Unlike REST API v1.1, there is no programmatic index of the limits per endpoint. The endpoint rate limits and reset windows are communicated via HTTP response headers.  All rate limiting in the Ads API utilizes OAuth 1.0A.
 
diff --git a/x-ads-api/measurement/mobile-conversions.mdx b/x-ads-api/measurement/mobile-conversions.mdx
@@ -2,7 +2,8 @@
 title: Mobile Conversions
 keywords: ["mobile conversions", "mobile conversion tracking", "app conversions", "mobile app tracking", "conversion tracking"]
 
-description: X [mobile app promotion](https://biz.---
+description: X [mobile app promotion](https://biz.
+---
 
 import { Button } from '/snippets/button.mdx';
 
diff --git a/x-api/direct-messages/manage/migrate.mdx b/x-api/direct-messages/manage/migrate.mdx
@@ -3,7 +3,8 @@ title: Migration guide
 sidebarTitle: Migration guide
 keywords: ["manage direct messages migration", "DM management migration", "v1.1 to v2 manage DMs", "DM migration guide", "migrate DM management"]
 
-description: 1 and v2 versions of the Direct Messages endpoints provide methods for creating Direct Message messages.---
+description: 1 and v2 versions of the Direct Messages endpoints provide methods for creating Direct Message messages.
+---
 
 import { Button } from '/snippets/button.mdx';
 
diff --git a/x-api/enterprise-gnip-2.0/fundamentals/data-enrichments.mdx b/x-api/enterprise-gnip-2.0/fundamentals/data-enrichments.mdx
@@ -2,7 +2,8 @@
 title: "Data enrichments: Enterprise"
 keywords: ["data enrichments", "enterprise enrichments", "GNIP enrichments", "data enrichment", "enriched data", "enterprise data enrichment"]
 
-description: `Enterprise` Enterprise enrichments are additive metadata included in the response payload of some of the data APIs. They are available in paid subscrip...---
+description: "`Enterprise` Enterprise enrichments are additive metadata included in the response payload of some of the data APIs. They are available in paid subscrip..."
+---
 
 
 ## Introduction
diff --git a/x-api/enterprise-gnip-2.0/fundamentals/decahose-api.mdx b/x-api/enterprise-gnip-2.0/fundamentals/decahose-api.mdx
@@ -2,7 +2,8 @@
 title: Decahose API
 keywords: ["Decahose", "10% stream", "decahose API", "enterprise decahose", "10% sampled stream", "enterprise streaming"]
 
-description: [Enterprise](https://developer.---
+description: "[Enterprise](https://developer."
+---
 
 <Note>
 This endpoint has been updated to include Post edit metadata. Learn more about these metadata on the ["Edit Posts" fundamentals page](/x-api/enterprise-gnip-2.0/fundamentals/edit-tweets). 
diff --git a/x-api/enterprise-gnip-2.0/fundamentals/engagement-api.mdx b/x-api/enterprise-gnip-2.0/fundamentals/engagement-api.mdx
@@ -2,7 +2,8 @@
 title: Engagement API
 keywords: ["Engagement API", "enterprise Engagement API", "engagement metrics", "engagement data", "enterprise engagement", "GNIP engagement"]
 
-description: [`Enterprise`](https://developer.---
+description: "[`Enterprise`](https://developer."
+---
 ## Overview
 
 [`Enterprise`](https://developer.x.com/en/products/x-api/enterprise)
diff --git a/x-api/enterprise-gnip-2.0/fundamentals/firehouse.mdx b/x-api/enterprise-gnip-2.0/fundamentals/firehouse.mdx
@@ -2,7 +2,8 @@
 title: Compliance Firehose API
 keywords: ["compliance firehose", "firehose API", "compliance API", "enterprise firehose", "compliance stream", "firehose"]
 
-description: >**Please note** > >We have released a new compliance tool to X API v2 called [batch compliance](/x-api/compliance/batch-compliance). This new tool allo...---
+description: "**Please note** > >We have released a new compliance tool to X API v2 called [batch compliance](/x-api/compliance/batch-compliance). This new tool allo..."
+---
 
 >**Please note**
 >
diff --git a/x-api/enterprise-gnip-2.0/fundamentals/overview.mdx b/x-api/enterprise-gnip-2.0/fundamentals/overview.mdx
@@ -2,7 +2,8 @@
 title: Gnip console
 keywords: ["GNIP console", "enterprise console", "GNIP", "enterprise API", "GNIP API", "enterprise data", "GNIP platform"]
 
-description: >The enterprise console (at console.---
+description: "The enterprise console (at console."
+---
 ## Overview
 
 >The enterprise console (at console.gnip.com) is available to enterprise data customers with contracted enterprise API access. If you are not currently an enterprise data customer but would like more information, you can learn more about [enterprise data](https://developer.x.com/en/products/x-api/enterprise) here.
diff --git a/x-api/enterprise-gnip-2.0/fundamentals/search-api.mdx b/x-api/enterprise-gnip-2.0/fundamentals/search-api.mdx
@@ -3,7 +3,8 @@ title: "Search API: Enterprise"
 sidebarTitle: Search API
 keywords: ["enterprise search", "GNIP search", "enterprise search API", "search API enterprise", "enterprise search endpoints"]
 
-description: >**Please note:** > >We have released a new version of [search Posts](/x-api/posts/search/introduction) and [Post counts](/x-api/posts/counts/introducti...---
+description: "**Please note:** > >We have released a new version of [search Posts](/x-api/posts/search/introduction) and [Post counts](/x-api/posts/counts/introducti..."
+---
 
 >**Please note:**
 >
diff --git a/x-api/posts/search/integrate/paginate.mdx b/x-api/posts/search/integrate/paginate.mdx
@@ -3,7 +3,8 @@ title: Pagination
 sidebarTitle: Pagination
 keywords: ["search pagination", "pagination guide", "page through results", "pagination tokens", "search pagination", "next token"]
 
-description: Search queries typically match on more Posts than can be returned in a single API response. When that happens, the data is returned in a series of 'pages'.---
+description: Search queries typically match on more Posts than can be returned in a single API response. When that happens, the data is returned in a series of 'pages'.
+---
 
 ### Recent search pagination
 
diff --git a/xdks/python/authentication.mdx b/xdks/python/authentication.mdx
@@ -2,7 +2,8 @@
 title: Authentication
 sidebarTitle: Authentication
 
-description: The X API requires authentication for all endpoints. The XDK supports three authentication methods: 1.---
+description: "The X API requires authentication for all endpoints. The XDK supports three authentication methods: 1."
+---
 The X API requires authentication for all endpoints. The XDK supports three authentication methods:
 1. Bearer Token (app-only)
 2. OAuth 2.0 with PKCE
diff --git a/xdks/python/pagination.mdx b/xdks/python/pagination.mdx
@@ -2,7 +2,8 @@
 title: Pagination
 sidebarTitle: Pagination
 
-description: The X API uses pagination for endpoints that return multiple pages of results (e.---
+description: The X API uses pagination for endpoints that return multiple pages of results (e.
+---
 The X API uses pagination for endpoints that return multiple pages of results (e.g. timelines, search etc.). Each API call response includes a `meta` object with `result_count`, `previous_token`, and `next_token`. The XDK takes care of making multiple API calls using the `next_token` so developers can just specify how much data they are looking for without having to make multiple calls.
 The SDK simplifies this with:
 - **Built-in Iterators**: Use generator functions for seamless multi-page fetching.
diff --git a/xdks/python/streaming.mdx b/xdks/python/streaming.mdx
@@ -2,7 +2,8 @@
 title: Streaming
 sidebarTitle: Streaming
 
-description: The X API supports real-time data via endpoints like the [Filtered Stream Endpoint](https://docs.---
+description: The X API supports real-time data via endpoints like the [Filtered Stream Endpoint](https://docs.
+---
 The X API supports real-time data via endpoints like the [Filtered Stream Endpoint](https://docs.x.com/x-api/posts/filtered-stream/introduction), delivering matching Posts as they occur. This requires making a persistent http connection.
 ## Setup and Basic Streaming
 ### Synchronous
diff --git a/xdks/typescript/authentication.mdx b/xdks/typescript/authentication.mdx
@@ -2,7 +2,8 @@
 title: "Authentication"
 sidebarTitle: "Authentication"
 
-description: The TypeScript SDK supports multiple authentication methods for different use cases.---
+description: The TypeScript SDK supports multiple authentication methods for different use cases.
+---
 
 The TypeScript SDK supports multiple authentication methods for different use cases.
 
diff --git a/xdks/typescript/streaming.mdx b/xdks/typescript/streaming.mdx
@@ -2,7 +2,8 @@
 title: "Streaming"
 sidebarTitle: "Streaming"
 
-description: The TypeScript SDK provides real-time streaming capabilities for live data feeds. Connect to real-time sampled posts: Consume the stream with async iter...---
+description: "The TypeScript SDK provides real-time streaming capabilities for live data feeds. Connect to real-time sampled posts: Consume the stream with async iter..."
+---
 
 The TypeScript SDK provides real-time streaming capabilities for live data feeds.
 
