Merge pull request #289494 from PatAltimore/patricka-mqtt-release-aio-m3

MQTT broker changes for M3

Author: prmerger-automator[bot]

articles/iot-operations/create-edge-apps/concept-about-state-store-protocol.md

@@ -5,7 +5,7 @@ author: PatAltimore
 ms.author: patricka
 ms.subservice: azure-mqtt-broker
 ms.topic: concept-article
-ms.date: 07/02/2024
+ms.date: 10/30/2024
 
 # CustomerIntent: As a developer, I want understand what the MQTT broker state store protocol is, so
 # that I can implement a client app to interact with the MQ state store.
@@ -198,10 +198,10 @@ The following is the current list of error strings. Your client application shou
 
 | Error string returned from state store | Explanation                                                                                                 |
 |----------------------------------------|-------------------------------------------------------------------------------------------------------------|
-| the requested timestamp is too far in the future; ensure that the client and broker system clocks are synchronized | Unexpected requested timestamp caused by the state store and client clocks are not in sync. |
+| the request timestamp is too far in the future; ensure that the client and broker system clocks are synchronized | Unexpected request timestamp caused by the state store and client clocks are not in sync. |
 | a fencing token is required for this request                                                                       | Error occurs if a key is marked with a fencing token, but the client doesn't specify the fencing token. |
-| the requested fencing token timestamp is too far in the future; ensure that the client and broker system clocks are synchronized | Unexpected fencing token timestamp caused by the state store and client clocks are not in sync. |
-| the requested fencing token is a lower version that the fencing token protecting the resource             | Incorrect requested fencing token version. For more information, see [Versioning and hybrid logical clocks].(#versioning-and-hybrid-logical-clocks) |
+| the request fencing token timestamp is too far in the future; ensure that the client and broker system clocks are synchronized | Unexpected fencing token timestamp caused by the state store and client clocks are not in sync. |
+| the request fencing token is a lower version that the fencing token protecting the resource             | Incorrect request fencing token version. For more information, see [Versioning and hybrid logical clocks].(#versioning-and-hybrid-logical-clocks) |
 | the quota has been exceeded                                                                               | The state store has a quota of how many keys it can store, which is based on the memory profile of the MQTT broker that's specified. |
 | syntax error                                                                                              | The payload sent doesn't conform to state store's definition.                                               |
 | not authorized                                                                                            | Authorization error                                                                                          |