summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorOxan van Leeuwen <oxan@oxanvanleeuwen.nl>2023-01-28 17:16:46 +0100
committerLeo Izen <leo.izen@gmail.com>2023-01-28 11:59:59 -0500
commit91ba71b09f5b0ee6ea612285d30c51ad053c1ff3 (patch)
tree2c228dd31842cb3c515e33a24a57f480334ae615
parent588d66fb253f11d8282fbd5bed10537e644d8d96 (diff)
downloadmpv-91ba71b09f5b0ee6ea612285d30c51ad053c1ff3.tar.bz2
mpv-91ba71b09f5b0ee6ea612285d30c51ad053c1ff3.tar.xz
DOCS: Add missing 'not'
-rw-r--r--DOCS/man/ipc.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/DOCS/man/ipc.rst b/DOCS/man/ipc.rst
index 615d3b69df..fbb0b01f5d 100644
--- a/DOCS/man/ipc.rst
+++ b/DOCS/man/ipc.rst
@@ -193,8 +193,8 @@ And this is the completion:
{"request_id":123,"error":"success","data":null}
By design, you will not get a confirmation that the command was started. If a
-command is long running, sending the message will lead to any reply until much
-later when the command finishes.
+command is long running, sending the message will not lead to any reply until
+much later when the command finishes.
Some commands execute synchronously, but these will behave like asynchronous
commands that finished execution immediately.