From 327bb0eb00d497cc91d5fe3141791a99ec633e8d Mon Sep 17 00:00:00 2001 From: NataliaIvakina <82437520+NataliaIvakina@users.noreply.github.com> Date: Tue, 20 Aug 2024 10:05:22 +0200 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Louise Berglund --- modules/ROOT/pages/notifications/index.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/notifications/index.adoc b/modules/ROOT/pages/notifications/index.adoc index c115fe0..5f1b405 100644 --- a/modules/ROOT/pages/notifications/index.adoc +++ b/modules/ROOT/pages/notifications/index.adoc @@ -185,7 +185,7 @@ The following table lists the Neo4j-defined groups of GQLSTATUS codes and their All server notifications are grouped by category (which is called classification in the GqlStatusObject framework) and severity level, which can be one of `WARNING`, `WARNING OR INFORMATION`, or `INFORMATION`. -The driver-side notification configuration used for filtering notifications by category and severity is the same for both Neo4j and GQLSTATUS notification frameworks. +The driver-side notification configuration used for filtering notifications by category and severity is the same for both Neo4j Notification and GQL-status object frameworks. The driver can filter notifications by category/classification and severity level, and the server will only send notifications that match the driver-side configuration. The driver can also choose to ignore notifications.