From 0b3fb848539ccaaf8f84c87a5d1e29ee7437801e Mon Sep 17 00:00:00 2001 From: William Chong Date: Wed, 4 Mar 2026 11:52:45 +0000 Subject: [PATCH] docs: clarify wording in subscriptions regarding starting positions --- docs/api/subscriptions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/api/subscriptions.md b/docs/api/subscriptions.md index f8b8ca0e..eacc54d0 100644 --- a/docs/api/subscriptions.md +++ b/docs/api/subscriptions.md @@ -46,7 +46,7 @@ When you subscribe to a stream with link events (e.g., `$ce` category stream), s ## Subscribing from a Position -Both stream and `$all` subscriptions accept a starting position if you want to read from a specific point onward. If events already exist at the position you subscribe to, they will be read on the server side and sent to the subscription. +Both stream and `$all` subscriptions accept a starting position if you want to read from a specific point onward. If events already exist after the position you subscribe to, they will be read on the server side and sent to the subscription. Once caught up, the server will push any new events received on the streams to the client. There is no difference between catching up and live on the client side.