Normalize links (#7475)

Author: JustinBeckwith

docs/activities/building-an-activity.mdx

@@ -71,8 +71,8 @@ Make your app fast, easy to join, and maximize fun to launch a crowd favorite.
 
 ### Keep load times as low as possible
 - This allows for easier drop-in drop-out behavior for the large portion of mobile users on Discord.
-- See the below [Quality & Testing Recommendations](#DOCS_ACTIVITIES_DESIGN_PATTERNS/quality-and-testing) for key areas of minimum quality support and testing recommendations.
-- See the below [Technical Considerations](#DOCS_ACTIVITIES_DESIGN_PATTERNS/technical-considerations) for recommendations on how to partition loading and work with various development tools to reduce load times.
+- See the below [Quality & Testing Recommendations](/docs/activities/design-patterns#quality-and-testing) for key areas of minimum quality support and testing recommendations.
+- See the below [Technical Considerations](/docs/activities/design-patterns#technical-considerations) for recommendations on how to partition loading and work with various development tools to reduce load times.
 - Consider different screen sizes and orientations across desktop and mobile devices and make sure UI elements scale appropriately.
 
 ### Support drop-in, drop-out behavior

docs/activities/design-patterns.mdx

@@ -2,11 +2,11 @@
 
 Activities are web applications that run in an iframe within Discord on desktop, mobile and web. In order to achieve this, we use the [`postMessage`](https://developer.mozilla.org/en-US/docs/Web/API/Window/postMessage) protocol to enable secure communication between your application and Discord.
 
-The [Embedded App SDK](https://github.com/discord/embedded-app-sdk) simplifies this process by managing the `postMessage` protocol on your behalf. For details on available commands and their usage, consult the [SDK Reference](#DOCS_DEVELOPER_TOOLS_EMBEDDED_APP_SDK). Our [Sample Projects](#DOCS_ACTIVITIES_OVERVIEW/sample-projects) provide practical examples of how to implement these features.
+The [Embedded App SDK](https://github.com/discord/embedded-app-sdk) simplifies this process by managing the `postMessage` protocol on your behalf. For details on available commands and their usage, consult the [SDK Reference](/docs/developer-tools/embedded-app-sdk). Our [Sample Projects](/docs/activities/overview#sample-projects) provide practical examples of how to implement these features.
 
 ## Designed for Single-Page Apps (SPAs)
 
-This SDK is intended for use by a single-page application. We recognize developers may be using frameworks or approaches that are not an exact fit for single-page applications. We recommend nesting those frameworks inside your Activity's top-level single-page application and passing messages as you see fit. Please refer to the [Nested Messages App](#DOCS_ACTIVITIES_OVERVIEW/sample-projects) sample project for guidance on this approach.
+This SDK is intended for use by a single-page application. We recognize developers may be using frameworks or approaches that are not an exact fit for single-page applications. We recommend nesting those frameworks inside your Activity's top-level single-page application and passing messages as you see fit. Please refer to the [Nested Messages App](/docs/activities/overview#sample-projects) sample project for guidance on this approach.
 
 ## Activity Lifecycle
 
@@ -20,7 +20,7 @@ This SDK is intended for use by a single-page application. We recognize develope
 ## Sample Code and Activity Lifecycle Diagram
 
 > info
-> Below is a minimal example of setting up the SDK. Please see our [Sample Projects](#DOCS_ACTIVITIES_OVERVIEW/sample-projects) for more complete sample applications.
+> Below is a minimal example of setting up the SDK. Please see our [Sample Projects](/docs/activities/overview#sample-projects) for more complete sample applications.
 
 ```javascript
 import {DiscordSDK} from '@discord/embedded-app-sdk';

docs/activities/development-guides.mdx

@@ -8,16 +8,16 @@ sidebar_label: Overview
 
 **Activities** are multiplayer games and social experiences that can be launched in Discord. Activities can integrate with Discord features like user identity, voice and chat, profile data like Rich Presence, and native monetization.
 
-Under the hood, Activities are single page web apps hosted in an iframe and use the [Embedded App SDK](#DOCS_ACTIVITIES_OVERVIEW/embedded-app-sdk) to communicate with Discord clients. This page focuses on how Activities are launched and built, but you can explore real-world Activities by reading some of our [developer case studies](https://discord.com/build#case-studies), or by trying a few out in Discord. You can also jump right into building using some of the resources below.
+Under the hood, Activities are single page web apps hosted in an iframe and use the [Embedded App SDK](/docs/activities/overview#embedded-app-sdk) to communicate with Discord clients. This page focuses on how Activities are launched and built, but you can explore real-world Activities by reading some of our [developer case studies](https://discord.com/build#case-studies), or by trying a few out in Discord. You can also jump right into building using some of the resources below.
 
 <Container>
-  <Card title="Build Your First Discord Activity" link="#DOCS_ACTIVITIES_BUILDING_AN_ACTIVITY">
+  <Card title="Build Your First Discord Activity" link="/docs/activities/building-an-activity">
     Follow the guide to build your first Activity using the Embedded App SDK.
   </Card>
-  <Card title="Development Patterns" link="#DOCS_ACTIVITIES_DEVELOPMENT_GUIDES">
+  <Card title="Development Patterns" link="/docs/activities/development-guides">
     Explore common development patterns and practices to make building Activities simpler.
   </Card>
-  <Card title="How Activities Work" link="#DOCS_ACTIVITIES_HOW_ACTIVITIES_WORK">
+  <Card title="How Activities Work" link="/docs/activities/how-activities-work">
     Learn more about the lifecycle of Activities and how they run in Discord clients.
   </Card>
 </Container>
@@ -34,41 +34,41 @@ Each of these are covered in more detail in the below sections.
 
 ### Entry Point Command
 
-Activities are primarily opened when users invoke your app's [Entry Point command](#DOCS_INTERACTIONS_APPLICATION_COMMANDS/entry-point-commands) in the App Launcher.
+Activities are primarily opened when users invoke your app's [Entry Point command](/docs/interactions/application-commands#entry-point-commands) in the App Launcher.
 
-When you enable Activities for your app, a [default Entry Point command](#DOCS_INTERACTIONS_APPLICATION_COMMANDS/default-entry-point-command) called "Launch" is created for you. By default, Discord automatically handles opening your Activity when your Entry Point command is run by a user.
+When you enable Activities for your app, a [default Entry Point command](/docs/interactions/application-commands#default-entry-point-command) called "Launch" is created for you. By default, Discord automatically handles opening your Activity when your Entry Point command is run by a user.
 
-Read more about setting up Entry Point commands in the [development guide](#DOCS_ACTIVITIES_DEVELOPMENT_GUIDES/setting-up-an-entry-point-command).
+Read more about setting up Entry Point commands in the [development guide](/docs/activities/development-guides#setting-up-an-entry-point-command).
 
 ### Interaction Response
 
-Activities can be launched in response to [command](#DOCS_INTERACTIONS_OVERVIEW/commands), [message component](#DOCS_INTERACTIONS_OVERVIEW/message-components), and [modal submission](#DOCS_INTERACTIONS_OVERVIEW/modals) interactions. To open an Activity, set the callback type to `LAUNCH_ACTIVITY` (type `12`) when [responding to the interaction](#DOCS_INTERACTIONS_RECEIVING_AND_RESPONDING/responding-to-an-interaction).
+Activities can be launched in response to [command](/docs/interactions/overview#commands), [message component](/docs/interactions/overview#message-components), and [modal submission](/docs/interactions/overview#modals) interactions. To open an Activity, set the callback type to `LAUNCH_ACTIVITY` (type `12`) when [responding to the interaction](/docs/interactions/receiving-and-responding#responding-to-an-interaction).
 
 ---
 
 ## Developing Activities
 
-Whether you're developing a multiplayer game, a new social experience, or another creative idea, your Activity will be built as a web app that is run in an iframe in Discord on desktop, mobile, and web. You can get started by following the guide on [Building an Activity using the Embedded App SDK](#DOCS_ACTIVITIES_BUILDING_AN_ACTIVITY) or exploring the [sample projects](#DOCS_ACTIVITIES_OVERVIEW/sample-projects)
+Whether you're developing a multiplayer game, a new social experience, or another creative idea, your Activity will be built as a web app that is run in an iframe in Discord on desktop, mobile, and web. You can get started by following the guide on [Building an Activity using the Embedded App SDK](/docs/activities/building-an-activity) or exploring the [sample projects](/docs/activities/overview#sample-projects)
 
-The sections below provide an overview of the Embedded App SDK, but technical details about how Activities are run in Discord is covered in [How Activities Work](#DOCS_ACTIVITIES_HOW_ACTIVITIES_WORK).
+The sections below provide an overview of the Embedded App SDK, but technical details about how Activities are run in Discord is covered in [How Activities Work](/docs/activities/how-activities-work).
 
 ### Embedded App SDK
 
-The [Embedded App SDK](#DOCS_DEVELOPER_TOOLS_EMBEDDED_APP_SDK) handles all of the communication between Discord and your app, making it easier to do common tasks like managing connected users, supporting mobile clients, and debugging your Activity. 
+The [Embedded App SDK](/docs/developer-tools/embedded-app-sdk) handles all of the communication between Discord and your app, making it easier to do common tasks like managing connected users, supporting mobile clients, and debugging your Activity. 
 
 The Embedded App SDK offers different events and commands to handle the communication between Discord and your Activity, which are covered more below.
 
 #### Commands
 
 The SDK has a set of commands you can call to interact with a Discord client, given you have the appropriate scopes. This is helpful when you want to do authorize and authenticate users, fetch information about your Activity, or update information for your Activity or an authenticated user.
 
-Read the [Embedded App SDK documentation](#DOCS_DEVELOPER_TOOLS_EMBEDDED_APP_SDK/sdk-commands) for a full list of commands, and details about each command.
+Read the [Embedded App SDK documentation](/docs/developer-tools/embedded-app-sdk#sdk-commands) for a full list of commands, and details about each command.
 
 #### Events
 
 The SDK also has events you can subscribe (or unsubscribe) to for things happening in a connected client that are relevant to your Activity, given you have the appropriate scopes. This is helpful when you want to do things like handle initial connection and thrown errors, listen to updates about a connected user, and listen to events related to your Activity instance.
 
-Read the [Embedded App SDK documentation](#DOCS_DEVELOPER_TOOLS_EMBEDDED_APP_SDK/sdk-events) for a full list of events, and details for each event.
+Read the [Embedded App SDK documentation](/docs/developer-tools/embedded-app-sdk#sdk-events) for a full list of events, and details for each event.
 
 
 ---

docs/activities/how-activities-work.md

@@ -4,11 +4,11 @@ date: "2017-07-19"
 breaking: true
 ---
 
-* [Channel](#DOCS_RESOURCES_CHANNEL/channel-object) Object
+* [Channel](/docs/resources/channel#channel-object) Object
   * `is_private` removed
-  * [`type`](#DOCS_RESOURCES_CHANNEL/channel-object-channel-types) is now an integer
-  * `recipient` is now `recipients`, an array of [user](#DOCS_RESOURCES_USER/user-object) objects
-* [Message](#DOCS_RESOURCES_MESSAGE/message-object) Object
-  * [`type`](#DOCS_RESOURCES_MESSAGE/message-object-message-types) added to support system messages
-* [Status Update](#DOCS_EVENTS_GATEWAY_EVENTS/update-presence-gateway-presence-update-structure) Object
+  * [`type`](/docs/resources/channel#channel-object-channel-types) is now an integer
+  * `recipient` is now `recipients`, an array of [user](/docs/resources/user#user-object) objects
+* [Message](/docs/resources/message#message-object) Object
+  * [`type`](/docs/resources/message#message-object-message-types) added to support system messages
+* [Status Update](/docs/events/gateway-events#update-presence-gateway-presence-update-structure) Object
   * `idle_since` renamed to `since`

docs/activities/overview.mdx

@@ -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.

docs/change-log/2017-07-19-breaking-change-version-6.md

@@ -4,4 +4,4 @@ date: "2017-08-16"
 breaking: true
 ---
 
-The `type` field in the [activity object](#DOCS_EVENTS_GATEWAY_EVENTS/activity-object) for [Gateway Status Update](#DOCS_EVENTS_GATEWAY_EVENTS/update-presence) and [Presence Update](#DOCS_EVENTS_GATEWAY_EVENTS/presence-update) payloads is no longer optional when the activity object is not null.
+The `type` field in the [activity object](/docs/events/gateway-events#activity-object) for [Gateway Status Update](/docs/events/gateway-events#update-presence) and [Presence Update](/docs/events/gateway-events#presence-update) payloads is no longer optional when the activity object is not null.

docs/change-log/2017-07-24-new-feature-audit-logs.md

@@ -3,4 +3,4 @@ title: "New Feature: Emoji Endpoints"
 date: "2017-09-10"
 ---
 
-[Emoji endpoints](#DOCS_RESOURCES_EMOJI/emoji-resource) have been added to the API. Bots can now manage guild emojis to their robo-hearts' content!
+[Emoji endpoints](/docs/resources/emoji#emoji-resource) have been added to the API. Bots can now manage guild emojis to their robo-hearts' content!

docs/change-log/2017-08-16-breaking-change-presence-activity-objects.md

@@ -3,4 +3,4 @@ title: "New Feature: Channel Categories"
 date: "2017-09-20"
 ---
 
-Changes have been made throughout the documentation to reflect the addition of channel categories to Discord. These includes an additional field—`parent_id`—to the base [channel](#DOCS_RESOURCES_CHANNEL/channel-object) object and a new [channel category example](#DOCS_RESOURCES_CHANNEL/channel-object-example-channel-category).
+Changes have been made throughout the documentation to reflect the addition of channel categories to Discord. These includes an additional field—`parent_id`—to the base [channel](/docs/resources/channel#channel-object) object and a new [channel category example](/docs/resources/channel#channel-object-example-channel-category).

docs/change-log/2017-09-10-new-feature-emoji-endpoints.md

@@ -4,4 +4,4 @@ date: "2017-10-16"
 breaking: true
 ---
 
-[API](#DOCS_REFERENCE/api-versioning) and Gateway versions below v6 are now discontinued after being previously deprecated. Version 6 is now the default API and Gateway version. Attempting to use a version below 6 will result in an error.
+[API](/docs/reference#api-versioning) and Gateway versions below v6 are now discontinued after being previously deprecated. Version 6 is now the default API and Gateway version. Attempting to use a version below 6 will result in an error.

docs/change-log/2017-09-20-new-feature-channel-categories.md

@@ -9,4 +9,4 @@ Rich Presence is now live and available for all developers! Rich Presence allows
 * Allowing users to post invitations to join their party or spectate their game in chat
 * Displaying "Spectate" and "Ask to Join" buttons on users' profiles
 
-For more information, check out our [Rich Presence site](https://discord.com/rich-presence). To get started on development, [read the docs](#DOCS_RICH_PRESENCE_OVERVIEW)!
+For more information, check out our [Rich Presence site](https://discord.com/rich-presence). To get started on development, [read the docs](/docs/rich-presence/overview)!

docs/change-log/2017-10-16-breaking-change-api-gateway-below-v6-discontinued.md

@@ -4,4 +4,4 @@ date: "2018-01-03"
 breaking: true
 ---
 
-Additional sharding requirements and information for bots in over 100,000 guilds has been added. This requires a small change in numbers of shards for affected bots. See the [documentation](#DOCS_EVENTS_GATEWAY/sharding-for-large-bots) for more information.
+Additional sharding requirements and information for bots in over 100,000 guilds has been added. This requires a small change in numbers of shards for affected bots. See the [documentation](/docs/events/gateway#sharding-for-large-bots) for more information.

docs/change-log/2017-11-09-new-feature-rich-presence.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.

docs/change-log/2018-01-03-semi-breaking-change-very-large-bot-sharding.md

@@ -3,4 +3,4 @@ title: "Enhancement: Get Guild Emoji Endpoint"
 date: "2018-01-30"
 ---
 
-The [Get Guild Emoji](#DOCS_RESOURCES_EMOJI/get-guild-emoji) response now also includes a user object if the emoji was added by a user.
+The [Get Guild Emoji](/docs/resources/emoji#get-guild-emoji) response now also includes a user object if the emoji was added by a user.

docs/change-log/2018-01-23-deprecation-accept-invite-endpoint.md

@@ -3,4 +3,4 @@ title: "Enhancement: New Message Properties"
 date: "2018-02-05"
 ---
 
-Additional `activity` and `application` fields—as well as corresponding object documentation—have been added to the [Message](#DOCS_RESOURCES_MESSAGE/message-object) object in support of our newly-released [Spotify integration](https://support.discord.com/hc/en-us/articles/360000167212-Discord-Spotify-Connection) and previous Rich Presence enhancements.
+Additional `activity` and `application` fields—as well as corresponding object documentation—have been added to the [Message](/docs/resources/message#message-object) object in support of our newly-released [Spotify integration](https://support.discord.com/hc/en-us/articles/360000167212-Discord-Spotify-Connection) and previous Rich Presence enhancements.

docs/change-log/2018-01-30-enhancement-get-guild-emoji-endpoint.md

@@ -3,4 +3,4 @@ title: "Documentation Fix: List of Open DMS in Certain Payloads"
 date: "2018-06-19"
 ---
 
-The documentation has been updated to correctly note that the `private_channels` field in the [Ready](#DOCS_EVENTS_GATEWAY_EVENTS/ready) should be an empty array, as well as the response from `/users/@me/channels` for a bot user. This change has been in effect for a long time, but the documentation was not updated.
+The documentation has been updated to correctly note that the `private_channels` field in the [Ready](/docs/events/gateway-events#ready) should be an empty array, as well as the response from `/users/@me/channels` for a bot user. This change has been in effect for a long time, but the documentation was not updated.

docs/change-log/2018-02-05-enhancement-new-message-properties.md

@@ -3,4 +3,4 @@ title: "Enhancement: User Object"
 date: "2018-11-30"
 ---
 
-The [User object](#DOCS_RESOURCES_USER/user-object) now includes two new additional fields, `premium_type` and `flags`. These can be used to know the Nitro status of a user, or determine which HypeSquad house a user is in.
+The [User object](/docs/resources/user#user-object) now includes two new additional fields, `premium_type` and `flags`. These can be used to know the Nitro status of a user, or determine which HypeSquad house a user is in.

docs/change-log/2018-06-19-documentation-fix-list-of-open-dms-in-certain-payloads.md

@@ -3,4 +3,4 @@ title: "New Invite Object Fields"
 date: "2019-04-18"
 ---
 
-The [Invite Object](#DOCS_RESOURCES_INVITE/invite-object) now includes two additional fields, `target_user` and `target_user_type`.
+The [Invite Object](/docs/resources/invite#invite-object) now includes two additional fields, `target_user` and `target_user_type`.