diff --git a/technical/7.-Jami-plugins.md b/technical/7.-Jami-plugins.md
index 627d0c30bac8971d9563925b3c8331778ecdbe82..423682b9786a5363632e69d33eec825611038cce 100644
--- a/technical/7.-Jami-plugins.md
+++ b/technical/7.-Jami-plugins.md
@@ -5,12 +5,24 @@ As from September of 2020, Jami team has added plugins as a call feature for Lin
 This meaning that now you can personalize your call experience by using one of our available plugins. 
 But that is not all, you can also transform your awesome ideas into a brand new plugin!
 
-To properly setup a plugin you must follow the steps bellow.
+* To properly setup a plugin you must follow the steps in [#How to use it?]("").
+* To build a available plugin, please refer to [#How to build?]("") instructions.
+* To create your own plugin, please refer to [Create Plugin](create_plugin) instructions.
 
-To build a available plugin, please refer to [#How to build?]("") instructions.
-To create your own plugin, please refer to [Create Plugin](create_plugin) instructions.
+## How it works?
+Jami can be break down to three main components that interact together: Daemon, LRC and clients.
+Daemon is the core of Jami, and although it does not interact with users, it is involved in every
+command. Therefore, Daemon has a `JamiPluginManager` class that among other actions perfoms install/uninstall, load/unload, edit preferences and control plugins' usage.
+Despite Daemon importance, what a plugin effectivelly does to a call video is unknown to it the same way Daemon does not know what is effectivelly done by LRC or the clients interfaces.
+Plugins then can be seen as a forth interacting component in Jami.
 
-If you are interested in knowing how our Plugin system works, please refer to [#How it works?]("")
+Plugins are composed by two main components: the media handler and the process. While the latter actually implements plugin's functionality and waits data to perform, the former is the interface between Daemon and the plugin.
+It is, the media handler is attached or detached to a media stream from Daemon and passes data to plugin's process.
+
+To use a plugin it is necessary that the `JamiPluginManager` knows plugin's media handlers and the available media streams.
+Plugin's media handlers are created once a plugin is loaded and they are shared with Daemon's Plugin Manager.
+And in the event of a new SIP call, the `JamiPluginManager` creates and stores the corresponding media stream subjects.
+Finally, once a user puts a plugin in action the `JamiPluginManager` attaches that plugin's media handler and the available call media streams. When deactivated, our Plugin Manager dettaches these two instances.
 
 ## How to use it?
 
@@ -183,21 +195,6 @@ Each of these files corresponds to a platform and tensorflow build to be used.
 
 The foregroundsegmentation.jpl file will be available under `<jami-plugins/build/>`.
 
-### How it works?
-Jami can be break down to three main components that interact together: Daemon, LRC and clients.
-Daemon is the core of Jami, and although it does not interact with users, it is involved in every
-command. Therefore it is only natural that Daemon is responsible for everything related to Plugin's management, and among other actions it perfoms install/uninstall, load/unload, edit preferences and control plugins' usage.
-Despite Daemon importance, what a plugin effectivelly does to a call video is unknown to it the same way Daemon does not know what is effectivelly done by LRC or the clients interfaces.
-Plugins then can be seen as a forth interacting component in Jami.
-
-By it's time Plugins are composed by two main components: the media handler and the process. While the latter actually implements plugin's functionality and waits data to perform, the former is the interface between Daemon and the plugin. 
-It is, the media handler is attached or detached to a media stream from Daemon and passes it to plugin's process.
-
-To use a plugin it is necessary that the Plugin Manager knows the available media stream and plugin's media handlers.
-Plugin's media handlers are created once a plugin is loaded and they are shared with Daemon's Plugin Manager.
-In the event of a new SIP call, the Plugin Manager creates and stores the corresponding media stream subjects.
-Finally, once a user puts a plugin in action the Plugin Manager attaches this plugin's media handler and the available call media streams. When deactivated, our Plugin Manager dettaches these two instances.
-
 
 Related articles:
 
diff --git a/uploads/plugins/Screenshot_20200716-131836_Jami.jpg b/uploads/plugins/Screenshot_20200716-131836_Jami.jpg
deleted file mode 100755
index 55386bb63cf84303194b37a72e1421a433d5c758..0000000000000000000000000000000000000000
Binary files a/uploads/plugins/Screenshot_20200716-131836_Jami.jpg and /dev/null differ
diff --git a/uploads/plugins/Screenshot_20200716-131841_Jami.jpg b/uploads/plugins/Screenshot_20200716-131841_Jami.jpg
deleted file mode 100755
index f11c435637947af686bdd178f85f56658666e4ea..0000000000000000000000000000000000000000
Binary files a/uploads/plugins/Screenshot_20200716-131841_Jami.jpg and /dev/null differ
diff --git a/uploads/plugins/change_preference_android.jpg b/uploads/plugins/change_preference_android.jpg
deleted file mode 100755
index 1b7a192d24f9a44e112660b3fe48620c7c596eee..0000000000000000000000000000000000000000
Binary files a/uploads/plugins/change_preference_android.jpg and /dev/null differ
diff --git a/uploads/plugins/install_android.jpg b/uploads/plugins/install_android.jpg
deleted file mode 100755
index 31fd7e382bee0d3a9d0d9dcb105e77e932110ee2..0000000000000000000000000000000000000000
Binary files a/uploads/plugins/install_android.jpg and /dev/null differ
diff --git a/uploads/plugins/install_linux.png b/uploads/plugins/install_linux.png
deleted file mode 100644
index 00b008b80d7487f70cfd6c98ca8fd07d3b8a1b8c..0000000000000000000000000000000000000000
Binary files a/uploads/plugins/install_linux.png and /dev/null differ
diff --git a/uploads/plugins/installed_android.jpg b/uploads/plugins/installed_android.jpg
deleted file mode 100755
index 492cf3f80b488cae5da406ffd3f4e238304b8fd0..0000000000000000000000000000000000000000
Binary files a/uploads/plugins/installed_android.jpg and /dev/null differ
diff --git a/uploads/plugins/installed_linux.png b/uploads/plugins/installed_linux.png
deleted file mode 100644
index 9034d99269fa9cf0e8ec77a2d4ab79e4385b084c..0000000000000000000000000000000000000000
Binary files a/uploads/plugins/installed_linux.png and /dev/null differ
diff --git a/uploads/plugins/plugin_disabled_android.jpg b/uploads/plugins/plugin_disabled_android.jpg
deleted file mode 100755
index 7f1dea5ef72ac3e6a759114dba2bf0d2439cbb6b..0000000000000000000000000000000000000000
Binary files a/uploads/plugins/plugin_disabled_android.jpg and /dev/null differ
diff --git a/uploads/plugins/uninstall_android.jpg b/uploads/plugins/uninstall_android.jpg
deleted file mode 100755
index 45f40300a287ffb1551ed93fce562e320394b34f..0000000000000000000000000000000000000000
Binary files a/uploads/plugins/uninstall_android.jpg and /dev/null differ
diff --git a/uploads/plugins/use_android.jpg b/uploads/plugins/use_android.jpg
deleted file mode 100755
index 6893fb0dc0e3a166bdc9181c92dddfe3ef9051e9..0000000000000000000000000000000000000000
Binary files a/uploads/plugins/use_android.jpg and /dev/null differ
diff --git a/uploads/plugins/use_linux.png b/uploads/plugins/use_linux.png
deleted file mode 100644
index 66ab92c3bf4ac65ef93b45aacb1f5d713c2252d3..0000000000000000000000000000000000000000
Binary files a/uploads/plugins/use_linux.png and /dev/null differ
diff --git a/uploads/plugins/using_android.jpg b/uploads/plugins/using_android.jpg
deleted file mode 100755
index eea0b1d8496094d4d879eb040e8ae21ab2fc776f..0000000000000000000000000000000000000000
Binary files a/uploads/plugins/using_android.jpg and /dev/null differ