From 60d2dc75f96216638cee57834814f4115033e0ae Mon Sep 17 00:00:00 2001
From: MadLittleMods <MadLittleMods@users.noreply.github.com>
Date: Wed, 7 Aug 2024 16:29:24 +0000
Subject: deploy: 11db575218d2601384e05519a45d930f34d0b1ae

---
 develop/development/room-dag-concepts.html | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

(limited to 'develop/development')

diff --git a/develop/development/room-dag-concepts.html b/develop/development/room-dag-concepts.html
index 93a6fcd4cb..6ae644c8a2 100644
--- a/develop/development/room-dag-concepts.html
+++ b/develop/development/room-dag-concepts.html
@@ -174,8 +174,10 @@ messages are added to the DAG. Normally, <code>stream_ordering</code> is an auto
 incrementing integer, but backfilled events start with <code>stream_ordering=-1</code> and decrement.</p>
 <hr />
 <ul>
-<li><code>/sync</code> returns things in the order they arrive at the server (<code>stream_ordering</code>).</li>
-<li><code>/messages</code> (and <code>/backfill</code> in the federation API) return them in the order determined by the event graph <code>(topological_ordering, stream_ordering)</code>.</li>
+<li>Incremental <code>/sync?since=xxx</code> returns things in the order they arrive at the server
+(<code>stream_ordering</code>).</li>
+<li>Initial <code>/sync</code>, <code>/messages</code> (and <code>/backfill</code> in the federation API) return them in
+the order determined by the event graph <code>(topological_ordering, stream_ordering)</code>.</li>
 </ul>
 <p>The general idea is that, if you're following a room in real-time (i.e.
 <code>/sync</code>), you probably want to see the messages as they arrive at your server,
-- 
cgit 1.5.1