plugins.md in power_stencil-0.4.8

- old
+ new

@@ -42,11 +42,11 @@
 The normal process would be to begin with a plugin within the project and once you're ok with its features you may release it as a standalone Ruby Gem.
 
 - Plugins local to the project are automatically taken in account.
 - To use plugins provided as Gems you have to set the `:plugins:` array property in the `.ps_project/versioned-config.yaml`
 
-:warning: Plugins provided as standalone Gems are not thoroughly tested, for the time being you may use plugins local to the project.
+:warning: Plugins provided as standalone Gems are not thoroughly tested, for the time being, you may use plugins local to the project.
 
 
 # Creating plugin local to the project
 
 The is a command provided for that, that will create a whole plugin skeleton.
@@ -143,12 +143,12 @@
 ```
 
 Wow it worked ! Useless, but worked !
 
 
-The documentation for plugins is not yet done, so you are encouraged to read the code, the capabilities (in the output of `power_stencil info`) give you an idea of what plugins can do.
+The documentation for plugins is not yet done, so you are encouraged to read the code, the `capabilities` (in the output of `power_stencil info`) give you an idea of what plugins can do. Some official plugins are under development, and the documentation will be improved along their development...
 
-:warning: As opposed to the rest of `PowerStencil`, the functionnality is nevertheless not completely frozen.
+**:warning: As opposed to the rest of `PowerStencil`, the functionnality is nevertheless not completely frozen. This will be the case once `PowerStencil` turns 1.0.0.**
 
 
 [:back:][Documentation root]
 <!-- End of Document -->
 
\ No newline at end of file