deploy: 350062661cbc402c089ce7a20b72d83073ed8fec

1 files changed, 2 insertions, 1 deletions

diff --git a/develop/development/room-dag-concepts.html b/develop/development/room-dag-concepts.html

index c206cce3d8..a03d34be03 100644
--- a/develop/development/room-dag-concepts.html
+++ b/develop/development/room-dag-concepts.html
@@ -176,7 +176,8 @@ yet correlated to the DAG.</p>
 <p>Outliers typically arise when we fetch the auth chain or state for a given
 event. When that happens, we just grab the events in the state/auth chain,
 without calculating the state at those events, or backfilling their
-<code>prev_events</code>.</p>
+<code>prev_events</code>. Since we don't have the state at any events fetched in that
+way, we mark them as outliers.</p>
 <p>So, typically, we won't have the <code>prev_events</code> of an <code>outlier</code> in the database,
 (though it's entirely possible that we <em>might</em> have them for some other
 reason). Other things that make outliers different from regular events:</p>