Merge pull request #29 from epics-containers/dev

make support less scary

Author: gilesknap

docs/user/tutorials/deploy_example.rst

@@ -30,6 +30,12 @@ running in your default domain as follows:
 You should see some headings and an empty list as you have not yet started an
 IOC Instance.
 
+.. note::
+
+    The command ``ec`` is the epics-containers command line utilities entry
+    point. For more information see `CLI` or try ``ec --help``.
+
+
 The following command will deploy the example IOC instance to your cluster:
 
 .. code-block:: bash

docs/user/tutorials/support_module.rst

@@ -1,21 +1,28 @@
 Working with Support Modules
 =============================
 
+TODO: this is currently a stub with some pointers.
+
+TODO: suggest that we will make a new Stream Device that will be a
+simple echo server. Use this to step through the process of creating a
+new support module.
+
 This is a type 3. change from the list at `ioc_change_types`.
 
 If you are starting a new support module then the preceding tutorials
 have covered all of the skills you will need.
 
 To work on a new support module you will need a generic IOC project to
-work inside. You could choose to create two new projects, MyNewDeviceSupport
-and ioc-MyNewDeviceSupport, or you could create a single project which looks
-like a traditional EPICS Support module and merge in the files from
-ioc-template.
+work inside. You could choose to create two new projects:
+
+:MyNewDeviceSupport:
+
+    a traditional EPICS Support module,
+
+:ioc-MyNewDeviceSupport:
+
+    a generic IOC container definition based on ioc-template
 
 Once you have created the project(s), working on the support module will
 look very similar to the procedures set out here `debug_generic_ioc`
 
-
-TODO: suggest that we will make a new Stream Device that will be a
-simple echo server. Use this to step through the process of creating a
-new support module.