Update SmartPlugins.rst page

docs/source/resources/SmartPlugins.rst

@@ -11,18 +11,18 @@ Introduction
 Prior to the Smart Plugin system, pluggable handlers were already possible. For example, if you wanted to modularize
 your applications, you had to do something like this...
 
-    .. note:: This is an example application that replies in private chats with two messages: one containing the same
+.. note:: This is an example application that replies in private chats with two messages: one containing the same
     text message you sent and the other containing the reversed text message (e.g.: "pyrogram" -> "pyrogram" and
     "margoryp"):
 
-    .. code-block:: text
+.. code-block:: text
 
     myproject/
         config.ini
         handlers.py
         main.py
 
-    - ``handlers.py``
+- ``handlers.py``
 
     .. code-block:: python
 
@@ -33,7 +33,7 @@ your applications, you had to do something like this...
         def echo_reversed(client, message):
             message.reply(message.text[::-1])
 
-    - ``main.py``
+- ``main.py``
 
     .. code-block:: python
 
@@ -64,14 +64,17 @@ functions. So... What if you could?
 Using Smart Plugins
 -------------------
 
-Setting up your Pyrogram project to accommodate Smart Plugins is as easy as creating a folder and putting your files
+Setting up your Pyrogram project to accommodate Smart Plugins is pretty straightforward:
-full of handlers inside.
 
-    .. note::
+#. Create a new folder to store all the plugins (e.g.: "plugins").
+#. Put your files full of plugins inside.
+#. Enable plugins in your Client.
+
+.. note::
 
     This is the same example application `as shown above <#introduction>`_, written using the Smart Plugin system.
 
-    .. code-block:: text
+.. code-block:: text
     :emphasize-lines: 2, 3
 
     myproject/
@@ -80,7 +83,7 @@ full of handlers inside.
         config.ini
         main.py
 
-    - ``plugins/handlers.py``
+- ``plugins/handlers.py``
 
     .. code-block:: python
         :emphasize-lines: 4, 9
@@ -97,22 +100,20 @@ full of handlers inside.
         def echo_reversed(client, message):
             message.reply(message.text[::-1])
 
-    - ``main.py``
+- ``main.py``
 
     .. code-block:: python
 
         from pyrogram import Client
 
-            Client("my_account").run()
+        Client("my_account", plugins_dir="plugins").run()
 
-The first important thing to note is the ``plugins`` folder, whose name is default and can be changed easily by setting
+The first important thing to note is the new ``plugins`` folder, whose name is passed to the the ``plugins_dir``
-the ``plugins_dir`` parameter when creating a :obj:`Client <pyrogram.Client>`; you can put *any python file* in there
+parameter when creating a :obj:`Client <pyrogram.Client>` in the ``main.py`` file — you can put *any python file* in
-and each file can contain *any decorated function* (handlers) with only one limitation: within a single plugin file you
+there and each file can contain *any decorated function* (handlers) with only one limitation: within a single plugin
-must use different names for each decorated function. Your Pyrogram Client instance (in the ``main.py`` file) will
+file you must use different names for each decorated function. Your Pyrogram Client instance will **automatically**
-**automatically** scan the folder upon creation to search for valid handlers and register them for you.
+scan the folder upon creation to search for valid handlers and register them for you.
 
 Then you'll notice you can now use decorators. That's right, you can apply the usual decorators to your callback
 functions in a static way, i.e. **without having the Client instance around**: simply use ``@Client`` (Client class)
 instead of the usual ``@app`` (Client instance) namespace and things will work just the same.
-
-The ``main.py`` script is now at its bare minimum and cleanest state.