From df2b45705ee68d9a98cec3e9ec5ef9e49e167765 Mon Sep 17 00:00:00 2001 From: guoguangwu Date: Sun, 12 Nov 2023 20:42:33 +0800 Subject: [PATCH] fix: typo Signed-off-by: guoguangwu --- server/README-MQTT.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/server/README-MQTT.md b/server/README-MQTT.md index e61a0991e87..cac3933d5f4 100644 --- a/server/README-MQTT.md +++ b/server/README-MQTT.md @@ -142,7 +142,7 @@ Here is the overview of how we set up and use JetStream **streams**, ## JetStream API All interactions with JetStream are performed via `mqttJSA` that sends NATS -requests to JetStream. Most are processed syncronously and await a response, +requests to JetStream. Most are processed synchronously and await a response, some (e.g. `jsa.sendAck()`) are sent asynchronously. JetStream API is usually referred to as `jsa` in the code. No special locking is required to use `jsa`, however the asynchronous use of JetStream may create race conditions with