From d7468ec158d70f2fc76e496e8b312a17a5b98d2e Mon Sep 17 00:00:00 2001 From: Ivan Enderlin Date: Mon, 13 Mar 2023 13:49:21 +0100 Subject: [PATCH] Update crates/matrix-sdk/src/sliding_sync/mod.rs Co-authored-by: Jonas Platte --- crates/matrix-sdk/src/sliding_sync/mod.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/crates/matrix-sdk/src/sliding_sync/mod.rs b/crates/matrix-sdk/src/sliding_sync/mod.rs index 1c2298da3..1cde584f1 100644 --- a/crates/matrix-sdk/src/sliding_sync/mod.rs +++ b/crates/matrix-sdk/src/sliding_sync/mod.rs @@ -346,8 +346,8 @@ //! To support this, in practice, one can spawn a `Future` that runs //! [`SlidingStream::stream`]. The spawned `Future` can be cancelled safely. If //! the client was waiting on a response, it's cancelled without any issue. If -//! the client was receiving a response, or a response was just received, the -//! response will be fully handled by `SlidingSync`. This _response is always +//! a response was just received, it +//! will be fully handled by `SlidingSync`. This _response is always //! handled_ process isn't blocking. The cancellation of the spawned `Future` //! will be as immediate as possible, and the response handling (if necessary) //! will be done in a “detached mode”. However, any further responses handling