Make "related issues" links consistent

Author: birkenfeld

protocol/specification/datainfo.rst

@@ -56,7 +56,9 @@ JSON can't transport those 'values'.
 If the relative resolution is not given or not better than 1.2e-7, single
 precision floats may be used in the ECS.
 
-Related issue: :issue:`042 Requirements of datatypes`
+.. dropdown:: Related issues
+
+    | :issue:`042 Requirements of datatypes`
 
 .. rubric:: Optional data properties
 
@@ -72,7 +74,9 @@ Related issue: :issue:`042 Requirements of datatypes`
     SHOULD be given, if meaningful.  The quantity is unitless if unit is omitted
     or the empty string.  Preferably SI units (including prefix) SHOULD be used.
 
-    Related issue: :issue:`043 Parameters and units`
+    .. dropdown:: Related issues
+
+        | :issue:`043 Parameters and units`
 
 ``"absolute_resolution"``
     A JSON number specifying the smallest difference between distinct values.
@@ -91,7 +95,9 @@ Related issue: :issue:`042 Requirements of datatypes`
 
     ``max(absolute_resolution, abs(value) * relative_resolution)``
 
-    Related issue: :issue:`049 Precision of Floating Point Values`
+    .. dropdown:: Related issues
+
+        | :issue:`049 Precision of Floating Point Values`
 
 ``"fmtstr"``
     A C-style format  string as a hint on how to format numeric parameters for
@@ -125,7 +131,9 @@ floating point value.  It is up to the client to perform the conversion when
 reading/writing.  The main motivation for this datatype is for SEC nodes with
 limited capabilities, where floating point calculation is a major effort.
 
-Related issue: :issue:`044 Scaled integers`
+.. dropdown:: Related issues
+
+    | :issue:`044 Scaled integers`
 
 .. rubric:: Mandatory data properties
 
@@ -410,7 +418,9 @@ As a JSON object.
 
 Example: ``{"x": 0.5, "y": 1}``
 
-Related issue: :issue:`035 Partial Structs`
+.. dropdown:: Related issues
+
+    | :issue:`035 Partial Structs`
 
 
 .. _matrix:

protocol/specification/descriptive.rst

@@ -217,7 +217,9 @@ Optional module properties
     lowercase version of a path component must not match the lowercase version
     of any module name on the same SEC node.
 
-    Related issue: :issue:`008 Groups and Hierarchy`
+    .. dropdown:: Related issues
+
+        | :issue:`008 Groups and Hierarchy`
 
 .. mod-property:: meaning
 

protocol/specification/messages/heartbeat.rst

@@ -29,7 +29,7 @@ Example:
     > ping 123
     < pong 123 [null, {"t": 1505396348.543}]
 
-.. dropdown:: Related Issues
+.. dropdown:: Related issues
 
     | :issue:`003 Timestamp Format`
     | :issue:`007 Time Synchronization`

protocol/specification/syntax.rst

@@ -37,10 +37,13 @@ Any SEC node is allowed to generate the following messages:
 
 .. rubric:: Compatibility
 
-The specification is intended to grow and adopt to new needs. (Related issue:
-:issue:`038 Extension mechanisms`.) To futureproof the the communication, the
-following messages MUST be parsed and treated correctly (i.e. the ignored_value
-part is to be ignored).
+The specification is intended to grow and adapt to new needs.  To futureproof
+the the communication, the following messages MUST be parsed and treated
+correctly (i.e. the ignored_value part is to be ignored).
+
+.. dropdown:: Related issues
+
+    | :issue:`038 Extension mechanisms`
 
 Any SEC node **MUST** accept the following messages and handle them properly:
 

protocol/specification/transport.rst

@@ -87,7 +87,7 @@ description does not match, it is up to the ECS to handle this.
 Naturally, if the previous connection was activated, an `activate` message has
 to be sent before it can continue as before.
 
-.. dropdown:: Related Issues
+.. dropdown:: Related issues
 
    | :issue:`004 The Timeout SEC Node Property`
    | :issue:`006 Keep Alive`