From c3e902ae4aebba4ff81d1254e44008ee638a1595 Mon Sep 17 00:00:00 2001
From: Reneta Popova <reneta.popova@neo4j.com>
Date: Tue, 22 Oct 2024 17:19:29 +0100
Subject: [PATCH 01/18] add 42 codes

---
 modules/ROOT/pages/errors/gql-errors.adoc | 188 +++++++++++++++++++++-
 1 file changed, 187 insertions(+), 1 deletion(-)

diff --git a/modules/ROOT/pages/errors/gql-errors.adoc b/modules/ROOT/pages/errors/gql-errors.adoc
index 320aa723..94c00246 100644
--- a/modules/ROOT/pages/errors/gql-errors.adoc
+++ b/modules/ROOT/pages/errors/gql-errors.adoc
@@ -304,6 +304,14 @@ Status description:: error: invalid transaction termination - inner transactions
 
 Transaction rollback errors occur when there is a failure in a transaction or a constituent transaction rollback.
 
+=== 40000
+
+Status description:: error: transaction rollback
+
+=== 40003
+
+Status description:: error: transaction rollback - statement completion unknown
+
 === 40N01
 
 Status description:: error: transaction rollback - rollback failed. Failed to rollback transaction. See debug log for details.
@@ -317,10 +325,124 @@ Status description:: error: transaction rollback - constituent rollback failed.
 
 Syntax error or access rule violation errors occur when a Cypher query contains invalid syntax or when a client request violates the access rules, such as when a query tries to access a database without enough privileges, etc.
 
+=== 42000
+
+Status description:: error: syntax error or access rule violation
+
+=== 42001
+
+Status description:: error: syntax error or access rule violation - invalid syntax
+
+=== 42002
+
+Status description:: error: syntax error or access rule violation - invalid reference
+
+=== 42004
+
+Status description:: error: syntax error or access rule violation - use of visually confusable identifiers
+
+=== 42006
+
+Status description:: error: syntax error or access rule violation - number of edge labels below supported minimum
+
+=== 42007
+
+Status description:: error: syntax error or access rule violation - number of edge labels exceeds supported maximum
+
+=== 42008
+
+Status description:: error: syntax error or access rule violation - number of edge properties exceeds supported maximum
+
+=== 42009
+
+Status description:: error: syntax error or access rule violation - number of node labels below supported minimum
+
+=== 42010
+
+Status description:: error: syntax error or access rule violation - number of node labels exceeds supported maximum
+
+=== 42011
+
+Status description:: error: syntax error or access rule violation - number of node properties exceeds supported maximum
+
+=== 42012
+
+Status description:: error: syntax error or access rule violation - number of node type key labels below supported minimum
+
+=== 42013
+
+Status description:: error: syntax error or access rule violation - number of node type key labels exceeds supported maximum
+
+=== 42014
+
+Status description:: error: syntax error or access rule violation - number of edge type key labels below supported minimum
+
+=== 42015
+
+Status description:: error: syntax error or access rule violation - number of edge type key labels exceeds supported maximum
+
+=== 42I00
+
+Status description:: error: syntax error or access rule violation - invalid case expression. 'CASE' expressions must have the same number of 'WHEN' and 'THEN' operands.
+
+=== 42I01
+
+Status description:: error: syntax error or access rule violation - invalid FOREACH. Invalid use of `{ $clause }` inside 'FOREACH'.
+
+=== 42I02
+
+Status description:: error: syntax error or access rule violation - invalid comment. Failed to parse comment. A comment starting with `'/*'` must also have a closing `'*/'`.
+
+=== 42I06
+
+Status description:: error: syntax error or access rule violation - invalid input. Invalid input `{ $input1 }`, expected: `{ $input2 }`.
+
+=== 42I18
+
+Status description:: error: syntax error or access rule violation - invalid reference to implicitly grouped expressions. The aggregation column contains implicit grouping expressions referenced by the variables `{ $varList }`. Implicit grouping expressions are variables not explicitly declared as grouping keys.
+
+
+=== 42I20
+
+Status description:: error: syntax error or access rule violation - invalid symbol in expression. Label expressions and relationship type expressions cannot contain `{ $input }`. To express a label disjunction use `{ $labelExpr }` instead.
+
+=== 42I25
+
+Status description:: error: syntax error or access rule violation - invalid use of CALL IN TRANSACTIONS. 'CALL { ... } IN TRANSACTIONS' is not supported after a write clause.
+
+=== 42I29
+
+Status description:: error: syntax error or access rule violation - invalid use of IS. The IS keyword cannot be used together with multiple labels in `{ $input }`. Rewrite the expression as `{ $replacement }`.
+
+=== 42I31
+
+Status description:: error: syntax error or access rule violation - invalid use of MATCH. MATCH ...' cannot directly follow an 'OPTIONAL MATCH ...'. Use a WITH clause between them.
+
+
+=== 42I37
+
+Status description:: error: syntax error or access rule violation - invalid use of `RETURN *`. `RETURN *'` is not allowed when there are no variables in scope.
+
+=== 42I38
+
+Status description:: error: syntax error or access rule violation - invalid use of `RETURN`. `RETURN ...'` can only be used at the end of a query or subquery.
+
+=== 42I40
+
+Status description:: error: syntax error or access rule violation - invalid use of `UNION and UNION ALL`. `UNION` and `UNION ALL` cannot be combined.
+
+=== 42I47
+
+Status description:: error: syntax error or access rule violation - parser error. Parser Error: `{ $msg }`.
+
 === 42I50
 
 Status description:: error: syntax error or access rule violation - token name too long. Invalid input { $input }... A { $tokenType } name cannot be longer than { $maxTokenLength }.
 
+=== 42N00
+
+Status description:: error: syntax error or access rule violation - no such database. The database `{ $db }` was not found. Verify that the spelling is correct.
+
 === 42N01
 
 Status description:: error: syntax error or access rule violation - no such constituent graph exists in composite database. The constituent graph { $graph } was not found in the in composite database { $db }. Verify that the spelling is correct.
@@ -389,14 +511,61 @@ Status description:: error: syntax error or access rule violation - unsupported
 
 Status description:: error: syntax error or access rule violation - unsupported request. { $input } is not allowed on the system database.
 
+=== 42N19
+
+Status description:: error: syntax error or access rule violation - duplicate clause. Duplicate `{ $syntax }` clause.
+
+=== 42N20
+
+Status description:: error: syntax error or access rule violation - empty list range operator. The list range operator `'[ ]'` cannot be empty.
+
+
+=== 42N21
+
+Status description:: error: syntax error or access rule violation - unaliased return item. Expression in `{ $clause }` must be aliased (use AS).
+
+
+=== 42N22
+
+Status description:: error: syntax error or access rule violation - single return column required. A COLLECT subquery must end with a single return column.
+
+=== 42N29
+
+Status description:: error: syntax error or access rule violation - unbound variables in pattern expression. Pattern expressions are not allowed to introduce new variables: `{ $var }`.
+
+=== 42N39
+
+Status description:: error: syntax error or access rule violation - incompatible return columns. All subqueries in a UNION clause must have the same return column names.
+
+=== 42N45
+
+Status description:: error: syntax error or access rule violation - unexpected end of input. Unexpected end of input, expected 'CYPHER', 'EXPLAIN', 'PROFILE' or a query.
+
 === 42N49
 
 Status description:: error: syntax error or access rule violation - unsupported normal form. Unknown Normal Form: { $input }.
 
+=== 42N57
+
+Status description:: error: syntax error or access rule violation - invalid use of data-modifications in expressions. `{ $expr }` cannot contain any updating clauses.
+
+=== 42N70
+
+Status description:: error: syntax error or access rule violation - function without required WHERE clause. The function `{ $fun }` requires a WHERE clause.
+
 === 42N75
 
 Status description:: error: syntax error or access rule violation - invalid use of graph function. A call to the graph function { $fun } is only allowed as the top-level argument of a USE clause.
 
+=== 42N76
+
+Status description:: error: syntax error or access rule violation - unfulfillable hints. The hint(s) `{ $hintAndedList }` cannot be fulfilled.
+
+=== 42N78
+
+Status description:: error: syntax error or access rule violation - variable already bound. Node `{ $var }` has already been bound and cannot be modified by the `{ $clause }` clause.
+
+
 === 42N83
 
 Status description:: error: syntax error or access rule violation - impersonation disallowed while password change required. Cannot impersonate a user while password change required.
@@ -409,6 +578,10 @@ Status description:: error: syntax error or access rule violation - TERMINATE TR
 
 Status description:: error: syntax error or access rule violation - cannot specify both allowed and denied databases. Allowed and denied database options are mutually exclusive.
 
+=== 42N86
+
+Status description:: error: syntax error or access rule violation - wildcard in parameter. `{ $syntax }` failed. Parameterized database and graph names do not support wildcards.
+
 === 42N88
 
 Status description:: error: syntax error or access rule violation - cannot grant privilege. Permission cannot be granted for 'REMOVE IMMUTABLE PRIVILEGE'.
@@ -421,6 +594,19 @@ Status description:: error: syntax error or access rule violation - invalid driv
 
 Status description:: error: syntax error or access rule violation - cannot alter immutable composite database. Composite databases cannot be altered (database: { $db }).
 
+=== 42N97
+
+Status description:: error: syntax error or access rule violation - missing mandatory auth clause. Clause `{ $clause }` is mandatory for auth provider `{ $auth }`.
+
+
+=== 42N98
+
+Status description:: error: syntax error or access rule violation - cannot modify own user. Cannot modify the user record of the current user.
+
+=== 42N99
+
+Status description:: error: syntax error or access rule violation - cannot delete own user. Cannot delete the user record of the current user.
+
 === 42NFD
 
 Status description:: error: syntax error or access rule violation - credentials expired. Permission denied. The credentials you provided were valid, but must be changed before you can use this instance.
@@ -810,4 +996,4 @@ Status description:: error: procedure exception - wrong database. Change identif
 
 === 52N32
 
-Status description:: error: procedure exception - invalid sequence number. Change identifier `{ $param1 }` has an invalid sequence number `{ $param2 }`.
\ No newline at end of file
+Status description:: error: procedure exception - invalid sequence number. Change identifier `{ $param1 }` has an invalid sequence number `{ $param2 }`.

From 09c9a50e8af10f956fe517dfef303bffadec8cbd Mon Sep 17 00:00:00 2001
From: Reneta Popova <reneta.popova@neo4j.com>
Date: Thu, 24 Oct 2024 14:24:12 +0100
Subject: [PATCH 02/18] Update modules/ROOT/pages/errors/gql-errors.adoc

Co-authored-by: Louise Berglund <louise.berglund@neo4j.com>
---
 modules/ROOT/pages/errors/gql-errors.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/modules/ROOT/pages/errors/gql-errors.adoc b/modules/ROOT/pages/errors/gql-errors.adoc
index 94c00246..5d719956 100644
--- a/modules/ROOT/pages/errors/gql-errors.adoc
+++ b/modules/ROOT/pages/errors/gql-errors.adoc
@@ -399,7 +399,7 @@ Status description:: error: syntax error or access rule violation - invalid inpu
 
 === 42I18
 
-Status description:: error: syntax error or access rule violation - invalid reference to implicitly grouped expressions. The aggregation column contains implicit grouping expressions referenced by the variables `{ $varList }`. Implicit grouping expressions are variables not explicitly declared as grouping keys.
+Status description:: error: syntax error or access rule violation - invalid reference to implicitly grouped expressions. The aggregation column contains implicit grouping expressions referenced by the variables `{ $variableList }`. Implicit grouping expressions are variables not explicitly declared as grouping keys.
 
 
 === 42I20

From 3fdd17189042a86daa211f5d9fcd6162a6041edb Mon Sep 17 00:00:00 2001
From: Reneta Popova <reneta.popova@neo4j.com>
Date: Thu, 24 Oct 2024 14:24:59 +0100
Subject: [PATCH 03/18] Update modules/ROOT/pages/errors/gql-errors.adoc

Co-authored-by: Louise Berglund <louise.berglund@neo4j.com>
---
 modules/ROOT/pages/errors/gql-errors.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/modules/ROOT/pages/errors/gql-errors.adoc b/modules/ROOT/pages/errors/gql-errors.adoc
index 5d719956..da8454e8 100644
--- a/modules/ROOT/pages/errors/gql-errors.adoc
+++ b/modules/ROOT/pages/errors/gql-errors.adoc
@@ -416,7 +416,7 @@ Status description:: error: syntax error or access rule violation - invalid use
 
 === 42I31
 
-Status description:: error: syntax error or access rule violation - invalid use of MATCH. MATCH ...' cannot directly follow an 'OPTIONAL MATCH ...'. Use a WITH clause between them.
+Status description:: error: syntax error or access rule violation - invalid use of MATCH. 'MATCH ...' cannot directly follow an 'OPTIONAL MATCH ...'. Use a WITH clause between them.
 
 
 === 42I37

From 7dbe23afe8982cdb31401f05df018a1d86aeae1d Mon Sep 17 00:00:00 2001
From: Reneta Popova <reneta.popova@neo4j.com>
Date: Thu, 24 Oct 2024 14:25:08 +0100
Subject: [PATCH 04/18] Update modules/ROOT/pages/errors/gql-errors.adoc

Co-authored-by: Louise Berglund <louise.berglund@neo4j.com>
---
 modules/ROOT/pages/errors/gql-errors.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/modules/ROOT/pages/errors/gql-errors.adoc b/modules/ROOT/pages/errors/gql-errors.adoc
index da8454e8..09478bea 100644
--- a/modules/ROOT/pages/errors/gql-errors.adoc
+++ b/modules/ROOT/pages/errors/gql-errors.adoc
@@ -421,7 +421,7 @@ Status description:: error: syntax error or access rule violation - invalid use
 
 === 42I37
 
-Status description:: error: syntax error or access rule violation - invalid use of `RETURN *`. `RETURN *'` is not allowed when there are no variables in scope.
+Status description:: error: syntax error or access rule violation - invalid use of `RETURN *`. `'RETURN *'` is not allowed when there are no variables in scope.
 
 === 42I38
 

From f536005b225a68788a452705bbb5c259d6f8df1c Mon Sep 17 00:00:00 2001
From: Reneta Popova <reneta.popova@neo4j.com>
Date: Thu, 24 Oct 2024 14:25:14 +0100
Subject: [PATCH 05/18] Update modules/ROOT/pages/errors/gql-errors.adoc

Co-authored-by: Louise Berglund <louise.berglund@neo4j.com>
---
 modules/ROOT/pages/errors/gql-errors.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/modules/ROOT/pages/errors/gql-errors.adoc b/modules/ROOT/pages/errors/gql-errors.adoc
index 09478bea..64c2735b 100644
--- a/modules/ROOT/pages/errors/gql-errors.adoc
+++ b/modules/ROOT/pages/errors/gql-errors.adoc
@@ -425,7 +425,7 @@ Status description:: error: syntax error or access rule violation - invalid use
 
 === 42I38
 
-Status description:: error: syntax error or access rule violation - invalid use of `RETURN`. `RETURN ...'` can only be used at the end of a query or subquery.
+Status description:: error: syntax error or access rule violation - invalid use of `RETURN`. `'RETURN ...'` can only be used at the end of a query or subquery.
 
 === 42I40
 

From 8d8253aba19c2bc6f1a416036214293bedb58a1f Mon Sep 17 00:00:00 2001
From: Reneta Popova <reneta.popova@neo4j.com>
Date: Thu, 24 Oct 2024 14:25:39 +0100
Subject: [PATCH 06/18] Update modules/ROOT/pages/errors/gql-errors.adoc

Co-authored-by: Louise Berglund <louise.berglund@neo4j.com>
---
 modules/ROOT/pages/errors/gql-errors.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/modules/ROOT/pages/errors/gql-errors.adoc b/modules/ROOT/pages/errors/gql-errors.adoc
index 64c2735b..6968749f 100644
--- a/modules/ROOT/pages/errors/gql-errors.adoc
+++ b/modules/ROOT/pages/errors/gql-errors.adoc
@@ -429,7 +429,7 @@ Status description:: error: syntax error or access rule violation - invalid use
 
 === 42I40
 
-Status description:: error: syntax error or access rule violation - invalid use of `UNION and UNION ALL`. `UNION` and `UNION ALL` cannot be combined.
+Status description:: error: syntax error or access rule violation - invalid use of `UNION` and `UNION ALL`. `UNION` and `UNION ALL` cannot be combined.
 
 === 42I47
 

From 958d9f2604520936986461a678f772442e7a9322 Mon Sep 17 00:00:00 2001
From: Reneta Popova <reneta.popova@neo4j.com>
Date: Thu, 24 Oct 2024 14:26:24 +0100
Subject: [PATCH 07/18] Update modules/ROOT/pages/errors/gql-errors.adoc

Co-authored-by: Louise Berglund <louise.berglund@neo4j.com>
---
 modules/ROOT/pages/errors/gql-errors.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/modules/ROOT/pages/errors/gql-errors.adoc b/modules/ROOT/pages/errors/gql-errors.adoc
index 6968749f..93a15af7 100644
--- a/modules/ROOT/pages/errors/gql-errors.adoc
+++ b/modules/ROOT/pages/errors/gql-errors.adoc
@@ -531,7 +531,7 @@ Status description:: error: syntax error or access rule violation - single retur
 
 === 42N29
 
-Status description:: error: syntax error or access rule violation - unbound variables in pattern expression. Pattern expressions are not allowed to introduce new variables: `{ $var }`.
+Status description:: error: syntax error or access rule violation - unbound variables in pattern expression. Pattern expressions are not allowed to introduce new variables: `{ $variable }`.
 
 === 42N39
 

From 75e17559f945c927263b430dff65614a6b39813f Mon Sep 17 00:00:00 2001
From: Reneta Popova <reneta.popova@neo4j.com>
Date: Thu, 24 Oct 2024 14:26:41 +0100
Subject: [PATCH 08/18] Update modules/ROOT/pages/errors/gql-errors.adoc

Co-authored-by: Louise Berglund <louise.berglund@neo4j.com>
---
 modules/ROOT/pages/errors/gql-errors.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/modules/ROOT/pages/errors/gql-errors.adoc b/modules/ROOT/pages/errors/gql-errors.adoc
index 93a15af7..465bd629 100644
--- a/modules/ROOT/pages/errors/gql-errors.adoc
+++ b/modules/ROOT/pages/errors/gql-errors.adoc
@@ -559,7 +559,7 @@ Status description:: error: syntax error or access rule violation - invalid use
 
 === 42N76
 
-Status description:: error: syntax error or access rule violation - unfulfillable hints. The hint(s) `{ $hintAndedList }` cannot be fulfilled.
+Status description:: error: syntax error or access rule violation - unfulfillable hints. The hint(s) `{ $hintList }` cannot be fulfilled.
 
 === 42N78
 

From 930ff56999e68462d37a7cc618beb071513909fa Mon Sep 17 00:00:00 2001
From: Reneta Popova <reneta.popova@neo4j.com>
Date: Thu, 24 Oct 2024 14:26:47 +0100
Subject: [PATCH 09/18] Update modules/ROOT/pages/errors/gql-errors.adoc

Co-authored-by: Louise Berglund <louise.berglund@neo4j.com>
---
 modules/ROOT/pages/errors/gql-errors.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/modules/ROOT/pages/errors/gql-errors.adoc b/modules/ROOT/pages/errors/gql-errors.adoc
index 465bd629..b56546f1 100644
--- a/modules/ROOT/pages/errors/gql-errors.adoc
+++ b/modules/ROOT/pages/errors/gql-errors.adoc
@@ -563,7 +563,7 @@ Status description:: error: syntax error or access rule violation - unfulfillabl
 
 === 42N78
 
-Status description:: error: syntax error or access rule violation - variable already bound. Node `{ $var }` has already been bound and cannot be modified by the `{ $clause }` clause.
+Status description:: error: syntax error or access rule violation - variable already bound. Node `{ $variable }` has already been bound and cannot be modified by the `{ $clause }` clause.
 
 
 === 42N83

From c49da67fea4f756351901ae61ab361ed3bcbd7b0 Mon Sep 17 00:00:00 2001
From: Reneta Popova <reneta.popova@neo4j.com>
Date: Thu, 24 Oct 2024 14:34:50 +0100
Subject: [PATCH 10/18] Update modules/ROOT/pages/errors/gql-errors.adoc

---
 modules/ROOT/pages/errors/gql-errors.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/modules/ROOT/pages/errors/gql-errors.adoc b/modules/ROOT/pages/errors/gql-errors.adoc
index b56546f1..7e38c706 100644
--- a/modules/ROOT/pages/errors/gql-errors.adoc
+++ b/modules/ROOT/pages/errors/gql-errors.adoc
@@ -408,7 +408,7 @@ Status description:: error: syntax error or access rule violation - invalid symb
 
 === 42I25
 
-Status description:: error: syntax error or access rule violation - invalid use of CALL IN TRANSACTIONS. 'CALL { ... } IN TRANSACTIONS' is not supported after a write clause.
+Status description:: error: syntax error or access rule violation - invalid use of `CALL IN TRANSACTIONS`. 'CALL { ... } IN TRANSACTIONS' is not supported after a write clause.
 
 === 42I29
 

From e5bccb751d9b0762971ebb64d40d45d09c28539c Mon Sep 17 00:00:00 2001
From: Reneta Popova <reneta.popova@neo4j.com>
Date: Thu, 24 Oct 2024 14:35:05 +0100
Subject: [PATCH 11/18] Update modules/ROOT/pages/errors/gql-errors.adoc

---
 modules/ROOT/pages/errors/gql-errors.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/modules/ROOT/pages/errors/gql-errors.adoc b/modules/ROOT/pages/errors/gql-errors.adoc
index 7e38c706..5f216bd3 100644
--- a/modules/ROOT/pages/errors/gql-errors.adoc
+++ b/modules/ROOT/pages/errors/gql-errors.adoc
@@ -416,7 +416,7 @@ Status description:: error: syntax error or access rule violation - invalid use
 
 === 42I31
 
-Status description:: error: syntax error or access rule violation - invalid use of MATCH. 'MATCH ...' cannot directly follow an 'OPTIONAL MATCH ...'. Use a WITH clause between them.
+Status description:: error: syntax error or access rule violation - invalid use of `MATCH`. 'MATCH ...' cannot directly follow an 'OPTIONAL MATCH ...'. Use a WITH clause between them.
 
 
 === 42I37

From 292c8376bf39f695f08703d6fd1c01c73037fb19 Mon Sep 17 00:00:00 2001
From: Reneta Popova <reneta.popova@neo4j.com>
Date: Thu, 24 Oct 2024 14:35:39 +0100
Subject: [PATCH 12/18] Update modules/ROOT/pages/errors/gql-errors.adoc

---
 modules/ROOT/pages/errors/gql-errors.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/modules/ROOT/pages/errors/gql-errors.adoc b/modules/ROOT/pages/errors/gql-errors.adoc
index 5f216bd3..afaa4be8 100644
--- a/modules/ROOT/pages/errors/gql-errors.adoc
+++ b/modules/ROOT/pages/errors/gql-errors.adoc
@@ -412,7 +412,7 @@ Status description:: error: syntax error or access rule violation - invalid use
 
 === 42I29
 
-Status description:: error: syntax error or access rule violation - invalid use of IS. The IS keyword cannot be used together with multiple labels in `{ $input }`. Rewrite the expression as `{ $replacement }`.
+Status description:: error: syntax error or access rule violation - invalid use of `IS`. The `IS` keyword cannot be used together with multiple labels in `{ $input }`. Rewrite the expression as `{ $replacement }`.
 
 === 42I31
 

From 28de429ca2afe7e4dce0f5a84817dc20f4abf344 Mon Sep 17 00:00:00 2001
From: Reneta Popova <reneta.popova@neo4j.com>
Date: Thu, 24 Oct 2024 14:36:10 +0100
Subject: [PATCH 13/18] Update modules/ROOT/pages/errors/gql-errors.adoc

---
 modules/ROOT/pages/errors/gql-errors.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/modules/ROOT/pages/errors/gql-errors.adoc b/modules/ROOT/pages/errors/gql-errors.adoc
index afaa4be8..ddbaf574 100644
--- a/modules/ROOT/pages/errors/gql-errors.adoc
+++ b/modules/ROOT/pages/errors/gql-errors.adoc
@@ -527,7 +527,7 @@ Status description:: error: syntax error or access rule violation - unaliased re
 
 === 42N22
 
-Status description:: error: syntax error or access rule violation - single return column required. A COLLECT subquery must end with a single return column.
+Status description:: error: syntax error or access rule violation - single return column required. A `COLLECT` subquery must end with a single return column.
 
 === 42N29
 

From 8fe93874587a9e43413c6d1a38a4d86152bc7482 Mon Sep 17 00:00:00 2001
From: Reneta Popova <reneta.popova@neo4j.com>
Date: Thu, 24 Oct 2024 14:45:57 +0100
Subject: [PATCH 14/18] add backticks around parameters

---
 modules/ROOT/pages/errors/gql-errors.adoc | 140 +++++++++++-----------
 1 file changed, 70 insertions(+), 70 deletions(-)

diff --git a/modules/ROOT/pages/errors/gql-errors.adoc b/modules/ROOT/pages/errors/gql-errors.adoc
index ddbaf574..307e8a62 100644
--- a/modules/ROOT/pages/errors/gql-errors.adoc
+++ b/modules/ROOT/pages/errors/gql-errors.adoc
@@ -21,32 +21,32 @@ Status description:: error: connection exception - transaction resolution unknow
 
 === 08N00
 
-Status description:: error: connection exception - unable to connect to database. Unable to connect to database { $db }. Unable to get bolt address of the leader. Check the status of the database. Retrying your request at a later time may succeed.
+Status description:: error: connection exception - unable to connect to database. Unable to connect to database `{ $db }`. Unable to get bolt address of the leader. Check the status of the database. Retrying your request at a later time may succeed.
 
 
 === 08N01
 
-Status description:: error: connection exception - unable to write to database. Unable to write to database { $db } on this server. Server-side routing is disabled. Either connect to the database leader directly or enable server-side routing by setting '{ $cfgSetting }=true'.
+Status description:: error: connection exception - unable to write to database. Unable to write to database `{ $db }` on this server. Server-side routing is disabled. Either connect to the database leader directly or enable server-side routing by setting '{ $cfgSetting }=true'.
 
 //Possible solutions:
-//Either connect to the database directly using the driver or interactively with the `:use { $db }` command), or enable server-side routing by setting `dbms.routing.enabled=true` in the configuration.
+//Either connect to the database directly using the driver or interactively with the `:use `{ $db }` command), or enable server-side routing by setting `dbms.routing.enabled=true` in the configuration.
 
 === 08N02
 
-Status description:: error: connection exception - unable to connect to database. Unable to connect to database { $db }. Server-side routing is disabled. Either connect to { $db } directly, or enable server-side routing by setting '{ $cfgSetting }=true'.
+Status description:: error: connection exception - unable to connect to database. Unable to connect to database `{ $db }`. Server-side routing is disabled. Either connect to `{ $db }` directly, or enable server-side routing by setting '{ $cfgSetting }=true'.
 
 Example error description:: error: connection exception - unable to route to database. Unable to connect to database `my_db`. Server-side routing is disabled. Either connect to `my_db` directly, or enable server-side routing by setting 'dbms.routing.enabled=true'.
 
 //Possible solutions:
-//Either connect to the database directly using the driver or interactively with the `:use { $db }` command), or enable server-side routing by setting `dbms.routing.enabled=true` in the configuration.
+//Either connect to the database directly using the driver or interactively with the `:use `{ $db }` command), or enable server-side routing by setting `dbms.routing.enabled=true` in the configuration.
 
 === 08N03
 
-Status description:: error: connection exception - failed to write to graph. Failed to write to graph { $graph }. Check the defined access mode in both driver and database.
+Status description:: error: connection exception - failed to write to graph. Failed to write to graph `{ $graph }`. Check the defined access mode in both driver and database.
 
 === 08N04
 
-Status description:: error: unable to route use clause. Routing with { $clause } is not supported in embedded sessions. Connect to the database directly or try running the query using a Neo4j driver or the HTTP API.
+Status description:: error: unable to route use clause. Routing with `{ $clause }` is not supported in embedded sessions. Connect to the database directly or try running the query using a Neo4j driver or the HTTP API.
 
 === 08N05
 
@@ -69,11 +69,11 @@ Status description:: error: connection exception - database is read only. This d
 
 === 08N09
 
-Status description:: error: connection exception - database unavailable. The database { $db } is currently unavailable. Check the database status. Retry your request at a later time.
+Status description:: error: connection exception - database unavailable. The database `{ $db }` is currently unavailable. Check the database status. Retry your request at a later time.
 
 === 08N10
 
-Status description:: error: connection exception - invalid server state. The server is not in a state that can process a message of type: { $boltMsgType }.
+Status description:: error: connection exception - invalid server state. The server is not in a state that can process a message of type: `{ $boltMsgType }`.
 
 === 08N11
 
@@ -85,15 +85,15 @@ Status description:: error: connection exception - failed to parse bookmark. Fai
 
 === 08N13
 
-Status description:: error: connection exception - database not up to requested bookmark. The database { $db } is not up to the requested bookmark { $transactionId1 }. The latest transaction ID is { $transactionId2 }.
+Status description:: error: connection exception - database not up to requested bookmark. The database `{ $db }` is not up to the requested bookmark `{ $transactionId1 }`. The latest transaction ID is `{ $transactionId2 }`.
 
 === 08N14
 
-Status description:: error: connection exception - alias chains are not permitted. Unable to provide a routing table for the database identifed by the alias { $alias1 } because the request comes from another alias { $alias2 } and alias chains are not permitted.
+Status description:: error: connection exception - alias chains are not permitted. Unable to provide a routing table for the database identifed by the alias `{ $alias1 }` because the request comes from another alias `{ $alias2 }` and alias chains are not permitted.
 
 === 08N15
 
-Status description:: error: connection exception - no such routing policy. Policy definition of the routing policy { $routingPolicy } could not be found. Verify that the spelling is correct.
+Status description:: error: connection exception - no such routing policy. Policy definition of the routing policy `{ $routingPolicy }` could not be found. Verify that the spelling is correct.
 
 == Data exceptions
 
@@ -107,51 +107,51 @@ Status description:: error: data exception - unsupported value. The provided val
 === 22N01
 
 Status description:: error: data exception - invalid type.
-Expected the value { $value } to be of type { $valueTypeList }, but was of type { $valueType }.
+Expected the value `{ $value }` to be of type `{ $valueTypeList }, but was of type `{ $valueType }`.
 
 === 22N02
 
-Status description:: error: data exception - specified negative numeric value. Expected { $option } to be a positive number but found { $value } instead.
+Status description:: error: data exception - specified negative numeric value. Expected `{ $option }` to be a positive number but found `{ $value }` instead.
 
 === 22N03
 
-Status description:: error: data exception - specified numeric value out of range. Expected { $component } to be of type { $valueType } and in the range { $lower }  to { $upper } but found { $value }.
+Status description:: error: data exception - specified numeric value out of range. Expected `{ $component }` to be of type `{ $valueType }` and in the range `{ $lower }`  to `{ $upper }` but found `{ $value }`.
 
 === 22N04
 
-Status description:: error: data exception - invalid input value. Invalid input { $input } for { $context }. Expected one of { $inputList }.
+Status description:: error: data exception - invalid input value. Invalid input `{ $input }` for `{ $context }`. Expected one of `{ $inputList }`.
 
 === 22N05
 
-Status description:: error: data exception - input failed validation. Invalid input { $input } for { $context }.
+Status description:: error: data exception - input failed validation. Invalid input `{ $input }` for `{ $context }`.
 
 === 22N06
 
-Status description:: error: data exception - empty input string. Invalid input. { $option } needs to be specified.
+Status description:: error: data exception - empty input string. Invalid input. `{ $option }` needs to be specified.
 
 === 22N07
 
-Status description:: error: data exception - invalid pre-parser option key. Invalid pre-parser option(s): { $optionList }.
+Status description:: error: data exception - invalid pre-parser option key. Invalid pre-parser option(s): `{ $optionList }`.
 
 === 22N08
 
-Status description:: error: data exception - invalid pre-parser combination. Invalid pre-parser option, cannot combine { $option1 } with { $option2 }.
+Status description:: error: data exception - invalid pre-parser combination. Invalid pre-parser option, cannot combine `{ $option1 }` with `{ $option2 }`.
 
 === 22N09
 
-Status description:: error: data exception - conflicting pre-parser combination. Invalid pre-parser option, cannot specify multiple conflicting values for { $option }.
+Status description:: error: data exception - conflicting pre-parser combination. Invalid pre-parser option, cannot specify multiple conflicting values for `{ $option }`.
 
 === 22N10
 
-Status description:: error: data exception - invalid pre-parser option value. Invalid pre-parser option, specified { $input } is not valid for option { $option }. Valid options are: { $optionList }.
+Status description:: error: data exception - invalid pre-parser option value. Invalid pre-parser option, specified `{ $input }` is not valid for option `{ $option }`. Valid options are: `{ $optionList }`.
 
 === 22N11
 
-Status description:: error: data exception - invalid argument. Invalid argument: cannot process { $input }.
+Status description:: error: data exception - invalid argument. Invalid argument: cannot process `{ $input }`.
 
 === 22N12
 
-Status description:: error: data exception - invalid date, time, or datetime format. Invalid argument: cannot process { $input }.
+Status description:: error: data exception - invalid date, time, or datetime format. Invalid argument: cannot process `{ $input }`.
 
 === 22N13
 
@@ -159,23 +159,23 @@ Status description:: error: data exception - invalid time zone. Specified time z
 
 === 22N14
 
-Status description:: error: data exception - invalid temporal value combination. Cannot select both { $temporal } and { $component }.
+Status description:: error: data exception - invalid temporal value combination. Cannot select both `{ $temporal }` and `{ $component }`.
 
 === 22N15
 
-Status description:: error: data exception - invalid temporal component. Cannot read the specified { $component } component from { $temporal }.
+Status description:: error: data exception - invalid temporal component. Cannot read the specified `{ $component }` component from `{ $temporal }`.
 
 === 22N16
 
-Status description:: error: data exception - invalid import value. Importing entity values to a graph with a USE clause is not supported. Attempted to import { $expr } to { $graph }.
+Status description:: error: data exception - invalid import value. Importing entity values to a graph with a USE clause is not supported. Attempted to import `{ $expr }` to `{ $graph }`.
 
 // === 22N17
 
-// Status description:: error: data exception - invalid date, time, or datetime function field name. Cannot read the specified { $component } component from { $temporal }.
+// Status description:: error: data exception - invalid date, time, or datetime function field name. Cannot read the specified `{ $component }` component from `{ $temporal }`.
 
 === 22N18
 
-Status description:: error: data exception - incomplete spatial value. A { $crs } POINT must contain { $mapKeyList }.
+Status description:: error: data exception - incomplete spatial value. A `{ $crs }` POINT must contain `{ $mapKeyList }`.
 
 === 22N19
 
@@ -183,11 +183,11 @@ Status description:: error: data exception - invalid spatial value. A POINT must
 
 === 22N20
 
-Status description:: error: data exception - invalid spatial value dimensions. Cannot create POINT with { $dim1 }D coordinate reference system (CRS) and { $value } coordinates. Use the equivalent { $dim2 }D coordinate reference system instead.
+Status description:: error: data exception - invalid spatial value dimensions. Cannot create POINT with `{ $dim1 }D coordinate reference system (CRS) and `{ $value }` coordinates. Use the equivalent `{ $dim2 }D coordinate reference system instead.
 
 === 22N21
 
-Status description:: error: data exception - unsupported coordinate reference system. Unsupported coordinate reference system (CRS): { $crs }.
+Status description:: error: data exception - unsupported coordinate reference system. Unsupported coordinate reference system (CRS): `{ $crs }`.
 
 === 22N22
 
@@ -195,15 +195,15 @@ Status description:: error: data exception - invalid spatial value combination.
 
 === 22N23
 
-Status description:: error: data exception - invalid latitude value. Cannot create WGS84 POINT with invalid coordinate: { $coordinates }. The valid range for the latitude coordinate is [-90, 90].
+Status description:: error: data exception - invalid latitude value. Cannot create WGS84 POINT with invalid coordinate: `{ $coordinates }`. The valid range for the latitude coordinate is [-90, 90].
 
 === 22N24
 
-Status description:: error: data exception - invalid coordinate arguments. Cannot construct a { $valueType } from { $coordinates }.
+Status description:: error: data exception - invalid coordinate arguments. Cannot construct a `{ $valueType }` from `{ $coordinates }`.
 
 === 22N25
 
-Status description:: error: data exception - invalid temporal arguments. Cannot construct a { $valueType } from { $temporal }.
+Status description:: error: data exception - invalid temporal arguments. Cannot construct a `{ $valueType }` from `{ $temporal }`.
 
 === 22N26
 
@@ -211,7 +211,7 @@ Status description:: error: data exception - unsupported rounding mode. Unknown
 
 === 22N27
 
-Status description:: error: data exception - invalid entity type. Invalid input { $input } for { $variable }. Expected to be one of { $valueTypeList }.
+Status description:: error: data exception - invalid entity type. Invalid input `{ $input }` for `{ $variable }`. Expected to be one of `{ $valueTypeList }`.
 
 
 == Invalid transaction state
@@ -220,7 +220,7 @@ Invalid transaction state errors occur when the transaction is in an invalid sta
 
 === 25N01
 
-Status description:: error: invalid transaction state - invalid combination of statement types.Failed to execute the query { $query } due to conflicting statement types (read query, write query, schema modification, or administration command). To execute queries in the same transaction, they must be either of the same type, or be a combination of schema modifications and read commands.
+Status description:: error: invalid transaction state - invalid combination of statement types.Failed to execute the query `{ $query }` due to conflicting statement types (read query, write query, schema modification, or administration command). To execute queries in the same transaction, they must be either of the same type, or be a combination of schema modifications and read commands.
 
 === 25N02
 
@@ -233,7 +233,7 @@ Status description:: error: invalid transaction state - concurrent access violat
 === 25N04
 
 Status description:: error: invalid transaction state - specified transaction does not exist.
-Transaction { $transactionId } does not exist.
+Transaction `{ $transactionId }` does not exist.
 
 === 25N05
 
@@ -261,11 +261,11 @@ Status description:: error: invalid transaction state - conflicting transaction
 
 === 25N12
 
-Status description:: error: invalid transaction state - index was dropped. Index { $idx } was dropped in this transaction and cannot be used.
+Status description:: error: invalid transaction state - index was dropped. Index `{ $idx }` was dropped in this transaction and cannot be used.
 
 === 25N13
 
-Status description:: error: invalid transaction state - cannot access entity after removal. A { $entityType } was accessed after being deleted in this transaction. Verify the transaction statements.
+Status description:: error: invalid transaction state - cannot access entity after removal. A `{ $entityType }` was accessed after being deleted in this transaction. Verify the transaction statements.
 
 == Invalid transaction termination
 
@@ -399,7 +399,7 @@ Status description:: error: syntax error or access rule violation - invalid inpu
 
 === 42I18
 
-Status description:: error: syntax error or access rule violation - invalid reference to implicitly grouped expressions. The aggregation column contains implicit grouping expressions referenced by the variables `{ $variableList }`. Implicit grouping expressions are variables not explicitly declared as grouping keys.
+Status description:: error: syntax error or access rule violation - invalid reference to implicitly grouped expressions. The aggregation column contains implicit grouping expressions referenced by the variables `{ $varList }`. Implicit grouping expressions are variables not explicitly declared as grouping keys.
 
 
 === 42I20
@@ -408,28 +408,28 @@ Status description:: error: syntax error or access rule violation - invalid symb
 
 === 42I25
 
-Status description:: error: syntax error or access rule violation - invalid use of `CALL IN TRANSACTIONS`. 'CALL { ... } IN TRANSACTIONS' is not supported after a write clause.
+Status description:: error: syntax error or access rule violation - invalid use of CALL IN TRANSACTIONS. 'CALL { ... }` IN TRANSACTIONS' is not supported after a write clause.
 
 === 42I29
 
-Status description:: error: syntax error or access rule violation - invalid use of `IS`. The `IS` keyword cannot be used together with multiple labels in `{ $input }`. Rewrite the expression as `{ $replacement }`.
+Status description:: error: syntax error or access rule violation - invalid use of IS. The IS keyword cannot be used together with multiple labels in `{ $input }`. Rewrite the expression as `{ $replacement }`.
 
 === 42I31
 
-Status description:: error: syntax error or access rule violation - invalid use of `MATCH`. 'MATCH ...' cannot directly follow an 'OPTIONAL MATCH ...'. Use a WITH clause between them.
+Status description:: error: syntax error or access rule violation - invalid use of MATCH. MATCH ...' cannot directly follow an 'OPTIONAL MATCH ...'. Use a WITH clause between them.
 
 
 === 42I37
 
-Status description:: error: syntax error or access rule violation - invalid use of `RETURN *`. `'RETURN *'` is not allowed when there are no variables in scope.
+Status description:: error: syntax error or access rule violation - invalid use of `RETURN *`. `RETURN *'` is not allowed when there are no variables in scope.
 
 === 42I38
 
-Status description:: error: syntax error or access rule violation - invalid use of `RETURN`. `'RETURN ...'` can only be used at the end of a query or subquery.
+Status description:: error: syntax error or access rule violation - invalid use of `RETURN`. `RETURN ...'` can only be used at the end of a query or subquery.
 
 === 42I40
 
-Status description:: error: syntax error or access rule violation - invalid use of `UNION` and `UNION ALL`. `UNION` and `UNION ALL` cannot be combined.
+Status description:: error: syntax error or access rule violation - invalid use of `UNION and UNION ALL`. `UNION` and `UNION ALL` cannot be combined.
 
 === 42I47
 
@@ -437,7 +437,7 @@ Status description:: error: syntax error or access rule violation - parser error
 
 === 42I50
 
-Status description:: error: syntax error or access rule violation - token name too long. Invalid input { $input }... A { $tokenType } name cannot be longer than { $maxTokenLength }.
+Status description:: error: syntax error or access rule violation - token name too long. Invalid input `{ $input }`... A `{ $tokenType }` name cannot be longer than `{ $maxTokenLength }`.
 
 === 42N00
 
@@ -445,7 +445,7 @@ Status description:: error: syntax error or access rule violation - no such data
 
 === 42N01
 
-Status description:: error: syntax error or access rule violation - no such constituent graph exists in composite database. The constituent graph { $graph } was not found in the in composite database { $db }. Verify that the spelling is correct.
+Status description:: error: syntax error or access rule violation - no such constituent graph exists in composite database. The constituent graph `{ $graph }` was not found in the in composite database `{ $db }`. Verify that the spelling is correct.
 
 === 42N02
 
@@ -457,59 +457,59 @@ Status description:: error: syntax error or access rule violation - writing to m
 
 === 42N04
 
-Status description:: error: syntax error or access rule violation - unsupported access of composite database. Failed to access database identified by { $db1 } while connected to session database { $db2 }. Connect to { $db3 } directly.
+Status description:: error: syntax error or access rule violation - unsupported access of composite database. Failed to access database identified by `{ $db1 }` while connected to session database `{ $db2 }`. Connect to `{ $db3 }` directly.
 
 === 42N05
 
-Status description:: error: syntax error or access rule violation - unsupported access of standard database. Failed to access database identified by { $db1 } while connected to composite session database { $db2 }. Connect to { $db3 } directly or create an alias in the composite database.
+Status description:: error: syntax error or access rule violation - unsupported access of standard database. Failed to access database identified by `{ $db1 }` while connected to composite session database `{ $db2 }`. Connect to `{ $db3 }` directly or create an alias in the composite database.
 
 === 42N06
 
-Status description:: error: syntax error or access rule violation - unsupported action on composite database. { $action } is not supported on composite databases.
+Status description:: error: syntax error or access rule violation - unsupported action on composite database. `{ $action }` is not supported on composite databases.
 
 === 42N07
 
-Status description:: error: syntax error or access rule violation - variable shadowing. The variable { $variable } is shadowing a variable with the same name from the outer scope and needs to be renamed.
+Status description:: error: syntax error or access rule violation - variable shadowing. The variable `{ $variable }` is shadowing a variable with the same name from the outer scope and needs to be renamed.
 
 === 42N08
 
-Status description:: error: syntax error or access rule violation - no such procedure or function. The procedure or function { $procFun } was not registered for this database instance. Verify that the spelling is correct.
+Status description:: error: syntax error or access rule violation - no such procedure or function. The procedure or function `{ $procFun }` was not registered for this database instance. Verify that the spelling is correct.
 
 === 42N09
 
-Status description:: error: syntax error or access rule violation - no such user. A user with the name { $user } was not found. Verify that the spelling is correct.
+Status description:: error: syntax error or access rule violation - no such user. A user with the name `{ $user }` was not found. Verify that the spelling is correct.
 
 === 42N10
 
-Status description:: error: syntax error or access rule violation - no such role. A role with the name { $role } was not found. Verify that the spelling is correct.
+Status description:: error: syntax error or access rule violation - no such role. A role with the name `{ $role }` was not found. Verify that the spelling is correct.
 
 === 42N11
 
-Status description:: error: syntax error or access rule violation - database or alias already exists. A [composite] database or alias with the name { $db } already exists.
+Status description:: error: syntax error or access rule violation - database or alias already exists. A [composite] database or alias with the name `{ $db }` already exists.
 
 === 42N12
 
-Status description:: error: syntax error or access rule violation - user already exists. A user with the name { $user } already exists.
+Status description:: error: syntax error or access rule violation - user already exists. A user with the name `{ $user }` already exists.
 
 === 42N13
 
-Status description:: error: syntax error or access rule violation - role already exists. A role with the name { $role } already exists.
+Status description:: error: syntax error or access rule violation - role already exists. A role with the name `{ $role }` already exists.
 
 === 42N14
 
-Status description:: error: syntax error or access rule violation - invalid use of command. { $clause } cannot be used together with { $cmd }.
+Status description:: error: syntax error or access rule violation - invalid use of command. `{ $clause }` cannot be used together with `{ $cmd }`.
 
 === 42N15
 
-Status description:: error: syntax error or access rule violation - invalid use of reserved keyword. { $syntax } is a reserved keyword and cannot be used in this place.
+Status description:: error: syntax error or access rule violation - invalid use of reserved keyword. `{ $syntax }` is a reserved keyword and cannot be used in this place.
 
 === 42N16
 
-Status description:: error: syntax error or access rule violation - unsupported index or constraint. Only single property { $idxType } are supported.
+Status description:: error: syntax error or access rule violation - unsupported index or constraint. Only single property `{ $idxType }` are supported.
 
 === 42N17
 
-Status description:: error: syntax error or access rule violation - unsupported request. { $input } is not allowed on the system database.
+Status description:: error: syntax error or access rule violation - unsupported request. `{ $input }` is not allowed on the system database.
 
 === 42N19
 
@@ -527,11 +527,11 @@ Status description:: error: syntax error or access rule violation - unaliased re
 
 === 42N22
 
-Status description:: error: syntax error or access rule violation - single return column required. A `COLLECT` subquery must end with a single return column.
+Status description:: error: syntax error or access rule violation - single return column required. A COLLECT subquery must end with a single return column.
 
 === 42N29
 
-Status description:: error: syntax error or access rule violation - unbound variables in pattern expression. Pattern expressions are not allowed to introduce new variables: `{ $variable }`.
+Status description:: error: syntax error or access rule violation - unbound variables in pattern expression. Pattern expressions are not allowed to introduce new variables: `{ $var }`.
 
 === 42N39
 
@@ -543,7 +543,7 @@ Status description:: error: syntax error or access rule violation - unexpected e
 
 === 42N49
 
-Status description:: error: syntax error or access rule violation - unsupported normal form. Unknown Normal Form: { $input }.
+Status description:: error: syntax error or access rule violation - unsupported normal form. Unknown Normal Form: `{ $input }`.
 
 === 42N57
 
@@ -555,15 +555,15 @@ Status description:: error: syntax error or access rule violation - function wit
 
 === 42N75
 
-Status description:: error: syntax error or access rule violation - invalid use of graph function. A call to the graph function { $fun } is only allowed as the top-level argument of a USE clause.
+Status description:: error: syntax error or access rule violation - invalid use of graph function. A call to the graph function `{ $fun }` is only allowed as the top-level argument of a USE clause.
 
 === 42N76
 
-Status description:: error: syntax error or access rule violation - unfulfillable hints. The hint(s) `{ $hintList }` cannot be fulfilled.
+Status description:: error: syntax error or access rule violation - unfulfillable hints. The hint(s) `{ $hintAndedList }` cannot be fulfilled.
 
 === 42N78
 
-Status description:: error: syntax error or access rule violation - variable already bound. Node `{ $variable }` has already been bound and cannot be modified by the `{ $clause }` clause.
+Status description:: error: syntax error or access rule violation - variable already bound. Node `{ $var }` has already been bound and cannot be modified by the `{ $clause }` clause.
 
 
 === 42N83
@@ -588,11 +588,11 @@ Status description:: error: syntax error or access rule violation - cannot grant
 
 === 42N89
 
-Status description:: error: syntax error or access rule violation - invalid driver settings map. Failed evaluating the given driver settings. { $cause }
+Status description:: error: syntax error or access rule violation - invalid driver settings map. Failed evaluating the given driver settings. `{ $cause }
 
 === 42N90
 
-Status description:: error: syntax error or access rule violation - cannot alter immutable composite database. Composite databases cannot be altered (database: { $db }).
+Status description:: error: syntax error or access rule violation - cannot alter immutable composite database. Composite databases cannot be altered (database: `{ $db }).
 
 === 42N97
 

From 103bf99de8226d448ee620409638acaaa8c929ba Mon Sep 17 00:00:00 2001
From: Reneta Popova <reneta.popova@neo4j.com>
Date: Thu, 24 Oct 2024 14:56:55 +0100
Subject: [PATCH 15/18] add missing backticks

---
 modules/ROOT/pages/errors/gql-errors.adoc | 36 +++++++++++------------
 1 file changed, 18 insertions(+), 18 deletions(-)

diff --git a/modules/ROOT/pages/errors/gql-errors.adoc b/modules/ROOT/pages/errors/gql-errors.adoc
index 307e8a62..560d891a 100644
--- a/modules/ROOT/pages/errors/gql-errors.adoc
+++ b/modules/ROOT/pages/errors/gql-errors.adoc
@@ -183,7 +183,7 @@ Status description:: error: data exception - invalid spatial value. A POINT must
 
 === 22N20
 
-Status description:: error: data exception - invalid spatial value dimensions. Cannot create POINT with `{ $dim1 }D coordinate reference system (CRS) and `{ $value }` coordinates. Use the equivalent `{ $dim2 }D coordinate reference system instead.
+Status description:: error: data exception - invalid spatial value dimensions. Cannot create POINT with `{ $dim1 }D` coordinate reference system (CRS) and `{ $value }` coordinates. Use the equivalent `{ $dim2 }D` coordinate reference system instead.
 
 === 22N21
 
@@ -387,7 +387,7 @@ Status description:: error: syntax error or access rule violation - invalid case
 
 === 42I01
 
-Status description:: error: syntax error or access rule violation - invalid FOREACH. Invalid use of `{ $clause }` inside 'FOREACH'.
+Status description:: error: syntax error or access rule violation - invalid `FOREACH`. Invalid use of `{ $clause }` inside 'FOREACH'.
 
 === 42I02
 
@@ -408,28 +408,28 @@ Status description:: error: syntax error or access rule violation - invalid symb
 
 === 42I25
 
-Status description:: error: syntax error or access rule violation - invalid use of CALL IN TRANSACTIONS. 'CALL { ... }` IN TRANSACTIONS' is not supported after a write clause.
+Status description:: error: syntax error or access rule violation - invalid use of `CALL IN TRANSACTIONS`. 'CALL { ... } IN TRANSACTIONS' is not supported after a write clause.
 
 === 42I29
 
-Status description:: error: syntax error or access rule violation - invalid use of IS. The IS keyword cannot be used together with multiple labels in `{ $input }`. Rewrite the expression as `{ $replacement }`.
+Status description:: error: syntax error or access rule violation - invalid use of `IS`. The `IS` keyword cannot be used together with multiple labels in `{ $input }`. Rewrite the expression as `{ $replacement }`.
 
 === 42I31
 
-Status description:: error: syntax error or access rule violation - invalid use of MATCH. MATCH ...' cannot directly follow an 'OPTIONAL MATCH ...'. Use a WITH clause between them.
+Status description:: error: syntax error or access rule violation - invalid use of `MATCH`. 'MATCH ...' cannot directly follow an 'OPTIONAL MATCH ...'. Use a `WITH` clause between them.
 
 
 === 42I37
 
-Status description:: error: syntax error or access rule violation - invalid use of `RETURN *`. `RETURN *'` is not allowed when there are no variables in scope.
+Status description:: error: syntax error or access rule violation - invalid use of `RETURN *`. 'RETURN *' is not allowed when there are no variables in scope.
 
 === 42I38
 
-Status description:: error: syntax error or access rule violation - invalid use of `RETURN`. `RETURN ...'` can only be used at the end of a query or subquery.
+Status description:: error: syntax error or access rule violation - invalid use of `RETURN`. 'RETURN ...' can only be used at the end of a query or subquery.
 
 === 42I40
 
-Status description:: error: syntax error or access rule violation - invalid use of `UNION and UNION ALL`. `UNION` and `UNION ALL` cannot be combined.
+Status description:: error: syntax error or access rule violation - invalid use of `UNION` and `UNION ALL`. `UNION` and `UNION ALL` cannot be combined.
 
 === 42I47
 
@@ -437,7 +437,7 @@ Status description:: error: syntax error or access rule violation - parser error
 
 === 42I50
 
-Status description:: error: syntax error or access rule violation - token name too long. Invalid input `{ $input }`... A `{ $tokenType }` name cannot be longer than `{ $maxTokenLength }`.
+Status description:: error: syntax error or access rule violation - token name too long. Invalid input `{ $input }..`. A `{ $tokenType }` name cannot be longer than `{ $maxTokenLength }`.
 
 === 42N00
 
@@ -453,7 +453,7 @@ Status description:: error: syntax error or access rule violation - writing in r
 
 === 42N03
 
-Status description:: error: syntax error or access rule violation - writing to multiple graphs. Writing to multiple graphs in the same transaction is not allowed. Use CALL IN TRANSACTION or create separate transactions in your application.
+Status description:: error: syntax error or access rule violation - writing to multiple graphs. Writing to multiple graphs in the same transaction is not allowed. Use `CALL IN TRANSACTION` or create separate transactions in your application.
 
 === 42N04
 
@@ -485,7 +485,7 @@ Status description:: error: syntax error or access rule violation - no such role
 
 === 42N11
 
-Status description:: error: syntax error or access rule violation - database or alias already exists. A [composite] database or alias with the name `{ $db }` already exists.
+Status description:: error: syntax error or access rule violation - database or alias already exists. A `[composite]` database or alias with the name `{ $db }` already exists.
 
 === 42N12
 
@@ -517,7 +517,7 @@ Status description:: error: syntax error or access rule violation - duplicate cl
 
 === 42N20
 
-Status description:: error: syntax error or access rule violation - empty list range operator. The list range operator `'[ ]'` cannot be empty.
+Status description:: error: syntax error or access rule violation - empty list range operator. The list range operator '[ ]' cannot be empty.
 
 
 === 42N21
@@ -527,7 +527,7 @@ Status description:: error: syntax error or access rule violation - unaliased re
 
 === 42N22
 
-Status description:: error: syntax error or access rule violation - single return column required. A COLLECT subquery must end with a single return column.
+Status description:: error: syntax error or access rule violation - single return column required. A `COLLECT` subquery must end with a single return column.
 
 === 42N29
 
@@ -535,7 +535,7 @@ Status description:: error: syntax error or access rule violation - unbound vari
 
 === 42N39
 
-Status description:: error: syntax error or access rule violation - incompatible return columns. All subqueries in a UNION clause must have the same return column names.
+Status description:: error: syntax error or access rule violation - incompatible return columns. All subqueries in a `UNION` clause must have the same return column names.
 
 === 42N45
 
@@ -555,7 +555,7 @@ Status description:: error: syntax error or access rule violation - function wit
 
 === 42N75
 
-Status description:: error: syntax error or access rule violation - invalid use of graph function. A call to the graph function `{ $fun }` is only allowed as the top-level argument of a USE clause.
+Status description:: error: syntax error or access rule violation - invalid use of graph function. A call to the graph function `{ $fun }` is only allowed as the top-level argument of a `USE` clause.
 
 === 42N76
 
@@ -572,7 +572,7 @@ Status description:: error: syntax error or access rule violation - impersonatio
 
 === 42N84
 
-Status description:: error: syntax error or access rule violation - TERMINATE TRANSACTION misses YIELD clause. WHERE clause without YIELD clause. Use 'TERMINATE TRANSACTION ... YIELD ... WHERE ...'.
+Status description:: error: syntax error or access rule violation - `TERMINATE TRANSACTION` misses `YIELD` clause. `WHERE` clause without `YIELD` clause. Use 'TERMINATE TRANSACTION ... YIELD ... WHERE ...'.
 
 === 42N85
 
@@ -588,11 +588,11 @@ Status description:: error: syntax error or access rule violation - cannot grant
 
 === 42N89
 
-Status description:: error: syntax error or access rule violation - invalid driver settings map. Failed evaluating the given driver settings. `{ $cause }
+Status description:: error: syntax error or access rule violation - invalid driver settings map. Failed evaluating the given driver settings. { $cause }
 
 === 42N90
 
-Status description:: error: syntax error or access rule violation - cannot alter immutable composite database. Composite databases cannot be altered (database: `{ $db }).
+Status description:: error: syntax error or access rule violation - cannot alter immutable composite database. Composite databases cannot be altered (database: `{ $db }`).
 
 === 42N97
 

From dff364f150c7224b2dff6d0332deece23e693a4c Mon Sep 17 00:00:00 2001
From: Reneta Popova <reneta.popova@neo4j.com>
Date: Thu, 24 Oct 2024 15:10:59 +0100
Subject: [PATCH 16/18] more missing backticks

---
 modules/ROOT/pages/errors/gql-errors.adoc | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/modules/ROOT/pages/errors/gql-errors.adoc b/modules/ROOT/pages/errors/gql-errors.adoc
index 560d891a..13375e01 100644
--- a/modules/ROOT/pages/errors/gql-errors.adoc
+++ b/modules/ROOT/pages/errors/gql-errors.adoc
@@ -175,15 +175,15 @@ Status description:: error: data exception - invalid import value. Importing ent
 
 === 22N18
 
-Status description:: error: data exception - incomplete spatial value. A `{ $crs }` POINT must contain `{ $mapKeyList }`.
+Status description:: error: data exception - incomplete spatial value. A `{ $crs }` `POINT` must contain `{ $mapKeyList }`.
 
 === 22N19
 
-Status description:: error: data exception - invalid spatial value. A POINT must contain either 'x' and 'y', or 'latitude' and 'longitude'.
+Status description:: error: data exception - invalid spatial value. A `POINT` must contain either 'x' and 'y', or 'latitude' and 'longitude'.
 
 === 22N20
 
-Status description:: error: data exception - invalid spatial value dimensions. Cannot create POINT with `{ $dim1 }D` coordinate reference system (CRS) and `{ $value }` coordinates. Use the equivalent `{ $dim2 }D` coordinate reference system instead.
+Status description:: error: data exception - invalid spatial value dimensions. Cannot create `POINT` with `{ $dim1 }D` coordinate reference system (CRS) and `{ $value }` coordinates. Use the equivalent `{ $dim2 }D` coordinate reference system instead.
 
 === 22N21
 
@@ -195,7 +195,7 @@ Status description:: error: data exception - invalid spatial value combination.
 
 === 22N23
 
-Status description:: error: data exception - invalid latitude value. Cannot create WGS84 POINT with invalid coordinate: `{ $coordinates }`. The valid range for the latitude coordinate is [-90, 90].
+Status description:: error: data exception - invalid latitude value. Cannot create WGS84 `POINT` with invalid coordinate: `{ $coordinates }`. The valid range for the latitude coordinate is `[-90, 90]`.
 
 === 22N24
 
@@ -207,7 +207,7 @@ Status description:: error: data exception - invalid temporal arguments. Cannot
 
 === 22N26
 
-Status description:: error: data exception - unsupported rounding mode. Unknown rounding mode. Valid values are: CEILING, FLOOR, UP, DOWN, HALF_EVEN, HALF_UP, HALF_DOWN, UNNECESSARY.
+Status description:: error: data exception - unsupported rounding mode. Unknown rounding mode. Valid values are: `CEILING`, `FLOOR`, `UP`, `DOWN`, `HALF_EVEN`, `HALF_UP`, `HALF_DOWN`, `UNNECESSARY`.
 
 === 22N27
 

From 50b9757e0bb2dd2e79976e66a53cd60254070947 Mon Sep 17 00:00:00 2001
From: Reneta Popova <reneta.popova@neo4j.com>
Date: Fri, 25 Oct 2024 12:34:03 +0100
Subject: [PATCH 17/18] Update modules/ROOT/pages/errors/gql-errors.adoc

---
 modules/ROOT/pages/errors/gql-errors.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/modules/ROOT/pages/errors/gql-errors.adoc b/modules/ROOT/pages/errors/gql-errors.adoc
index 13375e01..3c6566cd 100644
--- a/modules/ROOT/pages/errors/gql-errors.adoc
+++ b/modules/ROOT/pages/errors/gql-errors.adoc
@@ -395,7 +395,7 @@ Status description:: error: syntax error or access rule violation - invalid comm
 
 === 42I06
 
-Status description:: error: syntax error or access rule violation - invalid input. Invalid input `{ $input1 }`, expected: `{ $input2 }`.
+Status description:: error: syntax error or access rule violation - invalid input. Invalid input `{ $input }`, expected: `{ $valueList }`.
 
 === 42I18
 

From fe886b1c30722c946a17a4dca734860dbfb34df4 Mon Sep 17 00:00:00 2001
From: Reneta Popova <reneta.popova@neo4j.com>
Date: Fri, 25 Oct 2024 12:56:50 +0100
Subject: [PATCH 18/18] escape the bold formatting and remove the backticks

---
 modules/ROOT/pages/errors/gql-errors.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/modules/ROOT/pages/errors/gql-errors.adoc b/modules/ROOT/pages/errors/gql-errors.adoc
index 3c6566cd..d0adc0c3 100644
--- a/modules/ROOT/pages/errors/gql-errors.adoc
+++ b/modules/ROOT/pages/errors/gql-errors.adoc
@@ -391,7 +391,7 @@ Status description:: error: syntax error or access rule violation - invalid `FOR
 
 === 42I02
 
-Status description:: error: syntax error or access rule violation - invalid comment. Failed to parse comment. A comment starting with `'/*'` must also have a closing `'*/'`.
+Status description:: error: syntax error or access rule violation - invalid comment. Failed to parse comment. A comment starting with '/\*' must also have a closing '*/'.
 
 === 42I06