From c2dd4b53e9ab2f57331ed3ae5d149917febda035 Mon Sep 17 00:00:00 2001 From: CODe <71spates.bravest@icloud.com> Date: Fri, 31 Jan 2025 22:39:14 +0100 Subject: [PATCH] Fix in the backend-integration.mdx --- docs/appkit/next/notifications/backend-integration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/appkit/next/notifications/backend-integration.mdx b/docs/appkit/next/notifications/backend-integration.mdx index 40d10a58a..fd7414557 100644 --- a/docs/appkit/next/notifications/backend-integration.mdx +++ b/docs/appkit/next/notifications/backend-integration.mdx @@ -211,7 +211,7 @@ curl 'https://notify.walletconnect.com//subscribers' \ Unless marked as read by an app frontend, notifications will always be "unread". Because of this, when you initially add support for displaying unread status or unread count to your frontend, users that have received notifications in the past will have notifications display as "unread" even if they already have seen them. -This can potentially be an undesireable user experience. +This can potentially be an undesirable user experience. To mitigate this problem, you can make a one-time call to the `/v1//mark-all-as-read` API endpoint which will mark all existing notifications as read. Notifications marked as read in this way will not contribute