From d3e6976968295354d58eb783442f46e8b40156d2 Mon Sep 17 00:00:00 2001 From: Nikolas Date: Fri, 24 May 2024 13:52:43 +0200 Subject: [PATCH] Update content/400-pulse/400-api-reference.mdx Co-authored-by: Petra Donka --- content/400-pulse/400-api-reference.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/400-pulse/400-api-reference.mdx b/content/400-pulse/400-api-reference.mdx index 7553985104..64041c9c21 100644 --- a/content/400-pulse/400-api-reference.mdx +++ b/content/400-pulse/400-api-reference.mdx @@ -282,7 +282,7 @@ const subscription = await prisma.user.subscribe({ ## `stream()` vs `subscribe()` -For the majority of use cases, `stream()` is the recommended option because can provide guarantees for events to arrive on the consumer-side. Note though that because `stream()` requires event persistence to be enabled, this has implications for [pricing](https://www.prisma.io/pricing). +For the majority of use cases, `stream()` is the recommended option because it can provide guarantees for events to arrive on the consumer-side. Note though that because `stream()` requires event persistence to be enabled, this has implications for [event storage and costs](https://www.prisma.io/pricing). See a [more detailed comparison](/pulse/database-events#event-delivery-semantics-in-prisma-pulse).