From 19a9446185674768070d1aeacae6977305987071 Mon Sep 17 00:00:00 2001 From: Andy Balaam Date: Mon, 27 Nov 2023 17:15:00 +0000 Subject: [PATCH] Reword main timeline ID paragraph --- content/client-server-api/modules/receipts.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/client-server-api/modules/receipts.md b/content/client-server-api/modules/receipts.md index 74e2f1c3..470c099b 100644 --- a/content/client-server-api/modules/receipts.md +++ b/content/client-server-api/modules/receipts.md @@ -145,8 +145,8 @@ considered to be "in a thread" if: depth: a maximum of 3 hops is recommended to cover indirect relationships.) Events not in a thread but still in the room are considered to be in the "main -timeline". Threaded receipts for the main timeline use a special thread ID of -`main`. +timeline". When referring to the main timeline as a thread (e.g. in receipts +and notifications counts) a special thread ID of `main` is used. Thread roots are considered to be in the main timeline, as are events that are related to a thread root via non-thread relations. Note that clients providing a