fixes from the review by @Bilchreis

Author: birkenfeld

protocol/specification/changes.rst

@@ -30,8 +30,7 @@ loss of functionality.
 
 - The `meaning` property for modules has a different format with capabilities to
   link to external definitions/ontologies.  `meaning` can now also be given for
-  individual accessibles, and new "functions" have been added to be better
-  compatible with the NeXuS standard.
+  individual accessibles, and new "functions" have been added.
 
 .. TODO not yet in the text!
 

protocol/specification/classes.rst

@@ -54,7 +54,7 @@ Base classes
     a motorized needle valve).  It must have a `stop` command in addition to
     what a `Writable` has.  Note that in case the `stop` command has no
     effect, a `Writable` SHOULD be used.  Also, the `status` parameter will
-    indicate a BUSY state for a longer lasting operations.
+    indicate a ``BUSY`` state for a longer lasting operations.
 
 
 .. _features:

protocol/specification/messages/optional.rst

@@ -1,8 +1,11 @@
 ``check``, ``logging``: Optional extensions
 -------------------------------------------
 
-These messages are optional feature - the SEC node does not need to support them
-and should reply with a `ProtocolError` error to indicate this.
+These sets of messages are optional feature - the SEC node does not need to
+support them and should reply with a `ProtocolError` error to indicate this.
+
+Dry run functionality
+~~~~~~~~~~~~~~~~~~~~~
 
 .. message:: [request] check <module>:<accessible> [<value>]
              [reply] checked <module>:<accessible> <data-report>
@@ -51,6 +54,9 @@ and should reply with a `ProtocolError` error to indicate this.
         | :issue:`075 New messages check and checked`
 
 
+Logging support
+~~~~~~~~~~~~~~~
+
 .. message:: [request] logging <module>[:<parameter>] <level>
              [reply] logging <module>[:<parameter>] <level>
              [reply] error_logging <module> <error-report>