Consistent heading casing

Author: birkenfeld

protocol/specification/accessibles.rst

@@ -1,4 +1,4 @@
-Parameters and Commands
+Parameters and commands
 =======================
 
 A typical module has several accessibles associated with it.  An accessible is
@@ -14,7 +14,7 @@ The following section describes the currently predefined parameters and
 commands.  This list will be extended continuously in new SECoP versions.
 
 
-Basic Parameters
+Basic parameters
 ~~~~~~~~~~~~~~~~
 
 .. parameter:: value
@@ -239,7 +239,7 @@ Error handling
     other ERROR state before returning ``done <module>:clear_errors``.
 
 
-Coupled Modules
+Coupled modules
 ~~~~~~~~~~~~~~~
 
 .. parameter:: controlled_by
@@ -346,7 +346,7 @@ Coupled Modules
     parameter with the name of the controlling module).
 
 
-Limits and Offset
+Limits and offset
 ~~~~~~~~~~~~~~~~~
 
 .. parameter:: target_limits

protocol/specification/additional.rst

@@ -1,4 +1,4 @@
-Additional Topics
+Additional topics
 =================
 
 .. toctree::

protocol/specification/classes.rst

@@ -1,6 +1,6 @@
 .. _interface-classes:
 
-Interface Classes
+Interface classes
 =================
 
 Interface classes let the ECS determine the functionality of a module from its
@@ -23,7 +23,7 @@ of the base classes listed below.
     even conform to the Readable class.
 
 
-Base Classes
+Base classes
 ------------
 
 .. baseclass:: Communicator

protocol/specification/descriptive.rst

@@ -1,7 +1,7 @@
 .. _descriptive-data:
 
-Properties: Self-Description
-============================
+Properties and descriptive data
+===============================
 
 This section explains the "descriptive data", also called "structure report",
 i.e. the completely self-describing metadata sent by the SEC node in response to
@@ -75,14 +75,14 @@ Example of a complete description (JSON has been pretty-printed for clarity):
        :alt: accessible_description ::= '{' property+ '}'
 
 
-SEC Node Description
+SEC node description
 --------------------
 
 The descriptive data is a JSON object with nested sub-hierarchies.  The
 properties on the top level describe the SEC node.
 
 
-Mandatory SEC Node Properties
+Mandatory SEC node properties
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 .. node-property:: modules
@@ -113,7 +113,7 @@ Mandatory SEC Node Properties
     ``\n`` for linebreaks.
 
 
-Optional SEC Node Properties
+Optional SEC node properties
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 .. node-property:: firmware
@@ -140,10 +140,10 @@ Optional SEC Node Properties
 
 .. _module-description:
 
-Module Description
+Module description
 ------------------
 
-Mandatory Module Properties
+Mandatory module properties
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 .. mod-property:: accessibles
@@ -167,7 +167,7 @@ Mandatory Module Properties
     "Drivable"]``.
 
 
-Optional Module Properties
+Optional module properties
 ~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 .. mod-property:: visibility
@@ -351,10 +351,10 @@ Optional Module Properties
 
 .. _accessible-description:
 
-Parameter and Command Description
+Parameter and command description
 ---------------------------------
 
-Mandatory Properties
+Mandatory properties
 ~~~~~~~~~~~~~~~~~~~~
 
 .. acc-property:: description
@@ -376,7 +376,7 @@ Mandatory Properties
               the latter have a datainfo of ``{"type": "command", ...}``.
 
 
-Mandatory Parameter Properties
+Mandatory parameter properties
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 .. acc-property:: readonly
@@ -385,7 +385,7 @@ Mandatory Parameter Properties
     or not.
 
 
-Optional Properties
+Optional properties
 ~~~~~~~~~~~~~~~~~~~
 
 .. acc-property:: group
@@ -478,7 +478,7 @@ Optional Properties
         | :issue:`075 New messages check and checked`
 
 
-Optional Parameter Properties
+Optional parameter properties
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 .. acc-property:: constant
@@ -491,7 +491,7 @@ Optional Parameter Properties
     The value given here must conform to the data type of the accessible.
 
 
-Custom Properties
+Custom properties
 -----------------
 
 Custom properties may further augment accessibles, modules or the SEC node

protocol/specification/discovery.rst

@@ -1,4 +1,4 @@
-UDP Discovery Protocol
+UDP discovery protocol
 ======================
 
 Due to the flexibility of the SECoP node system, it is quite likely for multiple
@@ -10,7 +10,7 @@ All SEC nodes that wish to support autodiscovery open a UDP socket listening on
 port 10767.  Upon receiving a packet on this port, they reply with a packet
 containing the required information to connect to this node.
 
-Format of the Packets
+Format of the packets
 ---------------------
 
 From client to nodes
@@ -37,7 +37,7 @@ From node to client
 
     Further keys in the object can be specified later.
 
-Node Self-Announcement
+Node self-announcement
 ----------------------
 
 Furthermore, a SEC node can self-announce by broadcasting UDP packets to port

protocol/specification/future.rst

@@ -1,6 +1,6 @@
 .. _future-compatibility:
 
-Future Compatibility
+Future compatibility
 ====================
 
 Notes for implementors of the current specification
@@ -60,7 +60,7 @@ design:
 * Define additional features, listed in an additional property.
 
 
-Message Handling
+Message handling
 ----------------
 
 For this, see :ref:`this section <message-compat>`.

protocol/specification/messages/activation.rst

@@ -1,5 +1,5 @@
-``activate``, ``deactivate``: Controlling events
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+``activate``, ``deactivate``: Control events
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 .. message:: [request] activate [<module>]
              [reply] active [<module>]

protocol/specification/messages/commands.rst

@@ -1,4 +1,4 @@
-``do``: execute commands
+``do``: Execute commands
 ~~~~~~~~~~~~~~~~~~~~~~~~
 
 .. message:: [request] do <module>:<command> [<value>]

protocol/specification/messages/errors.rst

@@ -1,6 +1,6 @@
 .. _error-reply:
 
-``error_*``: Error Replies
+``error_*``: Error replies
 --------------------------
 
 Contains an error class from the list below as its second item (the specifier).
@@ -26,7 +26,7 @@ Example:
 
 .. _error-classes:
 
-Error Classes
+Error classes
 -------------
 
 Error classes are divided into two groups: persisting errors and retryable

protocol/specification/messages/heartbeat.rst

@@ -1,4 +1,4 @@
-``ping``: heartbeat
+``ping``: Heartbeat
 ~~~~~~~~~~~~~~~~~~~
 
 .. message:: [request] ping [<token>]