Skip to content

Commit 022bc40

Browse files
docs: clarify wording in subscriptions regarding starting positions (#457)
Co-authored-by: William Chong <william-chong@outlook.com>
1 parent bf3ba3d commit 022bc40

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/api/subscriptions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ When you subscribe to a stream with link events (e.g., `$ce` category stream), s
4545

4646
## Subscribing from a Position
4747

48-
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.
48+
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.
4949

5050
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.
5151

0 commit comments

Comments
 (0)