Merge pull request #247 from BPS-Circular-API/main

Fix minor grammatical errors within the docs

Author: Lulalaby

docs/extensions/commands/help-command.mdx

@@ -359,7 +359,7 @@ class MyHelp(commands.HelpCommand):
         await self.get_destination().send(embed=embed)
 ```
 
-Add all of these methods together and you have a fully functioning help command!
+Add all of these methods together, and you have a fully functioning help command!
 
 <details>
 <summary>Click to see the final code for this section</summary>

docs/extensions/tasks/tasks.mdx

@@ -82,7 +82,7 @@ at the specified time(s).
 to make it run forever which is also the default.
 4.  The loop function ***must*** be a coroutine.
 
-These are all really useful and they aren't the only parameters so if you wanna know more about them check out the
+These are all really useful, and they aren't the only parameters so if you want to know more about them check out the
 [docs](https://docs.pycord.dev/en/master/ext/tasks/index.html#discord.ext.tasks.loop)!
 
 ### Attributes
@@ -103,7 +103,7 @@ Now let's create a cog that handles a leaderboard we have in our bot using Tasks
 also provide a refresher of how slash commands groups work in cogs.
 
 For the sake of this example let's pretend that we have a leaderboard module that does all the leaderboard handling for
-us and that computing the leaderboard is very expensive computationally wise so we want to store one version of it that
+us and that computing the leaderboard is very expensive computationally wise, so we want to store one version of it that
 gets regularly updated instead of generating it every time someone calls the `/leaderboard view` command.
 ```py
 from discord.ext import tasks, commands
@@ -183,29 +183,29 @@ Now to explain what's going on:
 First things first we create a cog and in its `__init__` function we start the `update_leaderboard` task and generate
 the first instance of our leaderboard's embed.
 
-After that, we define the `update_leaderboard` task using the `loop` decorator and we make it run every ten minutes by
+After that, we define the `update_leaderboard` task using the `loop` decorator, and we make it run every ten minutes by
 passing 10 to the `minutes` parameter.
 
-Then that we define the `before_update_leaderboard` task using the `before_loop` decorator and we make it wait until the
+Then that we define the `before_update_leaderboard` task using the `before_loop` decorator, and we make it wait until the
 bot is ready before starting the task.
 
-Next up we define the `after_update_leaderboard` task using the `after_loop` decorator and we make it clean up the
+Next up we define the `after_update_leaderboard` task using the `after_loop` decorator, and we make it clean up the
 leaderboard when the loop finally stops running.
 
-Then we define the `update_leaderboard_error` task using the `error` decorator and we make it print any errors that may
+Then we define the `update_leaderboard_error` task using the `error` decorator, and we make it print any errors that may
 occur while we update our leaderboard to the console.
 
 Then we get into the fun stuff, we create a slash command group using the `SlashCommandGroup` class and name it
 `leaderboard`, we then create the `view` sub-command which sends the embed generated when the leaderboard is updated and
-`update_info` which shows a lot of data about the task using some of the attributes and functions available to us.
+`update_info` which shows a lot of data about the task using some attributes and functions available to us.
 
 We also create a slash command group called `leaderboard_config` which is only available to the owner of the bot.
 
 Then we create the `set_time_between_updates` sub-command which takes in the time in minutes and changes the time
 between updates of the leaderboard using the `change_interval` method, the `stop` sub-command which stops the task using
 the `stop` method and `restart` which restarts the task using the `restart` method.
 
-Finally, we add the `LeaderboardCog` cog to the bot and we're done!
+Finally, we add the `LeaderboardCog` cog to the bot, and we're done!
 
 I'd highly recommend you check the tasks extension
 [documentation](https://docs.pycord.dev/en/master/ext/tasks/index.html) for more info on how to use them and what other

docs/getting-started/more-features.mdx

@@ -21,7 +21,7 @@ So, you just created your first Pycord bot! Now, let's add some more features to
 
 ### Event Handlers
 
-Events in Discord are a way to listen for certain actions. For example, if you want to know when a user joins your server so you could send a welcome message, you can use the `on_member_join` event.
+Events in Discord are a way to listen for certain actions. For example, if you want to know when a user joins your server, so you could send a welcome message, you can use the `on_member_join` event.
 
 First, you need to ask Discord to send you events. This is done via "Intents". Read up the [Intents](../Popular-Topics/intents) page for more information.
 
@@ -203,7 +203,7 @@ embed.add_field(title="Inline Field 3", value="Inline Field 3", inline=True)
 
 This small section shows off embed fields. You can add fields to embeds with the [`add_field` method](https://docs.pycord.dev/en/master/api.html#discord.Embed.add_field)
 of the [`discord.Embed`](https://docs.pycord.dev/en/master/api.html#embed) class. These consist of three 
-keyword arguments: `title`, `value`, and `inline`. `title` and `value` are both required arguments, which inline defaults to `False` if it's not defined. The `inline` argument specifies whether or not space will be divided among the inline fields. There could be a mix of fields where inline has different values too.
+keyword arguments: `title`, `value`, and `inline`. `title` and `value` are both required arguments, which inline defaults to `False` if it's not defined. The `inline` argument specifies whether space will be divided among the inline fields. There could be a mix of fields where inline has different values too.
 
 ```py
 embed.set_footer(text="Footer! No markdown here.") # footers can have icons too
@@ -324,7 +324,7 @@ by using the following syntax:
 Inside the supported elements that have just been mentioned,
 the example above will look like this: [`Pycord`](https://pycord.dev/)
 
-Outside of them, the link will still be clickable but the formatting will be ignored,
+Outside them, the link will still be clickable but the formatting will be ignored,
 therefore the example above will look similarly to this: `[Pycord](https://pycord.dev/)`
 
 #### Embed Markdown

docs/getting-started/rules-and-common-practices.mdx

@@ -59,7 +59,7 @@ 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](../Popular-Topics/sharding). 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
+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
@@ -84,7 +84,7 @@ will be denied simply because you applied for an intent you didn't need.
 ### Subclassing
 
 While it may take some time, subclassing a bot is very worth it. Once again, this was explained 
-elsewhere so I won't go into the details, but I felt it fit here so I put it here.
+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](../Popular-Topics/subclassing-bots)
@@ -96,7 +96,7 @@ Your bot is only able to be run for one reason: its token. If you followed the
 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,
+such as making your bot leave all of its servers, spamming all 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#tokens) of
 the Creating Your First Bot guide.
@@ -106,13 +106,13 @@ the Creating Your First Bot guide.
 You always want to back up your bot's data. This includes both its code *and* its databases. This way,
 if something tragic happens, such as your host failing a data migration or you breaking your Raspberry
 Pi's SD card that held your bot, you'll still have its precious user data. I have a small program for
-my bot that uploads its databases to a remote GitHub repository every now and then to not lose any data.
+my bot that uploads its databases to a remote GitHub repository periodically to not lose any data.
 It may be smarter to find a bit more of a reliable way to do so, though.
 
 Public or private, having a local Git repository connected to a remote one is a good idea for making
 almost any application. For a lot of developers, it's like saving your work. If you do this, all of
-your bot's code won't be lost if your computer spontaneously combusts or you smash it to bits from 
-anger. You can simply grab the backup computer that everyone has laying around and you're back
+your bot's code won't be lost if your computer spontaneously combusts, or you smash it to bits from
+anger. You can simply grab the backup computer that everyone has lying around, and you're back
 in business. 
 
 ### Organization and Cleanliness
@@ -165,7 +165,7 @@ MongoDB is a JSON-like format and if you already use JSON files, it shouldn't be
 
 #### SQLite
 SQLite is based on SQL, a common relational data model. It's a lightweight, easy-to-use, portable database solution that
-works entirely on files. However, if for some reason you cannot read/write to and from a file and you need to manage
+works entirely on files. However, if for some reason you cannot read/write to and from a file, and you need to manage
 lots of data, SQLite might not be for you.
 
 While SQLite is a part of the Python Standard Library as the `sqlite3` package, we recommend not using it as it is 

docs/interactions/application-commands/context-menus.mdx

@@ -14,11 +14,11 @@ import "discord-message-components/packages/react/dist/style.css";
 
 import DiscordComponent, { defaultOptions } from "../../../src/components/DiscordComponent";
 
-When you right-click a message, you may see an option called "Apps". Hover over it and you can see
+When you right-click a message, you may see an option called "Apps". Hover over it, and you can see
 commands a bot can run with that message. These are called message commands.
 
 When you right-click a user in the user list, you can once again see an option called "Apps". 
-Hover over it and you can see commands a bot can run with that message. These are called user commands.
+Hover over it, and you can see commands a bot can run with that message. These are called user commands.
 
 Together, these two are called Context Menus or Context Menu Commands. These commands work very much like normal commands, except they take a member or message.
 

docs/interactions/index.mdx

@@ -15,7 +15,7 @@ import DiscordComponent, { defaultOptions } from "../../src/components/DiscordCo
 
 In December 2020, Discord released their first Interaction: the
 [Slash Command](https://discord.com/developers/docs/interactions/application-commands#slash-commands).
-Since then, Discord has added many different types of Interactions, including:
+Since then, Discord has added many types of Interactions, including:
 
 [**Application Commands**](https://discord.com/developers/docs/interactions/application-commands)
 
@@ -233,7 +233,7 @@ Menus page](./ui-components/dropdowns.mdx).
 
 Text Modals are the most recently added 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 multiple text fields, 
-which avoids having the user send multiple messages for the bot. Modals can accessed by either invoking an Application Command or by 
+which avoids having the user send multiple messages for the bot. Modals can be accessed by either invoking an Application Command or by
 interacting with another UI Component.
 
 ![Text Modal Example Image](../assets/interactions/modal-example.png)

docs/interactions/ui-components/buttons.mdx

@@ -288,7 +288,7 @@ No. As a Discord limitation, you can only have one view per message.
 
 They cannot be simple like commands. This system makes them flexible and doesn't limit your imagination. There are loads of different ways you can use UI Components. For example, you could subclass Buttons or Select Menus and add them to a view using the view's `add_item` function.
 
-UI Components aren't hard to use if you know Python. We recommend learning [Object Oriented Programming with Python](#oop).
+UI Components aren't hard to use if you know Python. We recommend learning [Object-Oriented Programming with Python](#oop).
 
 #### <span id="oop">What is OOP? What is subclassing?</span>
 

docs/interactions/ui-components/dropdowns.mdx

@@ -69,7 +69,7 @@ That was the decorator. Now, the function itself is pretty simple. It takes two
 
 <!-- TODO: The values are sorted in the order the user selected them (?). The selected values are (?) -->
 
-In the callback, you could do anything you want. You get the two parameters `select` and `interaction` to play around with. Here, we send a message using `await interaction.response.send_message` (where interaction is [`discord.InteractionResponse`](https://docs.pycord.dev/en/master/api.html#discord.InteractionResponse)) with content `select.values[0]`, which sends the label of the first/only option the user selected. Obviously, this is only an example and you could do just about anything you want.
+In the callback, you could do anything you want. You get the two parameters `select` and `interaction` to play around with. Here, we send a message using `await interaction.response.send_message` (where interaction is [`discord.InteractionResponse`](https://docs.pycord.dev/en/master/api.html#discord.InteractionResponse)) with content `select.values[0]`, which sends the label of the first/only option the user selected. Obviously, this is only an example, and you could do just about anything you want.
 
 Finally, we create a global slash command called `flavour` that sends a message "Choose a flavor!" along with the view
 that contains our select menu.
@@ -281,7 +281,7 @@ No. As a Discord limitation, you can only have one view per message.
 
 They cannot be simple like commands. This system makes them flexible and doesn't limit your imagination. There are loads of different ways you can use UI Components. For example, you could subclass Buttons or Select Menus and add them to a view using the view's `add_item` function.
 
-UI Components aren't hard to use if you know Python. We recommend learning [Object Oriented Programming with Python](#oop).
+UI Components aren't hard to use if you know Python. We recommend learning [Object-Oriented Programming with Python](#oop).
 
 #### <e id="oop">What is OOP? What is subclassing?</e>
 

docs/introduction.mdx

@@ -41,7 +41,7 @@ Here are some good resources to get started or to freshen up your Python knowled
 
 First of all, we would like to thank [Rapptz](https://github.com/Rapptz) for the original [discord.py](https://pypi.org/project/discord.py) library. Pycord is a maintained fork of this library.
 
-We would also like to thank the [discord.js guide](https://discordjs.guide), which inspired this guide style-wise, and the [original Pycord Guide](https://namantech.me/pycord), which inspired some of the content in this guide.
+We would also like to thank the [discord.js guide](https://discordjs.guide), which inspired this guide style-wise, and the [original Pycord Guide](https://namantech.me/pycord), which inspired some content in this guide.
 
 We created this guide using [Docusaurus v2](https://docusaurus.io), a modern static site generator for React. We would also like to thank Danktuary for his [`@discord-message-components/react`](https://www.npmjs.com/package/@discord-message-components/react) package, from which we took the Discord message components.
 

docs/more/contributing.mdx

@@ -21,7 +21,7 @@ This page outlines some of the basic syntax you need to know to contribute to th
 
 ## Info
 
-We use [Docusaurus v2](https://docusaurus.io/) to generate our guide. All of the guide pages are generated
+We use [Docusaurus v2](https://docusaurus.io/) to generate our guide. All the guide pages are generated
 from `mdx` files in the [`docs/`](https://github.com/Pycord-Development/guide/tree/master/docs) directory.
 MDX allows you to use JSX in your markdown content.