chore: rename from message components to interactive components

Author: almostSouji

guide/additional-info/changes-in-v13.md

@@ -75,7 +75,7 @@ In addition to the `interactionCreate` event covered in the above guide, this re
 discord.js now has support for message components!
 This introduces the `MessageActionRow`, `MessageButton`, and `MessageSelectMenu` classes, as well as associated interactions and collectors. 
 
-Refer to the [message components](/message-components/buttons.md) section of this guide to get started.
+Refer to the [message components](/interactive-components/buttons.md) section of this guide to get started.
 
 ## Threads
 
@@ -1136,7 +1136,7 @@ A Collection of Roles which are managed by the integration.
 
 Provides gateway support for slash command and message component interactions. 
 
-For more information refer to the [slash commands](/interactions/slash-commands.md#replying-to-slash-commands) and [message components](/message-components/buttons) sections of the guide.
+For more information refer to the [slash commands](/interactions/slash-commands.md#replying-to-slash-commands) and [message components](/interactive-components/buttons) sections of the guide.
 
 ### InteractionCollector
 

guide/creating-your-bot/command-deployment.md

@@ -134,7 +134,7 @@ You've successfully sent a response to a slash command! However, this is only th
 * utilising the different [Response methods](/slash-commands/response-methods.md) that can be used for slash commands.
 * expanding on these examples with additional validated option types in [Advanced command creation](/slash-commands/advanced-creation.md).
 * adding formatted [Embeds](/popular-topics/embeds.md) to your responses.
-* enhancing the command functionality with [Buttons](/message-components/buttons) and [Select Menus](/message-components/select-menus).
+* enhancing the command functionality with [Buttons](/interactive-components/buttons) and [Select Menus](/interactive-components/select-menus).
 * prompting the user for more information with [Modals](/interactions/modals.md).
 
 #### Resulting code

guide/message-components/action-rows.md renamed to guide/interactive-components/action-rows.md

@@ -3,7 +3,7 @@
 The first type of interactive component we'll cover creating is a Button. Buttons are available in a variety of styles and can be used to provide permanent interfaces, temporary confirmation workflows, and other forms of additional interaction with your bot.
 
 ::: tip
-This page is a follow-up to the [slash commands](/slash-commands/advanced-creation) section and [action rows](/message-components/action-rows) page. Please carefully read those pages first so that you can understand the methods used here.
+This page is a follow-up to the [slash commands](/slash-commands/advanced-creation) section and [action rows](/interactive-components/action-rows) page. Please carefully read those pages first so that you can understand the methods used here.
 :::
 
 ## Building buttons
@@ -169,4 +169,4 @@ const button = new ButtonBuilder()
 
 #### Next steps
 
-That's everything you need to know about building and sending buttons! From here you can learn about the other type of message component, [select menus](/message-components/select-menus), or have your bot start listening to [component interactions](/message-components/interactions) from your buttons. 
+That's everything you need to know about building and sending buttons! From here you can learn about the other type of message component, [select menus](/interactive-components/select-menus), or have your bot start listening to [component interactions](/interactive-components/interactions) from your buttons. 

guide/message-components/buttons.md renamed to guide/interactive-components/buttons.md

@@ -7,7 +7,7 @@ Every button click or select menu selection on a component sent by your bot fire
 - Creating a permanent component handler in the <DocsLink path="Client:Class#interactionCreate" /> event.
 
 ::: tip
-This page is a follow-up to the [slash commands](/slash-commands/advanced-creation) section, and assumes you have created either [buttons](/message-components/buttons) or [select menus](/message-components/select-menus) as detailed in this guide. Please carefully read those pages first so that you can understand the methods used here.
+This page is a follow-up to the [slash commands](/slash-commands/advanced-creation) section, and assumes you have created either [buttons](/interactive-components/buttons) or [select menus](/interactive-components/select-menus) as detailed in this guide. Please carefully read those pages first so that you can understand the methods used here.
 :::
 
 ## Responding to component interactions
@@ -32,7 +32,7 @@ Once `deferUpdate()` has been called, future messages can be sent by calling `fo
 
 ## Awaiting components
 
-If you followed our [buttons](/message-components/buttons) guide, the confirmation workflow for the `ban` command is a good example of a situation where your bot is expecting to receive a single response, from either the Confirm or Cancel button.
+If you followed our [buttons](/interactive-components/buttons) guide, the confirmation workflow for the `ban` command is a good example of a situation where your bot is expecting to receive a single response, from either the Confirm or Cancel button.
 
 Begin by adding `withResponse` to the options, and then calling <DocsLink path="Message:Class#awaitMessageComponent" type="method" /> on the message. This method returns a [Promise](/additional-info/async-await.md) that resolves when any interaction passes its filter (if one is provided), or throws if none are received before the timeout. If this happens, remove the components and notify the user.
 
@@ -82,7 +82,7 @@ try {
 
 ## Component collectors
 
-For situations where you want to collect multiple interactions, the Collector approach is better suited than awaiting singular interactions. Following on from the [select menus](/message-components/select-menus) guide, you're going to extend that example to use an <DocsLink path="InteractionCollector:Class"/> to listen for multiple <DocsLink path="StringSelectMenuInteraction:Class"/>s.
+For situations where you want to collect multiple interactions, the Collector approach is better suited than awaiting singular interactions. Following on from the [select menus](/interactive-components/select-menus) guide, you're going to extend that example to use an <DocsLink path="InteractionCollector:Class"/> to listen for multiple <DocsLink path="StringSelectMenuInteraction:Class"/>s.
 
 Begin by adding `withResponse` to the options, and then calling <DocsLink path="Message:Class#createMessageComponentCollector" type="method" /> on this instance. This method returns an InteractionCollector that will fire its <DocsLink path="InteractionCollector:Class#collect" /> event whenever an interaction passes its filter (if one is provided).
 

guide/message-components/images/select.png renamed to guide/interactive-components/images/select.png

@@ -3,7 +3,7 @@
 Select menus are one of the `MessageComponent` classes, which can be sent via messages or interaction responses.
 
 ::: tip
-This page is a follow-up to the [slash commands](/slash-commands/advanced-creation.md) section and [action rows](/message-components/action-rows.md) page. Please carefully read those pages first so that you can understand the methods used here.
+This page is a follow-up to the [slash commands](/slash-commands/advanced-creation.md) section and [action rows](/interactive-components/action-rows.md) page. Please carefully read those pages first so that you can understand the methods used here.
 :::
 
 ## Building string select menus

guide/message-components/interactions.md renamed to guide/interactive-components/interactions.md

@@ -51,7 +51,7 @@ const data = new SlashCommandBuilder()
 	.setDefaultMemberPermissions(PermissionFlagsBits.KickMembers);
 ```
 
-In reality, you'll probably want to have an additional confirmation step before a ban actually executes. Check out the [button components section](/message-components/buttons) of the guide to see how to add confirmation buttons to your command responses, and listen to button clicks.
+In reality, you'll probably want to have an additional confirmation step before a ban actually executes. Check out the [button components section](/interactive-components/buttons) of the guide to see how to add confirmation buttons to your command responses, and listen to button clicks.
 
 ## Contexts
 

guide/message-components/select-menus.md renamed to guide/interactive-components/select-menus.md

@@ -45,8 +45,8 @@ All content has been updated to use discord.js v14 syntax. The v13 version of th
 
 - [Updating from v13 to v14](/additional-info/changes-in-v14.md): A list of the changes from discord.js v13 to v14
 - [Slash commands](/slash-commands/advanced-creation.md): Registering, replying to slash commands and permissions
-- [Buttons](/message-components/buttons): Building, sending, and receiving buttons
-- [Select menus](/message-components/select-menus): Building, sending, and receiving select menus
+- [Buttons](/interactive-components/buttons): Building, sending, and receiving buttons
+- [Select menus](/interactive-components/select-menus): Building, sending, and receiving select menus
 - [Threads](/popular-topics/threads.md): Creating and managing threads
 - [Formatters](/popular-topics/formatters.md): A collection of formatters to use with your bot