Use mdx for all route subheadings

Author: JustinBeckwith

docs/events/gateway.mdx

@@ -697,7 +697,8 @@ The [Get Gateway Bot endpoint](/docs/events/gateway#get-gateway-bot) will always
 
 The session start limit for these bots will also be increased from 1000 to `max(2000, (guild_count / 1000) * 5)` per day. You also receive an increased `max_concurrency`, the number of [shards you can concurrently start](/docs/events/gateway#session-start-limit-object).
 
-## Get Gateway % GET /gateway
+## Get Gateway
+<Route type="GET">/gateway</Route>
 
 :::info
 This endpoint does not require authentication.
@@ -713,7 +714,9 @@ Returns an object with a valid WSS URL which the app can use when [Connecting](/
 }
 ```
 
-## Get Gateway Bot % GET /gateway/bot
+## Get Gateway Bot
+
+<Route type="GET">/gateway/bot</Route>
 
 :::warn
 This endpoint requires authentication using a valid bot token.

docs/interactions/application-commands.mdx

@@ -389,7 +389,8 @@ Interaction tokens are valid for **15 minutes**, meaning you can respond to an i
 The endpoints below are not bound to the application's [Global Rate Limit](/docs/topics/rate-limits#global-rate-limit).
 :::
 
-## Create Interaction Response % POST /interactions/\{interaction.id/docs/interactions/receiving-and-responding#interaction-object\}/\{interaction.token/docs/interactions/receiving-and-responding#interaction-object\}/callback
+## Create Interaction Response
+<Route type="POST">/interactions/\{interaction.id/docs/interactions/receiving-and-responding#interaction-object\}/\{interaction.token/docs/interactions/receiving-and-responding#interaction-object\}/callback</Route>
 
 Create a response to an Interaction. Body is an [interaction response](/docs/interactions/receiving-and-responding#interaction-response-object). Returns `204` unless `with_response` is set to `true` which returns `200` with the body as [interaction callback response](/docs/interactions/receiving-and-responding#interaction-callback-interaction-callback-response-object).
 
@@ -402,19 +403,23 @@ This endpoint also supports file attachments similar to the webhook endpoints. R
 | with_response? | [boolean](/docs/reference#boolean-query-strings) | Whether to include an [interaction callback object](/docs/interactions/receiving-and-responding#interaction-callback-interaction-callback-response-object) as the response |
 
 
-## Get Original Interaction Response % GET /webhooks/\{application.id/docs/resources/application#application-object\}/\{interaction.token/docs/interactions/receiving-and-responding#interaction-object\}/messages/@original
+## Get Original Interaction Response
+<Route type="GET">/webhooks/[\{application.id\}](/docs/resources/application#application-object)/[\{interaction.token\}](/docs/interactions/receiving-and-responding#interaction-object)/messages/@original</Route>
 
 Returns the initial Interaction response. Functions the same as [Get Webhook Message](/docs/resources/webhook#get-webhook-message).
 
-## Edit Original Interaction Response % PATCH /webhooks/\{application.id/docs/resources/application#application-object\}/\{interaction.token/docs/interactions/receiving-and-responding#interaction-object\}/messages/@original
+## Edit Original Interaction Response
+<Route type="PATCH">/webhooks/[\{application.id\}](/docs/resources/application#application-object)/[\{interaction.token\}](/docs/interactions/receiving-and-responding#interaction-object)/messages/@original</Route>
 
 Edits the initial Interaction response. Functions the same as [Edit Webhook Message](/docs/resources/webhook#edit-webhook-message).
 
-## Delete Original Interaction Response % DELETE /webhooks/\{application.id/docs/resources/application#application-object\}/\{interaction.token/docs/interactions/receiving-and-responding#interaction-object\}/messages/@original
+## Delete Original Interaction Response
+<Route type="DELETE">/webhooks/[\{application.id\}](/docs/resources/application#application-object)/[\{interaction.token\}](/docs/interactions/receiving-and-responding#interaction-object)/messages/@original</Route>
 
 Deletes the initial Interaction response. Returns `204 No Content` on success.
 
-## Create Followup Message % POST /webhooks/\{application.id/docs/resources/application#application-object\}/\{interaction.token/docs/interactions/receiving-and-responding#interaction-object\}
+## Create Followup Message
+<Route type="POST">/webhooks/[\{application.id\}](/docs/resources/application#application-object)/[\{interaction.token\}](/docs/interactions/receiving-and-responding#interaction-object)</Route>
 
 :::info
 Apps are limited to 5 followup messages per interaction if it was initiated from a user-installed app and isn't installed in the server (meaning the [authorizing integration owners object](/docs/interactions/receiving-and-responding#interaction-object-authorizing-integration-owners-object) only contains `USER_INSTALL`)
@@ -424,14 +429,17 @@ Create a followup message for an Interaction. Functions the same as [Execute Web
 
 When using this endpoint directly after responding to an interaction with `DEFERRED_CHANNEL_MESSAGE_WITH_SOURCE`, this endpoint will function as [Edit Original Interaction Response](/docs/interactions/receiving-and-responding#edit-original-interaction-response) for backwards compatibility. In this case, no new message will be created, and the loading message will be edited instead. The ephemeral flag will be ignored, and the value you provided in the initial defer response will be preserved, as an existing message's ephemeral state cannot be changed. This behavior is deprecated, and you should use the Edit Original Interaction Response endpoint in this case instead.
 
-## Get Followup Message % GET /webhooks/\{application.id/docs/resources/application#application-object\}/\{interaction.token/docs/interactions/receiving-and-responding#interaction-object\}/messages/\{message.id/docs/resources/channel#message-object\}
+## Get Followup Message
+<Route type="GET">/webhooks/[\{application.id\}](/docs/resources/application#application-object)/[\{interaction.token\}](/docs/interactions/receiving-and-responding#interaction-object)/messages/[\{message.id\}](/docs/resources/channel#message-object)</Route>
 
 Returns a followup message for an Interaction. Functions the same as [Get Webhook Message](/docs/resources/webhook#get-webhook-message).
 
-## Edit Followup Message % PATCH /webhooks/\{application.id/docs/resources/application#application-object\}/\{interaction.token/docs/interactions/receiving-and-responding#interaction-object\}/messages/\{message.id/docs/resources/channel#message-object\}
+## Edit Followup Message
+<Route type="PATCH">/webhooks/[\{application.id\}](/docs/resources/application#application-object)/[\{interaction.token\}](/docs/interactions/receiving-and-responding#interaction-object)/messages/[\{message.id\}](/docs/resources/channel#message-object)</Route>
 
 Edits a followup message for an Interaction. Functions the same as [Edit Webhook Message](/docs/resources/webhook#edit-webhook-message).
 
-## Delete Followup Message % DELETE /webhooks/\{application.id/docs/resources/application#application-object\}/\{interaction.token/docs/interactions/receiving-and-responding#interaction-object\}/messages/\{message.id/docs/resources/channel#message-object\}
+## Delete Followup Message
+<Route type="DELETE">/webhooks/[\{application.id\}](/docs/resources/application#application-object)/[\{interaction.token\}](/docs/interactions/receiving-and-responding#interaction-object)/messages/[\{message.id\}](/docs/resources/channel#message-object)</Route>
 
 Deletes a followup message for an Interaction. Returns `204 No Content` on success.

docs/interactions/receiving-and-responding.mdx

@@ -38,11 +38,15 @@ When a user connects their account using the bot's [`role_connections_verificati
 Each metadata type offers a comparison operation that allows guilds to configure role requirements based on metadata values stored by the bot. Bots specify a `metadata value` for each user and guilds specify the required `guild's configured value` within the guild role settings.
 :::
 
-## Get Application Role Connection Metadata Records % GET /applications/{application.id/docs/resources/application#application-object}/role-connections/metadata
+## Get Application Role Connection Metadata Records
+
+<Route type="GET">/applications/[\{application.id\}](/docs/resources/application#application-object)/role-connections/metadata</Route>
 
 Returns a list of [application role connection metadata](/docs/resources/application-role-connection-metadata#application-role-connection-metadata-object) objects for the given application.
 
-## Update Application Role Connection Metadata Records % PUT /applications/{application.id/docs/resources/application#application-object}/role-connections/metadata
+## Update Application Role Connection Metadata Records
+
+<Route type="PUT">/applications/[\{application.id\}](/docs/resources/application#application-object)/role-connections/metadata</Route>
 
 Updates and returns a list of [application role connection metadata](/docs/resources/application-role-connection-metadata#application-role-connection-metadata-object) objects for the given application.
 

docs/resources/application-role-connection-metadata.md renamed to docs/resources/application-role-connection-metadata.mdx

@@ -182,9 +182,8 @@ By default, newly-created apps only support installation to guilds.
 
 You can update which installation contexts your app supports in your [app's settings](https://discord.com/developers/applications). On the **Installation** page under the **Installation Contexts** section, you can select the installation contexts your app supports.
 
-:::info
-If you update your app to support a new installation context, you will need to update your existing [commands](/docs/interactions/application-commands#contexts) if you want them to be supported in the new context. Details are in the [Application Command](/docs/interactions/application-commands#contexts) documentation.
-:::
+> info
+> If you update your app to support a new installation context, you will need to update your existing [commands](/docs/interactions/application-commands#contexts) if you want them to be supported in the new context. Details are in the [Application Command](/docs/interactions/application-commands#contexts) documentation.
 
 ## Install Links
 
@@ -194,9 +193,8 @@ Install links provide an easy way for users to install your app in Discord. If y
 
 There are three options when configuring an install link for your app: "Discord Provided Link", "Custom URL", and "None". If you don't configure an install link (by selecting "None"), the "Add App" button will not appear for your app, and your app will not be eligible for the App Directory.
 
-:::info
-Note that install links are distinct from OAuth2 flows like the [authorization code grant](/docs/topics/oauth2#authorization-code-grant), which may additionally be required if you need to request user-specific [scopes](/docs/topics/oauth2#shared-resources-oauth2-scopes) like `identify` or `role_connections.write`.
-:::
+> info
+> Note that install links are distinct from OAuth2 flows like the [authorization code grant](/docs/topics/oauth2#authorization-code-grant), which may additionally be required if you need to request user-specific [scopes](/docs/topics/oauth2#shared-resources-oauth2-scopes) like `identify` or `role_connections.write`.
 
 #### Discord Provided Link
 
@@ -210,9 +208,8 @@ https://discord.com/oauth2/authorize?client_id=1234567895647001626
 
 Instead, these links will prompt the user for the scopes and bot user permissions configured in your Default Install Settings.
 
-:::info
-Discord Provided Links are limited to the `application.commands` and `bot` scopes
-:::
+> info
+> Discord Provided Links are limited to the `application.commands` and `bot` scopes
 
 #### Custom URL
 
@@ -226,17 +223,18 @@ You can configure your app's install link in your [app's settings](https://disco
 
 The Default Install Settings will appear on the **Installation** page when you have "Discord Provided Link" selected as your install link type.
 
-## Get Current Application % GET /applications/@me
+## Get Current Application
+<Route type="GET">/applications/@me</Route>
 
 Returns the [application](/docs/resources/application#application-object) object associated with the requesting bot user.
 
-## Edit Current Application % PATCH /applications/@me
+## Edit Current Application
+<Route type="PATCH">/applications/@me</Route>
 
 Edit properties of the app associated with the requesting bot user. Only properties that are passed will be updated. Returns the updated [application](/docs/resources/application#application-object) object on success.
 
-:::info
-All parameters to this endpoint are optional
-:::
+> info
+> All parameters to this endpoint are optional
 
 ###### JSON Params
 
@@ -260,11 +258,11 @@ All parameters to this endpoint are optional
 
 \*\* To update an Interactions endpoint URL via the API, the URL must be valid according to the [Receiving an Interaction](/docs/interactions/receiving-and-responding#receiving-an-interaction) documentation.
 
-## Get Application Activity Instance % GET /applications/{application.id/docs/resources/application#application-object}/activity-instances/{instance_id}
+## Get Application Activity Instance
+<Route>/applications/[\{application.id\}](/docs/resources/application#application-object)/activity-instances/[\{instance_id\}](/docs/resources/application#get-application-activity-instance-activity-instance-object)</Route>
 
 Returns a serialized activity instance, if it exists. Useful for [preventing unwanted activity sessions](/docs/activities/development-guides#preventing-unwanted-activity-sessions).
 
-
 ###### Example Activity Instance
 
 ```json
@@ -293,7 +291,6 @@ Returns a serialized activity instance, if it exists. Useful for [preventing unw
 | users          | array of snowflakes, [user](/docs/resources/user#user-object) IDs                                           | IDs of the Users currently connected to the instance                                     |
 
 
-
 ###### Activity Location Object
 
 The Activity Location is an object that describes the location in which an activity instance is running.

docs/resources/application.md renamed to docs/resources/application.mdx

@@ -197,7 +197,8 @@ For most objects, the change keys may be any field on the changed object. The fo
 | [Partial Role](/docs/topics/permissions#role-object)                                                                                           | `$add` and `$remove` as keys                                   | `new_value` is an array of objects that contain the role `id` and `name`                                                                                                                                                                                    |
 | [Webhook](/docs/resources/webhook#webhook-object)                                                                                              | `avatar_hash` key (instead of `avatar`)                        |                                                                                                                                                                                                                                                             |
 
-## Get Guild Audit Log % GET /guilds/{guild.id/docs/resources/guild#guild-object}/audit-logs
+## Get Guild Audit Log
+<Route type="GET">/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/audit-logs</Route>
 
 Returns an [audit log](/docs/resources/audit-log#audit-log-object) object for the guild. Requires the [`VIEW_AUDIT_LOG`](/docs/topics/permissions#permissions-bitwise-permission-flags) permission.
 

docs/resources/audit-log.md renamed to docs/resources/audit-log.mdx

@@ -198,23 +198,26 @@ value of [action type](/docs/resources/auto-moderation#auto-moderation-action-ob
 Users are required to have the `MANAGE_GUILD` permission to access all Auto Moderation resources.
 Some [action types](/docs/resources/auto-moderation#auto-moderation-action-object-action-types) require additional permissions, e.g. the `TIMEOUT` action type requires an additional `MODERATE_MEMBERS` permission.
 
-## List Auto Moderation Rules for Guild % GET /guilds/{guild.id/docs/resources/guild#guild-object}/auto-moderation/rules
+## List Auto Moderation Rules for Guild
+<Route type="GET">/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/auto-moderation/rules</Route>
 
 Get a list of all rules currently configured for the guild. Returns a list of [auto moderation rule](/docs/resources/auto-moderation#auto-moderation-rule-object) objects for the given guild.
 
 :::info
 This endpoint requires the `MANAGE_GUILD` [permission](/docs/resources/auto-moderation#auto-moderation-permission-requirements).
 :::
 
-## Get Auto Moderation Rule % GET /guilds/{guild.id/docs/resources/guild#guild-object}/auto-moderation/rules/{auto_moderation_rule.id/docs/resources/auto-moderation#auto-moderation-rule-object}
+## Get Auto Moderation Rule
+<Route type="GET">/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/auto-moderation/rules/[\{auto_moderation_rule.id\}](/docs/resources/auto-moderation#auto-moderation-rule-object)</Route>
 
 Get a single rule. Returns an [auto moderation rule](/docs/resources/auto-moderation#auto-moderation-rule-object) object.
 
 :::info
 This endpoint requires the `MANAGE_GUILD` [permission](/docs/resources/auto-moderation#auto-moderation-permission-requirements).
 :::
 
-## Create Auto Moderation Rule % POST /guilds/{guild.id/docs/resources/guild#guild-object}/auto-moderation/rules
+## Create Auto Moderation Rule
+<Route type="POST">/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/auto-moderation/rules</Route>
 
 Create a new rule. Returns an [auto moderation rule](/docs/resources/auto-moderation#auto-moderation-rule-object) on success. Fires an [Auto Moderation Rule Create](/docs/events/gateway-events#auto-moderation-rule-create) Gateway event.
 
@@ -246,7 +249,8 @@ See [Trigger Types](/docs/resources/auto-moderation#auto-moderation-rule-object-
 :::
 
 
-## Modify Auto Moderation Rule % PATCH /guilds/{guild.id/docs/resources/guild#guild-object}/auto-moderation/rules/{auto_moderation_rule.id/docs/resources/auto-moderation#auto-moderation-rule-object}
+## Modify Auto Moderation Rule
+<Route type="PATCH">/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/auto-moderation/rules/[\{auto_moderation_rule.id\}](/docs/resources/auto-moderation#auto-moderation-rule-object)</Route>
 
 Modify an existing rule. Returns an [auto moderation rule](/docs/resources/auto-moderation#auto-moderation-rule-object) on success. Fires an [Auto Moderation Rule Update](/docs/events/gateway-events#auto-moderation-rule-update) Gateway event.
 
@@ -276,7 +280,8 @@ This endpoint supports the `X-Audit-Log-Reason` header.
 
 \* Can be omitted based on `trigger_type`. See the `Associated Trigger Types` column in [trigger metadata](/docs/resources/auto-moderation#auto-moderation-rule-object-trigger-metadata) to understand which `trigger_type` values require `trigger_metadata` to be set.
 
-## Delete Auto Moderation Rule % DELETE /guilds/{guild.id/docs/resources/guild#guild-object}/auto-moderation/rules/{auto_moderation_rule.id/docs/resources/auto-moderation#auto-moderation-rule-object}
+## Delete Auto Moderation Rule
+<Route type="DELETE">/guilds/[\{guild.id\}](/docs/resources/guild#guild-object)/auto-moderation/rules/[\{auto_moderation_rule.id\}](/docs/resources/auto-moderation#auto-moderation-rule-object)</Route>
 
 Delete a rule. Returns a `204` on success. Fires an [Auto Moderation Rule Delete](/docs/events/gateway-events#auto-moderation-rule-delete) Gateway event.