From ec67b8b646566bcfb41371085ee56e47269c8ab9 Mon Sep 17 00:00:00 2001 From: Jason Fox Date: Wed, 31 Jul 2024 15:02:20 +0200 Subject: [PATCH] Amend Text --- docs/iot-agent-json.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/iot-agent-json.md b/docs/iot-agent-json.md index fda80ef..4ae8002 100644 --- a/docs/iot-agent-json.md +++ b/docs/iot-agent-json.md @@ -55,7 +55,7 @@ A direct comparison of the two IoT Agents can be seen below: | HTTP commands posted to a well-known URL - response is in the reply | HTTP commands posted to a well-known URL - response is in the reply | Communications Handshake | | MQTT devices are identified by the path of the topic `/XXX/YYY` | MQTT devices are identified by the path of the topic `/XXX/YYY` | Device Identification | | MQTT commands posted to the `cmd` topic | MQTT commands posted to the `cmd` topic | Communications Handshake | -| MQTT command responses posted to the `cmdexe` topic | MQTT commands posted to the `cmdexe` topic | Communications Handshake | +| MQTT command responses posted to the `cmdexe` topic | MQTT command responses posted to the `cmdexe` topic | Communications Handshake | As can be seen, the message payload differs entirely between the two IoT Agents, but much of the rest of the protocol remains the same.