Formatting and minor updates

Author: actions-user

README.md

@@ -523,18 +523,16 @@ communicating by sending device measures over the `/ul/4jggokgpepnvsb2uv4s40d59o
 
 > **Note** Measures and commands are sent over different MQTT topics:
 >
-> *   _Measures_ are sent on the `/<protocol>/<api-key>/<device-id>/attrs` topic
-> *   _Commands_ are sent on the `/<api-key>/<device-id>/cmd` topic
+> -   _Measures_ are sent on the `/<protocol>/<api-key>/<device-id>/attrs` topic
+> -   _Commands_ are sent on the `/<api-key>/<device-id>/cmd` topic
 >
->  The reasoning behind this is that when sending measures northbound from device to IoT Agent,
->  it is necessary to explicitly identify which IoT Agent is needed to parse the data. This
->  is done by prefixing the relevant MQTT topic with a protocol, otherwise there is no way to
->  define which agent is processing the measure. This mechanism allows smart systems to connect
->  different devices to different IoT Agents according to need.
+> The reasoning behind this is that when sending measures northbound from device to IoT Agent, it is necessary to
+> explicitly identify which IoT Agent is needed to parse the data. This is done by prefixing the relevant MQTT topic
+> with a protocol, otherwise there is no way to define which agent is processing the measure. This mechanism allows
+> smart systems to connect different devices to different IoT Agents according to need.
 >
->  For southbound commands, this distinction is unnecessary since the correct IoT Agent has already
->  registered itself for the command during the device provisioning step and the device will always
->  receive commands in an appropriate format.
+> For southbound commands, this distinction is unnecessary since the correct IoT Agent has already registered itself for
+> the command during the device provisioning step and the device will always receive commands in an appropriate format.
 
 The `resource` attribute is left blank since HTTP communication is not being used. The URL location of `cbroker` is an
 optional attribute - if it is not provided, the IoT Agent uses the default context broker URL as defined in the