Rename Plugins.rst to SmartPlugins.rst

docs/source/index.rst

@@ -84,7 +84,7 @@ To get started, press the Next button.
 
     resources/UpdateHandling
     resources/UsingFilters
-    resources/Plugins
+    resources/SmartPlugins
     resources/AutoAuthorization
     resources/CustomizeSessions
     resources/TgCrypto

docs/source/resources/SmartPlugins.rst

@@ -1,15 +1,15 @@
-Plugins
+Smart Plugins
-=======
+=============
 
-Pyrogram embeds an **automatic** and lightweight plugin system that is meant to further simplify the organization of
+Pyrogram embeds a **smart** (automatic) and lightweight plugin system that is meant to further simplify the organization
-large projects and to provide a way for creating pluggable components that can be **easily shared** across different
+of large projects and to provide a way for creating pluggable components that can be **easily shared** across different
 Pyrogram applications with **minimal boilerplate code**.
 
 Introduction
 ------------
 
-Prior to the plugin system, pluggable handlers were already possible. For instance, if you wanted to modularize your
+Prior to the Smart Plugin system, pluggable handlers were already possible. For example, if you wanted to modularize
-applications, you had to do something like this...
+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
         text message you sent and the other containing the reversed text message (e.g.: "pyrogram" -> "pyrogram" and
@@ -61,13 +61,15 @@ manually ``import``, manually :meth:`add_handler <pyrogram.Client.add_handler>`
 :obj:`MessageHandler <pyrogram.MessageHandler>` object because **you can't use those cool decorators** for your
 functions. So... What if you could?
 
-Creating Plugins
+Using Smart Plugins
-----------------
+-------------------
 
-Setting up your Pyrogram project to accommodate plugins is as easy as creating a folder and putting your files full of
+Setting up your Pyrogram project to accommodate Smart Plugins is as easy as creating a folder and putting your files
-handlers inside.
+full of handlers inside.
 
-    .. note:: This is the same example application `as shown above <#introduction>`_, written using the plugin system.
+    .. note::
+
+        This is the same example application `as shown above <#introduction>`_, written using the Smart Plugin system.
 
     .. code-block:: text
         :emphasize-lines: 2, 3
@@ -104,14 +106,13 @@ handlers inside.
             Client("my_account").run()
 
 The first important thing to note is the ``plugins`` folder, whose name is default and can be changed easily by setting
-the ``plugins_dir`` parameter when creating a :obj:`Client <pyrogram.Client>`; you can put *any python file* in the
+the ``plugins_dir`` parameter when creating a :obj:`Client <pyrogram.Client>`; you can put *any python file* in there
-plugins folder and each file can contain *any decorated function (handlers)*. Your Pyrogram Client instance (in the
+and each file can contain *any decorated function* (handlers) with only one limitation: within a single plugin file you
-``main.py`` file) will **automatically** scan the folder upon creation to search for valid handlers and register them
+must use different names for each decorated function. Your Pyrogram Client instance (in the ``main.py`` file) will
-for you.
+**automatically** scan the folder upon creation to search for valid handlers and register them for you.
 
-Then you'll notice you can now use decorators, with only one limitation: within a single plugin file you must use
+Then you'll notice you can now use decorators. That's right, you can apply the usual decorators to your callback
-different names for each decorated function. That's right, you can apply the usual decorators to your callback functions
+functions in a static way, i.e. **without having the Client instance around**: simply use ``@Client`` (Client class)
-in a static way, i.e. **without having the Client instance around**: simply use ``@Client`` (Client class) instead of
+instead of the usual ``@app`` (Client instance) namespace and things will work just the same.
-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.