Fix some references

Author: birkenfeld

protocol/specification/messages.rst

@@ -109,8 +109,8 @@ identifier length is limited (<=63 characters).
     - accessible names of a module (including the group entries of those
       parameters) - each module has its own scope
     - properties
-    - names of elements in a :ref:`struct` (each struct has its own scope)
-    - names of variants in an :ref:'enum` (each enum has its own scope)
+    - names of elements in a :ref:`struct <struct>` (each struct has its own scope)
+    - names of variants in an :ref:`enum <enum>` (each enum has its own scope)
     - names of qualifiers
 
 SECoP defined names are usually lowercase, though that is not a restriction
@@ -885,7 +885,7 @@ Essentially this boils down to:
 #) same for error class (i.e. treat ``WrongType:MustBeInt`` as ``WrongType``,
    ignoring the ``:MustBeInt`` part)
 #) upon parsing a value, when you know it should be one element from an
-   :ref:`enum` (which SHOULD be transported as integer), if you find a string
+   :ref:`enum <enum>` (which SHOULD be transported as integer), if you find a string
    instead and that string is one of the names from the Enum, use that entry.
 #) check newer versions of the specification and check the issues as well, as
    the above may change

protocol/specification/modules.rst

@@ -31,7 +31,7 @@ to be unique within an SEC node, accessible names have to be unique within a
 module.  There are two basic types of accessibles: parameters and commands.
 
 Module and accessible names should be in English (incl. acronyms), using only
-ASCII letters and digits and some additional characters (see :ref:`messages`).
+ASCII letters and digits and some additional characters (see :doc:`messages`).
 The maximum name length is 63 characters.
 
 Definition: Parameter

protocol/specification/overview.rst

@@ -18,7 +18,7 @@ SECoP Node Structure
 - SECoP is a communication protocol with a client-server model.  The server is
   called the "SEC node".
 
-- Each SEC node consists of one or more :ref:`Modules`.  These represent the
+- Each SEC node consists of one or more :ref:`modules`.  These represent the
   main interface for interacting with the hardware.
 
 - Each of these modules can have static values which are known at startup and
@@ -60,8 +60,8 @@ SECoP Node Structure
 Messages
 --------
 
-The communication between client and server builds upon :ref:`messages
-<messages>` which are transferred between SEC node and client.
+The communication between client and server builds upon :doc:`messages`
+which are transferred between SEC node and client.
 
 As an introduction, we will look at the general message structure, and the
 messages :ref:`*IDN? <message-identification>`, :ref:`describe