Merge pull request #83 from epics-containers/remove-dev

remove references to the dev namespace of ke command

Author: gilesknap

docs/user/tutorials/debug_generic_ioc.rst

@@ -66,10 +66,10 @@ where the last successful Dockerfile command was run. This means that we can
 investigate the build failure by running a shell in the container. ``ec``
 provides us with the following convenience command to do this:
 
-
 - scroll up the page until you see the last successful build step e.g.
 
-  .. code-block:: bash
+.. code-block:: bash
+
     STEP 14/19: COPY ibek-support/StreamDevice/ StreamDevice/
     --> 631291db1751
     STEP 15/19: RUN StreamDevice/install.sh 2.8.24

docs/user/tutorials/dev_container.rst

@@ -65,7 +65,7 @@ dependencies on our local machine. Instead we can use a developer container,
 and in fact our Generic IOC *is* our developer container.
 
 When the CI builds a Generic IOC it creates
-`two targets <https://github.com/orgs/epics-containers/packages?repo_name=ioc-adsimdetector>`_:
+`two targets <https://github.com/orgs/epics-containers/packages?repo_name=ioc-adsimdetector>`_
 
 :developer: this target installs all the build tools and build time dependencies
    into the container image. It then compiles the support modules and IOC.
@@ -87,7 +87,7 @@ you should use the developer container CLI to get your developer container
 started. This means the configuration in ``.devcontainer/devcontainer.json``
 is used to start the container. This is necessary as that is where the
 useful host filesystem mounts and other config items are defined. See
-`devcontainer-cli<https://code.visualstudio.com/docs/devcontainers/devcontainer-cli>`_
+`devcontainer-cli <https://code.visualstudio.com/docs/devcontainers/devcontainer-cli>`_
 for details.