You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These are all very minor, so I don't expect any interest in addressing them, but I thought it might be good to report. These are all from the MQTT v5.0 PDF available at https://mqtt.org/mqtt-specification/.
L1167: "The values the Connect Reason Code are shown below" is inconsistent with similar statements in the spec (L2463, L2541, L2642).
Expected: "The values [for] the Connect Reason Code are shown below."
L1199 "... other than that sent by the Client in the CONNACK" seems to suggest the Client would send a CONNACK to the server.
Expected: "... other than that sent by the Client in the CONNECT."
L1328: "A value is 0 means ..."
Expected: "A value [of] 0 means ..."
L1344: "A value is 0 means ..."
Expected: "A value [of] 0 means ..."
L1555: "Payload Forma t Indicator" (space in the word Format)
Expected: "Payload Format Indicator"
L1568: "Message Expiry Interval`" (tilde following the word Interval)
Expected: "Message Expiry Interval"
L1741, [MQTT-3.3.4-4] "... which have a Subscription Identifiers, their" (pluralization)
Expected: "... which have a Subscription Identifier, their"
It seems likely I'll find more as I continue reading. Are any of these helpful? Is there a better method or place for me to report them?
The text was updated successfully, but these errors were encountered:
L3319: "... the expectation is that that Client will choose ..." is inconsistent with other references to "the Client" (L3294, L3298, L3299)
Expected: "... the expectation is that the Client will choose ..."
L3441: "Definitions of Malformed Packet and Protocol Errors are contained in section 1.2 Terminology, some but not all, of these error cases are noted throughout the specification." This is a run-on sentence, and could be improved by splitting the two distinct thoughts into separate sentences.
Expected: "Definitions of Malformed Packet and Protocol Errors are contained in section 1.2 Terminology. Some, but not all, of these error cases are noted throughout the specification.
These are all very minor, so I don't expect any interest in addressing them, but I thought it might be good to report. These are all from the MQTT v5.0 PDF available at https://mqtt.org/mqtt-specification/.
L1167: "The values the Connect Reason Code are shown below" is inconsistent with similar statements in the spec (L2463, L2541, L2642).
Expected: "The values [for] the Connect Reason Code are shown below."
L1199 "... other than that sent by the Client in the CONNACK" seems to suggest the Client would send a CONNACK to the server.
Expected: "... other than that sent by the Client in the CONNECT."
L1328: "A value is 0 means ..."
Expected: "A value [of] 0 means ..."
L1344: "A value is 0 means ..."
Expected: "A value [of] 0 means ..."
L1555: "Payload Forma t Indicator" (space in the word Format)
Expected: "Payload Format Indicator"
L1568: "Message Expiry Interval`" (tilde following the word Interval)
Expected: "Message Expiry Interval"
L1741, [MQTT-3.3.4-4] "... which have a Subscription Identifiers, their" (pluralization)
Expected: "... which have a Subscription Identifier, their"
It seems likely I'll find more as I continue reading. Are any of these helpful? Is there a better method or place for me to report them?
The text was updated successfully, but these errors were encountered: