Skip to content

Commit 23f9064

Browse files
docs: clarify wording in subscriptions regarding starting positions (#381)
Co-authored-by: William Chong <william-chong@outlook.com>
1 parent f3f0be6 commit 23f9064

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

docs/api/subscriptions.md

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

4747
## Subscribing from a Position
4848

49-
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.
49+
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.
5050

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

0 commit comments

Comments
 (0)