From b8541cc27c3ec04b4a515fe647064c3ab37bdadc Mon Sep 17 00:00:00 2001 From: Johannes Marbach Date: Wed, 10 Jul 2024 10:04:54 +0200 Subject: [PATCH] Update content/client-server-api/modules/read_markers.md Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com> --- content/client-server-api/modules/read_markers.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/client-server-api/modules/read_markers.md b/content/client-server-api/modules/read_markers.md index 1f970fb2..31e05266 100644 --- a/content/client-server-api/modules/read_markers.md +++ b/content/client-server-api/modules/read_markers.md @@ -65,8 +65,8 @@ attention irrespective of [read receipts](#receipts) or The user's unread marker in a room is kept under an `m.marked_unread` event in the room's [account data](#client-config). The event may be read -to determine the user's current unread marker state in the room, and just -like other account data events the event will be pushed down the event +to determine the user's current unread marker state in the room. Just +like other account data events, the event will be pushed down the event stream when updated. {{% event event="m.marked_unread" %}}