Update some broken links and don't link to WoT Core Concepts so much.

Author: rwb27

docs/source/actions.rst

@@ -8,7 +8,7 @@ terms, any method of a `.Thing` that we want to be able to call over HTTP
 should be decorated as an Action, using `.thing_action`.
 
 This page gives an overview of how actions are implemented in LabThings-FastAPI.
-:ref:`wot_cc` includes a section on :ref:`wot_actions` that introduces the general concept.
+Our implementation should align with :ref:`wot_actions` as defined by the Web of Things standard.
 
 Running actions via HTTP
 ------------------------

src/labthings_fastapi/decorators/__init__.py

@@ -1,12 +1,10 @@
 """Mark the Interaction Affordances of a Thing.
 
-See :ref:`wot_cc` for definitions of Interaction Affordance and other terms.
-
 LabThings generates a :ref:`wot_td` to allow actions, properties, and
 events to be used by client code. The descriptions of each "interaction
-affordance" rely on docstrings and Python type hints to provide a full
-description of the parameters, so it's important that you use these
-effectively.
+affordance" (see :ref:`wot_affordances`) rely on docstrings and Python
+type hints to provide a full description of the parameters, so it's
+important that you use these effectively.
 
 If you have a complex datatype, it's recommended to use a `pydantic` model
 to describe it - this is often the case for complicated properties or events.

src/labthings_fastapi/thing.py

@@ -1,8 +1,8 @@
 """A class to represent hardware or software Things.
 
 The `.Thing` class enables most of the functionality of this library,
-and is the way in to most of its features. See :ref:`wot_cc` and :ref:`labthings_cc`
-for more.
+and is the way in to most of its features. See :ref:`structure`
+for how it fits with the rest of the library.
 """
 
 from __future__ import annotations