Skip to content

Commit ea1c8c1

Browse files
committed
docs: clarify wording in subscriptions regarding starting positions
1 parent c4a508a commit ea1c8c1

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

docs/api/subscriptions.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -46,12 +46,12 @@ 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

5353
::: warning
54-
The positions provided to the subscriptions are exclusive. You will only receive the next event after the subscribed position.
54+
The positions provided to the subscriptions are **exclusive**. You will only receive the next event after the subscribed position.
5555
:::
5656

5757
**Stream from specific position:**

0 commit comments

Comments
 (0)