Index: script.txt
==================================================================
--- script.txt
+++ script.txt
@@ -170,12 +170,12 @@
    for them belonging to the previous slice.  Both sliver descriptions include
    a public interface to the CN and user-defined properties for telling apart
    the source sliver from the target one.  Sliver descriptions go to the
    registry.
 4. Each of the previous nodes gets a sliver description for it.  If enough
-   resources are available, a container is created with the desired
-   configuration.
+   resources are available, a container is created by applying the desired
+   configuration over the selected template.
 5. Once the researcher knows that slivers have been instantiated, the server
    can be commanded to activate the slice.  The server updates the registry.
 6. When nodes get instructions to activate slivers they start the containers.
 7. Containers run the experiment setup program and the run program.  The
    programs query sliver properties to decide their behaviour.