Updates unavailable links

guide/additional-features/cooldowns.md

@@ -3,7 +3,7 @@
 Spam is something you generally want to avoid, especially if one of your commands require calls to other APIs or takes a bit of time to build/send.
 
 ::: tip
-This section assumes you followed the [Command Handling](/creating-your-bot/command-handling.md) part.
+This section assumes you followed the [Command Handling](/guide/creating-your-bot/command-handling.md) part.
 :::
 
 First, add a cooldown property to your command. This will determine how long the user would have to wait (in seconds) before using the command again.
@@ -22,7 +22,7 @@ module.exports = {
 };
 ```
 
-In your main file, initialize a [Collection](/additional-info/collections.md) to store cooldowns of commands:
+In your main file, initialize a [Collection](/guide/additional-info/collections.md) to store cooldowns of commands:
 
 ```js
 client.cooldowns = new Collection();
@@ -93,4 +93,4 @@ This line causes the entry for the user under the specified command to be delete
 
 ## Resulting code
 
-<ResultingCode path="additional-features/cooldowns" />
+<ResultingCode path="additional-features/cooldowns" />

guide/additional-features/reloading-commands.md

@@ -7,7 +7,7 @@ ESM does not support require and clearing import cache. You can use [hot-esm](ht
 :::
 
 ::: tip
-This section assumes you followed the [Command Handling](/creating-your-bot/command-handling.md) part.
+This section assumes you followed the [Command Handling](/guide/creating-your-bot/command-handling.md) part.
 :::
 
 ::: warning
@@ -69,4 +69,4 @@ The snippet above uses a `try...catch` block to load the command file and add it
 
 ## Resulting code
 
-<ResultingCode path="additional-features/reloading-commands" />
+<ResultingCode path="additional-features/reloading-commands" />

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

@@ -66,7 +66,7 @@ discord.js v13 makes the switch to Discord API v9! In addition to this, the new
 ## Slash commands
 
 discord.js now has support for slash commands!
-Refer to the [slash commands](/interactions/slash-commands.html) section of this guide to get started.
+Refer to the [slash commands](/guide/interactions/slash-commands.html) section of this guide to get started.
 
 In addition to the `interactionCreate` event covered in the above guide, this release also includes the new Client events `applicationCommandCreate`, `applicationCommandDelete`, and `applicationCommandUpdate`.
 
@@ -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](/guide/message-components/buttons.md) section of this guide to get started.
 
 ## Threads
 

guide/creating-your-bot/README.md

@@ -28,7 +28,7 @@ console.log(token);
 ::::
 
 ::: danger
-If you're using Git, you should not commit this file and should [ignore it via `.gitignore`](/creating-your-bot/#git-and-gitignore).
+If you're using Git, you should not commit this file and should [ignore it via `.gitignore`](/guide/creating-your-bot/README.md#git-and-gitignore).
 :::
 
 ## Using environment variables
@@ -127,4 +127,4 @@ config.json
 Aside from keeping credentials safe, `node_modules` should be included here. Since this directory can be restored based on the entries in your `package.json` and `package-lock.json` files by running `npm install`, it does not need to be included in Git.
 
 You can specify quite intricate patterns in `.gitignore` files, check out the [Git documentation on `.gitignore`](https://git-scm.com/docs/gitignore) for more information!
-:::
+:::

guide/creating-your-bot/main-file.md

@@ -1,7 +1,7 @@
 # Creating the main file
 
 ::: tip
-This page assumes you've already prepared the [configuration files](/creating-your-bot/#creating-configuration-files) from the previous page. We're using the `config.json` approach, however feel free to substitute your own!
+This page assumes you've already prepared the [configuration files](/guide/creating-your-bot/#creating-configuration-files) from the previous page. We're using the `config.json` approach, however feel free to substitute your own!
 :::
 
 Open your code editor and create a new file. We suggest that you save the file as `index.js`, but you may name it whatever you wish.
@@ -37,7 +37,7 @@ Intents also define which events Discord should send to your bot, and you may wi
 
 ## Running your application
 
-Open your terminal and run `node index.js` to start the process. If you see "Ready!" after a few seconds, you're good to go! The next step is to start adding [slash commands](/creating-your-bot/slash-commands.md) to develop your bot's functionality.
+Open your terminal and run `node index.js` to start the process. If you see "Ready!" after a few seconds, you're good to go! The next step is to start adding [slash commands](/guide/creating-your-bot/slash-commands.md) to develop your bot's functionality.
 
 ::: tip
 You can open your `package.json` file and edit the `"main": "index.js"` field to point to your main file. You can then run `node .` in your terminal to start the process!
@@ -47,4 +47,4 @@ After closing the process with `Ctrl + C`, you can press the up arrow on your ke
 
 #### Resulting code
 
-<ResultingCode path="creating-your-bot/initial-files" />
+<ResultingCode path="creating-your-bot/initial-files" />