Remove all unncecessary :role: tags that I can find.

Author: AlexanderWells-diamond

docs/how-to/make-publishable-ioc.rst

@@ -1,7 +1,7 @@
 Create a Publishable IOC
 ========================
 
-As seen in :doc:`../tutorials/creating-an-ioc`, a single Python script can be an IOC.
+As seen in `../tutorials/creating-an-ioc`, a single Python script can be an IOC.
 It is also possible (and the most common situation) to have an entire Python module
 comprising an IOC. This guide explains both, as well as how to publish an IOC within
 the DLS environment.

docs/how-to/read-data-from-ioc.rst

@@ -8,8 +8,8 @@ This guide explains how to read data from an IOC in a separate Python program.
     These are used by EPICS for channel access to the PVs.
 
 
-To start, run the :mod:`cothread` IOC from :doc:`../tutorials/creating-an-ioc` or the 
-:mod:`asyncio` IOC from :doc:`use-asyncio-in-an-ioc` and leave it running at the 
+To start, run the `cothread` IOC from `../tutorials/creating-an-ioc` or the 
+`asyncio` IOC from `use-asyncio-in-an-ioc` and leave it running at the 
 interactive shell.
 
 We will read data from that IOC using this script:

docs/how-to/use-asyncio-in-an-ioc.rst

@@ -2,32 +2,32 @@ Use `asyncio` in an IOC
 =======================
 
 There are two libraries available for asynchronous operations in PythonIOC:
-:mod:`cothread` and :mod:`asyncio`. This guide shows how to use the latter in
+`cothread` and `asyncio`. This guide shows how to use the latter in
 an IOC.
 
 .. note::
-    This page only explains the differences between using :mod:`cothread` and :mod:`asyncio`.
-    For more thorough explanation of the IOC itself see :doc:`../tutorials/creating-an-ioc`
+    This page only explains the differences between using `cothread` and `asyncio`.
+    For more thorough explanation of the IOC itself see `../tutorials/creating-an-ioc`
 
 .. literalinclude:: ../examples/example_asyncio_ioc.py
 
 
 The ``dispatcher`` is created and passed to :func:`~softioc.softioc.iocInit`. This is what 
-allows the use of :mod:`asyncio` functions in this IOC. It contains a new event loop to handle
+allows the use of `asyncio` functions in this IOC. It contains a new event loop to handle
 this.
 
 The ``async update`` function will increment the value of ``ai`` once per second,
 sleeping that coroutine between updates.
 Note that we run this coroutine in the ``loop`` of the ``dispatcher``, and not in the
 main event loop.
 
-This IOC will, like the one in :doc:`../tutorials/creating-an-ioc`, leave an interactive 
+This IOC will, like the one in `../tutorials/creating-an-ioc`, leave an interactive 
 shell open. The values of the PVs can be queried using the methods defined in the 
-:mod:`softioc.softioc` module.
+`softioc.softioc` module.
 
 
 Asynchronous Channel Access
 ---------------------------
 
-PVs can be retrieved externally from a PV in an asynchronous manner by using the :py:mod:`aioca` module. 
+PVs can be retrieved externally from a PV in an asynchronous manner by using the :py`aioca` module. 
 It provides ``await``-able implementations of ``caget``, ``caput``, etc. See that module for more information.

docs/reference/api.rst

@@ -374,7 +374,7 @@ starting the IOC.
     This must be called exactly once after creating all the records required by
     the IOC and before calling :func:`~softioc.softioc.iocInit`.  After this
     function has been called none of the functions provided by
-    :mod:`softioc.builder` are usable.
+    `softioc.builder` are usable.
 
 .. automodule:: softioc.alarm
 

docs/tutorials/creating-an-ioc.rst

@@ -4,10 +4,10 @@ Creating an IOC
 Introduction
 ------------
 
-Once the module has been installed (see :doc:`installation`) we can create a 
+Once the module has been installed (see `installation`) we can create a 
 simple EPICS Input/Output Controller (IOC). 
 
-An EPICS IOC created with the help of ``pythonIoc`` and :mod:`softioc` is
+An EPICS IOC created with the help of ``pythonIoc`` and `softioc` is
 referred to as a "Python soft IOC".  The code below illustrates a simple IOC
 with two Process Variables (PVs):
 
@@ -19,21 +19,21 @@ Each section is explained in detail below:
     :start-after: # Import
     :end-before: # Set
 
-The :mod:`softioc` library is part of ``pythonIoc``. The two submodules 
-:mod:`softioc.softioc` and :mod:`softioc.builder` provide the basic 
+The `softioc` library is part of ``pythonIoc``. The two submodules 
+`softioc.softioc` and `softioc.builder` provide the basic 
 functionality for Python soft IOCs and are the ones that are normally used.
 
-:mod:`cothread` is one of the two possible libraries the IOC can use for
+`cothread` is one of the two possible libraries the IOC can use for
 asynchronous operations. 
-(see :doc:`../how-to/use-asyncio-in-an-ioc` for the alternative)
+(see `../how-to/use-asyncio-in-an-ioc` for the alternative)
 
 
 
 .. literalinclude:: ../examples/example_cothread_ioc.py
     :start-after: # Create 
     :end-before: # Boilerplate
 
-PVs are normally created dynamically using :mod:`softioc.builder`.  All PV
+PVs are normally created dynamically using `softioc.builder`.  All PV
 creation must be done before initialising the IOC. We define a lambda function for 
 `on_update` on ``ao`` such that whenever we set ``ao``, ``ai`` will be set to the 
 same value. The ``always_update`` flag ensures that the ``on_update`` function is always 
@@ -66,11 +66,11 @@ needed.  The :func:`~softioc.softioc.interactive_ioc` runs a Python
 interpreter shell with a number of useful EPICS functions in scope, and
 passing ``globals()`` through can allow interactive interaction with the
 internals of the IOC while it's running.  The alternative is to call something
-like :func:`cothread.WaitForQuit` or some other :mod:`cothread` blocking
+like :func:`cothread.WaitForQuit` or some other `cothread` blocking
 action.
 
 In this interpreter there is immediate access to methods defined in the 
-:mod:`softioc.softioc` module. For example the :func:`~softioc.softioc.dbgf` function
+`softioc.softioc` module. For example the :func:`~softioc.softioc.dbgf` function
 can be run to observe the increasing value of ``AI``::
 
     >>> dbgf("MY-DEVICE-PREFIX:AI")
@@ -93,12 +93,12 @@ and read the value on ``AI`` (exact values will vary based on time taken)::
 Creating PVs
 ------------
 
-See the documentation of :mod:`softioc.builder` for details, but an overview is
+See the documentation of `softioc.builder` for details, but an overview is
 provided here.
 
 PVs are created internally and dynamically using functionality provided by
-:mod:`epicsdbbuilder`, which in this context simply provides mechanisms for
-creating ``.db`` files, but :mod:`softioc.builder` also binds each created PV to
+`epicsdbbuilder`, which in this context simply provides mechanisms for
+creating ``.db`` files, but `softioc.builder` also binds each created PV to
 a special ``Python`` device -- this allows PV processing to be hooked into
 Python support.
 
@@ -131,7 +131,3 @@ For all records created by these methods both
 reading and writing the current value of the record.  For IN records calling
 :meth:`~softioc.device.ProcessDeviceSupportIn.set` will trigger a record update
 (all IN records are by default created with ``SCAN='I/O Intr'``).
-
-
-..  _cothread: https://github.com/dls-controls/cothread
-..  _epicsdbbuilder: https://github.com/Araneidae/epicsdbbuilder