man/io_uring_prep_cancel.3: clarify the NOTES section a bit more
Signed-off-by: Jens Axboe <axboe@kernel.dk>
diff --git a/man/io_uring_prep_cancel.3 b/man/io_uring_prep_cancel.3
index 3201445..3c9f2df 100644
--- a/man/io_uring_prep_cancel.3
+++ b/man/io_uring_prep_cancel.3
@@ -103,13 +103,15 @@
The execution state of the request has progressed far enough that cancelation
is no longer possible. This should normally mean that it will complete shortly,
either successfully, or interrupted due to the cancelation.
-
.SH NOTES
-
-Although the cancelation request uses async request syntax, the kernel part isn't async at all. It is guaranteed that a CQE is always generated by the time the cancel request has been submitted. If the cancelation is succeed, the request targeted for cancelation will have been posted by the time submission returns. For
+Although the cancelation request uses async request syntax, the kernel side of
+the cancelation is always run synchronously. It is guaranteed that a CQE is
+always generated by the time the cancel request has been submitted. If the
+cancelation is successful, the completion for the request targeted for
+cancelation will have been posted by the time submission returns. For
.B -EALREADY
-it may take a bit of time to do so.
-
+it may take a bit of time to do so. For this case, the caller must wait for the
+canceled request to post its completion event.
.SH SEE ALSO
.BR io_uring_prep_poll_remove (3),
.BR io_uring_get_sqe (3),
