builds.md in power_stencil-0.6.2

- old
+ new

@@ -18,10 +18,19 @@
 
 **:warning: You should have already read the documentation about [templates], before reading this.**
 
 You build a [buildable] entity by issuing `power_stencil build <entity_type>/<entity_name>`. If you try to build an entity which is not buildable, the process fail with an error message.
 
+**:information_source: You can get the list of buildable entities in your repository by issuing a `power_stencil build --list`:**
+
+```
+$ power_stencil build --list
+ - 'simple_exec' (buildable by 'PowerStencil core' and provided by 'PowerStencil core').
+```
+
+We will see later in the [templates] part what to do with this `simple_exec` entity type.
+
 Let's describe a bit more in detail what this build process is:
 
 ![entity-build-flow]
 
 Humm :thinking:... What is this _compilation_ step that appears on this schema ??! I thought Ruby was an interpreted language...
@@ -30,10 +39,10 @@
 
 # The "_compilation_" process
 
 The mechanism of the compilation is coming from the [universe_compiler] Gem, but the two following features are the ones you really need to understand.
 
-:information_source: The compilation process can be applied to any entity, ie it doesn't need to be [buildable] (see in next paragraph how to run the compilation). But an entity needs to be [buildable] to use `power_stencil build` which corresponds actually to _compilation_ + _detemplatization_.
+:information_source: The compilation process is actually applied to all entities, ie it doesn't need to be [buildable] (see in next paragraph how to run the compilation). But an entity needs to be [buildable] to use `power_stencil build` which corresponds actually to _compilation_ + _detemplatization_.
 
 ## Extending an entity
 
 We could describe this mechanism as inheritance at entity level (not entity type !), said differently this a way for an entity to _inherit_ (or _extend_ in the `PowerStencil` paradigm) the content of another entity.
 
\ No newline at end of file