started ioc_changes2

Author: gilesknap

docs/user/tutorials/dev_container.rst

@@ -249,10 +249,10 @@ Adding the Beamline to the Workspace
 ------------------------------------
 
 To meaningfully test the Generic IOC we will need an instance to test it
-against. We will use the ``bl01t`` beamline that you already made. The container 
+against. We will use the ``bl01t`` beamline that you already made. The container
 has been configured to mount some useful local files from the user's home directory,
-including the parent folder of the workspace as ``/repos`` so we can work on 
-multiple peer projects. 
+including the parent folder of the workspace as ``/repos`` so we can work on
+multiple peer projects.
 
 In VSCode click the ``File`` menu and select ``Add Folder to Workspace``.
 Navigate to ``/repos`` and you will see all the peers of your ``ioc-adsimdetector``
@@ -320,6 +320,10 @@ host. i.e. the root folder under which your projects are all cloned):
      - WS
      - all peers to Generic IOC source repo
 
+.. _choose-ioc-instance:
+
+Choose the IOC Instance to Test
+-------------------------------
 
 Now that we have the beamline repo visible in our container we can
 easily supply some instance configuration to the Generic IOC.

docs/user/tutorials/ioc_changes2.rst

@@ -1,11 +1,16 @@
 Changing a Generic IOC Part 1
 =============================
 
+.. warning ::
+
+    This tutorial is a work in progress. It is not yet complete.
+
 This is a type 2 change from `ioc_change_types`.
 
 The changes that you can make in an IOC instance are limited to what
-the author of a generic IOC has made configurable. Therefore you will
-occasionally need to update the generic IOC that your instance is using.
+the author of the associated Generic IOC has made configurable.
+Therefore you will
+occasionally need to update the Generic IOC that your instance is using.
 Some of the reasons for doing this are:
 
 - Update one or more support modules to new versions
@@ -98,6 +103,11 @@ following command will select the example IOC instance:
 
     ibek dev instance /epics/ioc-adsample/ioc_examples/bl01t-ea-ioc-02
 
+In an earlier tutorial when learning about the dev container, we manually
+performed this step, see `choose-ioc-instance`. The above command does
+exactly the same thing: removes the existing config folder in ``/epics/ioc``
+and symlinks in the chosen IOC instance definition's ``config`` folder.
+
 Now  run the IOC:
 
 .. code-block:: console