Updated links

anthonydiscord · anthonydiscord · commit 58c0d1155ada · 2025-04-22T19:10:31.000Z
diff --git a/docs/change-log/2017-07-24-new-feature-audit-logs.md b/docs/change-log/2017-07-24-new-feature-audit-logs.md
@@ -3,4 +3,4 @@ title: "New Feature: Audit Logs"
 date: "2017-07-24"
 ---
 
-Audit logs are here! Well, they've been here all along, but now we've got [documentation](/docs/resources/audit-log#) about them. Check it out, but remember: with great power comes great responsibility.
+Audit logs are here! Well, they've been here all along, but now we've got [documentation](/docs/resources/audit-log) about them. Check it out, but remember: with great power comes great responsibility.
diff --git a/docs/change-log/2018-01-23-deprecation-accept-invite-endpoint.md b/docs/change-log/2018-01-23-deprecation-accept-invite-endpoint.md
@@ -3,4 +3,4 @@ title: "Deprecation: Accept Invite Endpoint"
 date: "2018-01-23"
 ---
 
-The [Accept Invite](/docs/resources/invite#) endpoint is deprecated starting today, and will be discontinued on March 23, 2018. The [Add Guild Member](/docs/resources/guild#add-guild-member) endpoint should be used in its place.
+The [Accept Invite](/docs/resources/invite) endpoint is deprecated starting today, and will be discontinued on March 23, 2018. The [Add Guild Member](/docs/resources/guild#add-guild-member) endpoint should be used in its place.
diff --git a/docs/change-log/2019-08-12-more-precise-rate-limits.md b/docs/change-log/2019-08-12-more-precise-rate-limits.md
@@ -3,4 +3,4 @@ title: "More Precise Rate Limits"
 date: "2019-08-12"
 ---
 
-You can now get more precise rate limit reset times, via a new request header. Check out the [rate limits](/docs/topics/rate-limits#) documentation for more information.
+You can now get more precise rate limit reset times, via a new request header. Check out the [rate limits](/docs/topics/rate-limits) documentation for more information.
diff --git a/docs/change-log/2020-12-15-slash-commands-and-interactions.md b/docs/change-log/2020-12-15-slash-commands-and-interactions.md
@@ -3,7 +3,7 @@ title: "Slash Commands and Interactions"
 date: "2020-12-15"
 ---
 
-Slash Commands are here! There's a *lot* to cover, so go check out specific documentation under [Slash Commands](/docs/interactions/application-commands#).
+Slash Commands are here! There's a *lot* to cover, so go check out specific documentation under [Slash Commands](/docs/interactions/application-commands).
 
 Slash Commands include some new features for webhooks as well:
 
diff --git a/docs/change-log/2023-09-26-premium-app-subscriptions-available-in-the-us.md b/docs/change-log/2023-09-26-premium-app-subscriptions-available-in-the-us.md
@@ -17,6 +17,6 @@ Starting today, eligible US-based developers can monetize their verified apps wi
   * [Delete Test Entitlement](/docs/resources/entitlement#delete-test-entitlement)  `DELETE /applications/<application.id>/entitlements/<entitlement.id>`
 * [Gateway Events](/docs/events/gateway-events#entitlements) for working with entitlements: `ENTITLEMENT_CREATE`, `ENTITLEMENT_UPDATE`, `ENTITLEMENT_DELETE`
 * New [`PREMIUM_REQUIRED (10)` interaction response type](/docs/interactions/receiving-and-responding#interaction-response-object-interaction-callback-type) is available to prompt users to upgrade
-* New `entitlements` field, which is an array of [entitlement](/docs/resources/entitlement#) objects, available in interaction data payloads when [receiving and responding to interactions](/docs/interactions/receiving-and-responding#interaction-object-interaction-structure)
+* New `entitlements` field, which is an array of [entitlement](/docs/resources/entitlement) objects, available in interaction data payloads when [receiving and responding to interactions](/docs/interactions/receiving-and-responding#interaction-object-interaction-structure)
 
 To learn more about eligibility details and how to enable monetization for your app, check out the [Monetization Overview](/docs/monetization/overview).
diff --git a/docs/components/reference.mdx b/docs/components/reference.mdx
@@ -29,7 +29,7 @@ For a practical guide on implementing these components, see our [Using Message C
 
 Components allow you to style and structure your messages, modals, and interactions. They are interactive elements that can create rich user experiences in your Discord applications.
 
-Components are a field on the [message object](/docs/resources/message#message-object) and [modal](/docs/interactions/receiving-and-responding#interaction-response-object-modal). You can use them when creating messages or responding to an interaction, like an [application command](/docs/interactions/application-commands#).
+Components are a field on the [message object](/docs/resources/message#message-object) and [modal](/docs/interactions/receiving-and-responding#interaction-response-object-modal). You can use them when creating messages or responding to an interaction, like an [application command](/docs/interactions/application-commands).
 
 ### Component Object
 
@@ -1153,13 +1153,13 @@ To use this component, you need to send the [message flag](/docs/resources/messa
 
 ## Unfurled Media Item Structure
 
-| Field         | Type    | Description                                                                                                                                      |
-|---------------|---------|--------------------------------------------------------------------------------------------------------------------------------------------------|
-| url           | string  | Supports arbitrary urls and attachment://\<filename> references                                                                                  |
-| proxy_url?    | string  | The proxied url of the media item. This field is ignored and provided by the API as part of the response                                         |
-| height?       | integer | The height of the media item. This field is ignored and provided by the API as part of the response                                              |
-| width?        | integer | The width of the media item. This field is ignored and provided by the API as part of the response                                               |
-| content_type? | string  | The [media type](https://en.wikipedia.org/wiki/Media_type) of the content. This field is ignored and provided by the API as part of the response |
+| Field         | Type     | Description                                                                                                                                      |
+|---------------|----------|--------------------------------------------------------------------------------------------------------------------------------------------------|
+| url           | string   | Supports arbitrary urls and attachment://\<filename> references                                                                                  |
+| proxy_url?    | string   | The proxied url of the media item. This field is ignored and provided by the API as part of the response                                         |
+| height?       | ?integer | The height of the media item. This field is ignored and provided by the API as part of the response                                              |
+| width?        | ?integer | The width of the media item. This field is ignored and provided by the API as part of the response                                               |
+| content_type? | string   | The [media type](https://en.wikipedia.org/wiki/Media_type) of the content. This field is ignored and provided by the API as part of the response |
 
 ### Uploading a file
 
diff --git a/docs/components/using-message-components.mdx b/docs/components/using-message-components.mdx
@@ -30,13 +30,13 @@ All content must be sent as components instead of using the standard message for
 
 ```json
 {
+  "flags": "32768",
   "components": [
     {
       "type": 10,
       "content": "This is a message using the Text Display component"
     },
-  ],
-  "flags": "32768"
+  ]
 }
 ```
 
@@ -46,6 +46,7 @@ To send a message with multiple components, you can include multiple component o
 
 ```json
 {
+  "flags": "32768",
   "components": [
     {
       "type": 10,
@@ -55,8 +56,7 @@ To send a message with multiple components, you can include multiple component o
       "type": 10,
       "content": "This is another Text Display component!"
     },
-  ],
-  "flags": "32768"
+  ]
 }
 ```
 
@@ -68,6 +68,7 @@ For example, you can create a message with an Action Row component that contains
 
 ```json
 {
+  "flags": "32768",
   "components": [
     {
       "type": 10,
@@ -90,8 +91,7 @@ For example, you can create a message with an Action Row component that contains
         }
       ]
     }
-  ],
-  "flags": "32768"
+  ]
 }
 ```
 
diff --git a/docs/developer-tools/community-resources.mdx b/docs/developer-tools/community-resources.mdx
@@ -37,7 +37,7 @@ Discord does not maintain official SDKs.  The following table is an inexhaustive
 
 ## Interactions
 
-[Interactions](/docs/interactions/receiving-and-responding#) are the great, new way of making a Discord bot. The following open-source libraries provide help for the security and authentication checks that are mandatory if you are receiving Interactions via outgoing webhook. They also include some types for the Interactions data models.
+[Interactions](/docs/interactions/receiving-and-responding) are the great, new way of making a Discord bot. The following open-source libraries provide help for the security and authentication checks that are mandatory if you are receiving Interactions via outgoing webhook. They also include some types for the Interactions data models.
 
 - C#
   - [Discord.Net.Rest](https://github.com/discord-net/Discord.Net)
diff --git a/docs/events/gateway-events.mdx b/docs/events/gateway-events.mdx
@@ -354,7 +354,7 @@ Receive events are Gateway events encapsulated in an [event payload](/docs/event
 | [Integration Create](/docs/events/gateway-events#integration-create)                                         | Guild integration was created                                                                                                                  |
 | [Integration Update](/docs/events/gateway-events#integration-update)                                         | Guild integration was updated                                                                                                                  |
 | [Integration Delete](/docs/events/gateway-events#integration-delete)                                         | Guild integration was deleted                                                                                                                  |
-| [Interaction Create](/docs/events/gateway-events#interaction-create)                                         | User used an interaction, such as an [Application Command](/docs/interactions/application-commands#)                                           |
+| [Interaction Create](/docs/events/gateway-events#interaction-create)                                         | User used an interaction, such as an [Application Command](/docs/interactions/application-commands)                                            |
 | [Invite Create](/docs/events/gateway-events#invite-create)                                                   | Invite to a channel was created                                                                                                                |
 | [Invite Delete](/docs/events/gateway-events#invite-delete)                                                   | Invite to a channel was deleted                                                                                                                |
 | [Message Create](/docs/events/gateway-events#message-create)                                                 | Message was created                                                                                                                            |
@@ -1384,7 +1384,7 @@ Sent when a guild channel's webhook is created, updated, or deleted.
 
 #### Interaction Create
 
-Sent when a user uses an [Application Command](/docs/interactions/application-commands#) or [Message Component](/docs/components/reference#component-object). Inner payload is an [Interaction](/docs/interactions/receiving-and-responding#interaction-object-interaction-structure).
+Sent when a user uses an [Application Command](/docs/interactions/application-commands) or [Message Component](/docs/components/reference#component-object). Inner payload is an [Interaction](/docs/interactions/receiving-and-responding#interaction-object-interaction-structure).
 
 ### Stage Instances
 
diff --git a/docs/interactions/application-commands.mdx b/docs/interactions/application-commands.mdx
@@ -121,7 +121,7 @@ Details about Entry Point command handler types are in the [Entry Point handlers
 
 ## Authorizing Your Application
 
-Application commands do not depend on a bot user in the guild; they use the [interactions](/docs/interactions/receiving-and-responding#) model. To create commands in a guild, your app must be authorized with the `applications.commands` scope which can be used independently, but is also automatically included with the `bot` scope.
+Application commands do not depend on a bot user in the guild; they use the [interactions](/docs/interactions/receiving-and-responding) model. To create commands in a guild, your app must be authorized with the `applications.commands` scope which can be used independently, but is also automatically included with the `bot` scope.
 
 When requesting this scope, we "shortcut" the OAuth2 flow similar to adding a bot. You don't need to complete the flow, exchange for a token, or any of that.
 
diff --git a/docs/resources/application-role-connection-metadata.mdx b/docs/resources/application-role-connection-metadata.mdx
@@ -1,6 +1,6 @@
 # Application Role Connection Metadata
 
-A representation of role connection metadata for an [application](/docs/resources/application#).
+A representation of role connection metadata for an [application](/docs/resources/application).
 
 When a guild has added a bot and that bot has configured its [`role_connections_verification_url`](/docs/resources/application#application-object) (in the developer portal), the application will render as a potential verification method in the guild's role verification configuration.
 
diff --git a/docs/resources/auto-moderation.mdx b/docs/resources/auto-moderation.mdx
@@ -1,6 +1,6 @@
 # Auto Moderation
 
-Auto Moderation is a feature which allows each [guild](/docs/resources/guild#) to set up rules that trigger based on some criteria. For example, a rule can trigger whenever a message contains a specific keyword.
+Auto Moderation is a feature which allows each [guild](/docs/resources/guild) to set up rules that trigger based on some criteria. For example, a rule can trigger whenever a message contains a specific keyword.
 
 Rules can be configured to automatically execute actions whenever they trigger. For example, if a user tries to send a message which contains a certain keyword, a rule can trigger and block the message before it is sent.
 
diff --git a/docs/resources/guild-scheduled-event.mdx b/docs/resources/guild-scheduled-event.mdx
@@ -1,6 +1,6 @@
 # Guild Scheduled Event
 
-A representation of a scheduled event in a [guild](/docs/resources/guild#).
+A representation of a scheduled event in a [guild](/docs/resources/guild).
 
 ### Guild Scheduled Event Object
 
diff --git a/docs/resources/message.mdx b/docs/resources/message.mdx
diff --git a/docs/resources/user.mdx b/docs/resources/user.mdx
diff --git a/docs/rich-presence/using-with-the-game-sdk.mdx b/docs/rich-presence/using-with-the-game-sdk.mdx
diff --git a/docs/topics/oauth2.mdx b/docs/topics/oauth2.mdx
diff --git a/docs/topics/opcodes-and-status-codes.md b/docs/topics/opcodes-and-status-codes.md

Original file line number	Diff line number	Diff line change
`@@ -30,13 +30,13 @@ All content must be sent as components instead of using the standard message for`
`30`	`30`
`31`	`31`	```json
`32`	`32`	`{`
	`33`	`+ "flags": "32768",`
`33`	`34`	`"components": [`
`34`	`35`	`{`
`35`	`36`	`"type": 10,`
`36`	`37`	`"content": "This is a message using the Text Display component"`
`37`	`38`	`},`
`38`		`- ],`
`39`		`- "flags": "32768"`
	`39`	`+ ]`
`40`	`40`	`}`
`41`	`41`	```
`42`	`42`
`@@ -46,6 +46,7 @@ To send a message with multiple components, you can include multiple component o`
`46`	`46`
`47`	`47`	```json
`48`	`48`	`{`
	`49`	`+ "flags": "32768",`
`49`	`50`	`"components": [`
`50`	`51`	`{`
`51`	`52`	`"type": 10,`
`@@ -55,8 +56,7 @@ To send a message with multiple components, you can include multiple component o`
`55`	`56`	`"type": 10,`
`56`	`57`	`"content": "This is another Text Display component!"`
`57`	`58`	`},`
`58`		`- ],`
`59`		`- "flags": "32768"`
	`59`	`+ ]`
`60`	`60`	`}`
`61`	`61`	```
`62`	`62`
`@@ -68,6 +68,7 @@ For example, you can create a message with an Action Row component that contains`
`68`	`68`
`69`	`69`	```json
`70`	`70`	`{`
	`71`	`+ "flags": "32768",`
`71`	`72`	`"components": [`
`72`	`73`	`{`
`73`	`74`	`"type": 10,`
`@@ -90,8 +91,7 @@ For example, you can create a message with an Action Row component that contains`
`90`	`91`	`}`
`91`	`92`	`]`
`92`	`93`	`}`
`93`		`- ],`
`94`		`- "flags": "32768"`
	`94`	`+ ]`
`95`	`95`	`}`
`96`	`96`	```
`97`	`97`