Format files and fix hyperlinks

Author: WhoIsConch

docs/Extensions/Commands/cogs.mdx

@@ -106,12 +106,12 @@ access the `bot` variable outside of a function. To make an event, you have to u
 method, `@commands.Cog.listener()`. Events also need `self` as its first parameter.
 
 And that's it! Cogs are a simple and easy way of organizing your code. Now you can check out how to
-create a help command [here](help-command.mdx)
+create a help command [here](help-command)
 
 :::info Related Topics
 
-- [Creating a Help Command](help-command.mdx)
-- [Rules and Common Practices](../Getting-Started/rules-and-common-practices.mdx)
-- [Prefixed Commands](prefixed-commands.mdx)
+- [Creating a Help Command](help-command)
+- [Rules and Common Practices](../../Getting-Started/rules-and-common-practices)
+- [Prefixed Commands](prefixed-commands)
 
 :::

docs/Extensions/Commands/groups.mdx

@@ -43,7 +43,7 @@ async def subtract(ctx, a: int, b: int):
 
 :::info Related Topics
 
-- [Prefixed Commands](prefixed-commands.mdx)
-- [Cogs](cogs.mdx)
+- [Prefixed Commands](prefixed-commands)
+- [Cogs](cogs)
 
 :::

docs/Extensions/Commands/help-command.mdx

@@ -469,8 +469,8 @@ Thanks to InterStella0 for making this guide amazing.
 
 :::info Related Topics
 
-- [Subclassing Bots](../Popular-Topics/subclassing-bots.mdx)
-- [Prefixed Commands](prefixed-commands.mdx)
-- [Cogs](cogs.mdx)
+- [Subclassing Bots](../../Popular-Topics/subclassing-bots)
+- [Prefixed Commands](prefixed-commands)
+- [Cogs](cogs)
 
 :::

docs/Extensions/Commands/prefixed-commands.mdx

@@ -308,7 +308,7 @@ with `int(guess)`.
 
 :::info Related Topics
 
-- [Command Groups](groups.mdx)
-- [Rules and Common Practices](../Getting-Started/rules-and-common-practices.mdx)
+- [Command Groups](groups)
+- [Rules and Common Practices](../../Getting-Started/rules-and-common-practices)
 
 :::

docs/Getting-Started/hosting-your-bot.mdx

@@ -2,10 +2,13 @@
 title: Hosting Your Pycord Bot
 ---
 
+import Tabs from "@theme/Tabs";
+import TabItem from "@theme/TabItem";
+
 # Hosting Your Pycord Bot
 
 If you're completely new to this, you might have thought something along the lines of "Yay! I got my
-bot working," after following our [Creating your First Bot](creating-your-first-bot.mdx) guide, only
+bot working," after following our [Creating your First Bot](creating-your-first-bot) guide, only
 to close your IDE or shut down your computer to find your bot offline.
 
 The reason for this is that programs have to be hosted somewhere, meaning some machine somewhere has
@@ -39,9 +42,9 @@ There are three types of hosts.
  <TabItem value="hosttype-shared" label="Shared Hosting">
  Shared hosting is a type of hosting where multiple people share one VPS. Getting a spot on
  a shared host is usually cheap, sometimes even free. Shared hosts do not give you a lot of 
- resources, from less than 4 gigabytes of RAM and half of a CPU, with very little storage. 
- Shared hosting is usually used for website hosting and is not recommended for hosting a Discord
- bot.
+ resources, from less than a gigabyte of RAM (usually 512mb on free hosts) and half of a CPU 
+ with very little storage. Shared hosting is usually used for website hosting and is not 
+ recommended for hosting a Discord bot.
  </TabItem>
  <TabItem value="hosttype-vps" label="VPS" default>
  A virtual private server (VPS) is a virtual computer (virtual machine) that is rented out to
@@ -58,6 +61,7 @@ There are three types of hosts.
  large projects and are overkill for something like a Discord bot.
  </TabItem>
 </Tabs>
+<br/>
 
 :::danger
 
@@ -87,7 +91,7 @@ the bot.
 
 :::warning
 
-If you are using SSH and run the file, your bot will not stay running. This is because the file is
+If you are using SSH to run the file, your bot will not stay running. This is because the file is
 only told to run during your session. You can use a command like [nohup](https://en.wikipedia.org/wiki/Nohup)
 to make sure your file stays running after you disconnect.
 

docs/Getting-Started/rules-and-common-practices.mdx

@@ -5,7 +5,7 @@ title: Rules and Common Practices
 # Rules and Common Practices of Creating a Bot
 
 When creating almost anything, there's always a certain set of rules to follow or common practices,
-such as (PEP8)[https://www.python.org/dev/peps/pep-0008/] for Python. This applies for creating bots
+such as [PEP8](https://www.python.org/dev/peps/pep-0008/) for Python. This applies for creating bots
 with Pycord as well.
 
 :::note
@@ -56,12 +56,12 @@ about it. I'm here to tell you that it isn't a good idea to shard your bot.
 
 *Wait a minute, why would it be an option if it wasn't a good idea?* It's simple. I lied. Sort of.
 I'm not going to go into the details of sharding a bot, so you can read about it on
-[this page](../Topics/sharding.mdx). Basically, though, sharding is the process of taking your bot
+[this page](../Popular-Topics/sharding). Basically, though, sharding is the process of taking your bot
 and breaking it up into small pieces so it's easier to perform tasks. This is very useful for large
 bots, as it makes them faster and more reliable. Sharding is not a good practice for small bots.
 
 :::note
-Discord itself will actually notify you once your bot is ready for sharding.
+Discord will notify you once it is time to shard your bot, and will eventually force you to do so.
 :::
 
 At the very least, wait for one thousand servers to shard your bot. If you shard your bot while it's
@@ -85,18 +85,18 @@ While it may take some time, subclassing a bot is very worth it. Once again, thi
 elsewhere so I won't go into the details, but I felt it fit here so I put it here.
 
 Subclassing a bot makes it more flexible and allows it to do a lot more. Read more about subclassing
-bots [here](../Topics/subclassing-bots.mdx)
+bots [here](../Topics/subclassing-bots)
 
 ### Your Bot's Token
 
 Your bot is only able to be run for one reason: its token. If you followed the 
-[guide for creating your first bot](creating-your-first-bot.mdx), you should already know a bit about
+[guide for creating your first bot](creating-your-first-bot), you should already know a bit about
 keeping that token safe. That's exactly what you want to do.
 
 Sharing your token is never good. If someone evil gets a hold of your token, they can do terrible things,
 such as making your bot leave all of its servers, spamming all of the members the bot has contact with,
 and even manipulating the servers the bot is in, if given the permissions. That's why it's very important
-to keep your token safe. To learn how to do so, read [this part](creating-your-first-bot.mdx#Tokens) of
+to keep your token safe. To learn how to do so, read [this part](creating-your-first-bot#Tokens) of
 the Creating Your First Bot guide.
 
 ### Backups

docs/Interactions/buttons.mdx

@@ -25,7 +25,7 @@ So, let's see how you can add buttons to your bot!
 
 Buttons weren't the only update to the interactions system in Discord. Discord also added drop-down menus, called Select Menus. Discord is also still working on more interaction elements!
 
-These UI elements reside in a "view". To learn more about views, please refer to the (interactions page.)[index.mdx]
+These UI elements reside in a "view". To learn more about views, please refer to the [interactions page.](index)
 
 ## Usage Syntax
 
@@ -299,7 +299,7 @@ That is up to you. Buttons do provide a cleaner interface for your bot, and are
 
 :::info Related Topics
 
-- [Slash Commands](slash-commands.mdx)
-- [Interactions Index](index.mdx)
+- [Slash Commands](slash-commands)
+- [Interactions Index](index)
 
 :::

docs/Interactions/context-menus.mdx

@@ -109,7 +109,7 @@ async def is_this_msg_sus(ctx, message: discord.Message): # message commands re
 
 :::info Related Topics
 
-- [Slash Commands](slash-commands.mdx)
-- [Interactions Index](index.mdx)
+- [Slash Commands](slash-commands)
+- [Interactions Index](index)
 
 :::

docs/Interactions/dropdowns.mdx

@@ -11,8 +11,8 @@ Menus. This guide will show you the easy and painless ways of using them with Py
 
 ## Concept
 
-Select Menus aren't the only message component in Discord. There are also [Buttons](buttons.mdx) and
-[Text Modals](modals.mdx). Select Menus make it easy for users to pick one or multiple options from
+Select Menus aren't the only message component in Discord. There are also [Buttons](buttons) and
+[Text Modals](modals). Select Menus make it easy for users to pick one or multiple options from
 a list provided by a bot.
 
 ```py
@@ -101,7 +101,7 @@ skills, as Pycord requires a bit of Python experience.
 
 :::info Related Topics
 
-- [Slash Commands](slash-commands.mdx)
-- [Interactions Index](index.mdx)
+- [Slash Commands](slash-commands)
+- [Interactions Index](index)
 
 :::

docs/Interactions/index.mdx

@@ -14,13 +14,13 @@ import "@discord-message-components/react/styles";
 Back in the December 2020, Discord released their first interaction: the slash command.
 Since then, Discord has added and updated Interactions a lot. Different types of Interactions are:
 
-****Message Components****
+**Message Components**
 
 - **Buttons**: buttons that can be clicked on to perform an action
 - **Select Menus**: Dropdowns used to select an option from a list of options
 - **Modals**: Form-like modals that can be used to ask for input
 
-****Application Commands****
+**Application Commands**
 
 - **Slash Commands**: Commands that can be used to perform an action
 - **Context Menu Commands**
@@ -69,32 +69,33 @@ things with buttons, such as calculators, games, and more!
 <br />
 
 This is what a Button looks like. Very simple and modern. To learn more about buttons, refer to our
-(buttons page)[buttons.mdx].
+[buttons page](buttons).
 
 ### Select Menus
 
 Select Menus are the second of Discord's Message Components. They allow for quick choices by the
 user that your bot can use. Select Menus are good for things such as choosing features, pages of a
 help menu, and more.
 
-[Insert Select Menu example]
+<!-- [Insert Select Menu example] -->
 
 This is what a Select Menu looks like. While not looking as good as Buttons, they still look great
-and have even greater possibilities. To learn more about Select Menus, please refer to our (Select
-Menus page)[dropdowns.mdx].
+and have even greater possibilities. To learn more about Select Menus, please refer to our [Select
+Menus page](dropdowns).
 
 ### Text Modals
 
 Text Modals are the most recent Message Component in Discord. They're useful for text input and
 filling out forms such as a sign-up for your bot's service. These are meant to replace long bot setup
 processes by allowing users to fill out a form, as well as replace having to make the user send
-messages that the bot uses in general. Due to the upcoming (Message Content Intent)[topics/intents.mdx],
+messages that the bot uses in general. Due to the upcoming [Message Content Intent](../Popular-Topics/intents),
 verified bots will be forced to use Discord's new interactions system instead of messages. Text Modals
 are opened by clicking on a button.
 
-[Text Modal example?]
+<!-- [Text Modal example?] -->
 
-This is what a Text Modal looks like. Easy to use and one of the most useful Message Components yet.
+This is what a Text Modal looks like. Easy to use and one of the most useful Message Components yet. To
+learn more about text modals, please visit our [Text Modals page](text-modals)
 
 ## Application Commands
 
@@ -148,14 +149,14 @@ are useful for having a function to add a user to a ticket, warn a user, and mor
 
 This is a Message Command:
 
-[Message Command Example]
+<!-- [Message Command Example] -->
 
 And this is a User Command:
 
-[User Command Example]
+<!-- [User Command Example] -->
 
-Pretty cool, right? To learn more about these two, please read the (Message and User Commands guide)
-[message-user-commands.mdx]
+Pretty cool, right? To learn more about these two, please read the [Message and User Commands guide]
+(message-user-commands)
 
 ## Application Commands vs. Prefix Commands