docs/mctpd: Minor wording/formatting fixes

Some small clarifications and alignment of terms to the MCTP spec, and
some minor formatting adjustments.

Signed-off-by: Jeremy Kerr <[email protected]>

Author: jk-ozlabs

docs/mctpd.md

@@ -26,8 +26,8 @@ Service au.com.codeconstruct.MCTP1:
 ## Top-level object: `/au/com/codeconstruct/mctp1`
 
 This object serves as the global MCTP daemon namespace.
-It hosts `au.com.codeconstruct.MCTP1` dbus interface to modify mctp properties like
-supported message types.
+It hosts `au.com.codeconstruct.MCTP1` dbus interface to modify properties of
+the MCTP stack, such as supported message types.
 ```
 NAME                                TYPE      SIGNATURE  RESULT/VALUE  FLAGS
 au.com.codeconstruct.MCTP1          interface -          -             -
@@ -37,18 +37,17 @@ au.com.codeconstruct.MCTP1          interface -          -             -
 #### `.RegisterTypeSupport`: `yau`
 
 This method is used to add support for mctp message types other than control
-messages. Once called successfully subsequent response for get message type
-control command will include this new message type also. Also the versions
-passed to this method will be used to respond to get version control command.
+messages. Once called successfully subsequent response for Get Message Type
+Support control commands will include this new message type. Versions passed to
+this method will be used to respond to Get MCTP Version Support commands.
 
 `RegisterTypeSupport <msg type> <versions>`
 
-If message type is already registered then dbus call will fail
+If the message type is already registered, then dbus call will fail.
 
-`<msg type>` Message type defined in DSP0239
-
-`<versions>` Versions supported for this message type formatted as uint32 integers as
-specified in DSP0236
+ - `<msg type>` Message type, as defined in DSP0239.
+ - `<versions>` Versions supported for this message type formatted as uint32
+   integers as specified in DSP0236
 
 De-registration is automatic - the specified types (and versions) are registered
 for as long as the dbus sender remains attached to the message bus, and are