Merge pull request #537 from wes-johnson/develop

Various fixes and updates for Sparkplug 4.0.0

Author: wes-johnson

specification/src/main/asciidoc/chapters/Sparkplug_1_Introduction.adoc

@@ -343,8 +343,9 @@ context of the Edge Node ID under which it exists.
 Identifies a single 'tag change event' in the Sparkplug Payload. It represents an event that 
 occurred at the Edge Node or Device such as a value or quality of a data point changing. For 
 example, it could represent the value of an analog or boolean changing at a Sparkplug Device. A 
-Sparkplug Metric typically includes a name, value, and timestamp. Sparkplug Metrics are also used in 
-NCMD and DCMD messages to send messages to Edge Nodes and Devices to change values at the Edge.
+Sparkplug Metric typically includes a name, value, quality, and timestamp. Sparkplug Metrics are
+also used in NCMD and DCMD messages to send messages to Edge Nodes and Devices to change values at
+the Edge.
 
 [[introduction_datatypes]]
 ===== Data Types

specification/src/main/asciidoc/chapters/Sparkplug_2_Principles.adoc

@@ -86,7 +86,7 @@ timer.
 === Birth and Death Certificates
 
 Birth and Death Certificates are used by both Edge Nodes and Host Applications. Death Certificates
-for both are always registered in the MQTT CONNECT packet as the MQTT Will Message. By using the
+for both, are always registered in the MQTT CONNECT packet as the MQTT Will Message. By using the
 MQTT Will message, the Death Certificates will be delivered to subscribers even if the MQTT client
 connection is lost ungracefully. For Edge Nodes, the Death Certificate uses the NDEATH Sparkplug
 verb in the topic. For Host Applications, the spBv1.0/STATE/sparkplug_host_id topic is used. More