From 3081a893e03edbc633e28a0f355a81ffdaa35b2f Mon Sep 17 00:00:00 2001
From: Ahmed // Dropheart <35108279+DroppedHeart@users.noreply.github.com>
Date: Fri, 5 Jan 2018 02:15:02 +0300
Subject: [PATCH] Fixing some grammar. (#70)

Changed "Now lets" to "Now let's" on line 24
---
 docs/bot_tutorial/first_steps.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/bot_tutorial/first_steps.md b/docs/bot_tutorial/first_steps.md
index 02f05a8..6b6b961 100644
--- a/docs/bot_tutorial/first_steps.md
+++ b/docs/bot_tutorial/first_steps.md
@@ -21,7 +21,7 @@ The \_\_init\_\_.py file is required for Python to find your plugin, but it can
 {% endhint %}
 
 
-Now lets setup the configuration file. To start off with we'll paste the following template in and modify our token key (`MY_BOT_TOKEN_HERE`) to be the token we obtained above. The plugins section tells disco what plugins to load, based on a module path (similar to how Python imports work). In this example we're asking disco to load the plugin contained in the tutorial file within the plugins directory (or "module"). Disco by default loads the first plugin it finds within the module, so you want to make sure each plugin class is contained within its own file.
+Now let's setup the configuration file. To start off with we'll paste the following template in and modify our token key (`MY_BOT_TOKEN_HERE`) to be the token we obtained above. The plugins section tells disco what plugins to load, based on a module path (similar to how Python imports work). In this example we're asking disco to load the plugin contained in the tutorial file within the plugins directory (or "module"). Disco by default loads the first plugin it finds within the module, so you want to make sure each plugin class is contained within its own file.
 
 ```yaml
 token: 'MY_BOT_TOKEN_HERE'