GQL framework

modules/ROOT/content-nav.adoc

@@ -1,7 +1,7 @@
 * xref:index.adoc[]
 * xref:errors/index.adoc[]
-** xref:errors/all-errors.adoc[]
 ** xref:errors/gql-errors.adoc[]
+** xref:errors/all-errors.adoc[]
 * xref:notifications/index.adoc[]
 ** xref:notifications/all-notifications.adoc[]
 * xref:changelogs.adoc[]

modules/ROOT/pages/errors/all-errors.adoc

@@ -1,8 +1,28 @@
-:description: The Neo4j error codes for Neo4j version {neo4j-version}.
+:description: The legacy error codes for Neo4j 5.
 
 
 [[neo4j-errors]]
-= List of all server error codes
+= List of legacy server error codes
+
+This page lists the legacy server error codes, also known as Neo4j status codes.
+These will be replaced by xref:errors/gql-errors.adoc[GQLSTATUS server error codes].
+
+Error codes are returned by the server when the execution of a query fails.
+They always have the severity level `ERROR`.
+Errors are grouped based on the type of the Neo4j status code:
+
+Client errors::
+These errors are caused by the client and are usually related to the request itself.
+The Neo4j status codes for client errors have the prefix `Neo.ClientError`.
+
+Transient errors::
+These errors are detected by the server and are usually related to some kind of database unavailability, such as limits reached, out-of-memory, timeouts, etc.
+The error can be temporary, and the request could succeed if retried.
+The Neo4j status codes for transient errors have the prefix Neo.`TransientError`.
+
+Database errors::
+These errors are caused by the database and are usually related to the database state.
+The Neo4j status codes for database errors have the prefix `Neo.DatabaseError`.
 
 This page contains lists of all Neo4j errors, grouped by type.
 
@@ -13,7 +33,7 @@ This is a complete list of all client errors Neo4j may return, and what they mea
 [options="header", cols="<1m,<1"]
 |===
 
-| Neo4j status code
+| Neo4j legacy code
 | Description
 
 | Neo.ClientError.ChangeDataCapture.InvalidIdentifier
@@ -279,7 +299,7 @@ This is a complete list of all transient errors Neo4j may return, and what they
 [options="header", cols="<1m,<1"]
 |===
 
-| Neo4j status code
+| Neo4j legacy code
 | Description
 
 | Neo.TransientError.ChangeDataCapture.FutureIdentifier
@@ -386,7 +406,7 @@ This is a complete list of all database errors Neo4j may return, and what they m
 [options="header", cols="<1m,<1"]
 |===
 
-| Neo4j status code
+| Neo4j legacy code
 | Description
 
 | Neo.DatabaseError.ChangeDataCapture.Disabled

modules/ROOT/pages/errors/gql-errors.adoc

@@ -1,15 +1,15 @@
 :description: This section describes the GQLSTATUS errors that Neo4j can return, grouped by category, and an example of when they can occur.
 
 [[neo4j-gqlstatus-errors]]
-= List of all GQLSTATUS server error codes
+= List of GQLSTATUS server error codes
 
 //The following page provides an overview of all server errors in Neo4j, along with some scenarios and their possible solutions.
 The following page provides an overview of all GQLSTATUS server error codes in Neo4j.
 All errors in Neo4j have severity level `ERROR`.
 
 == Connection exceptions
 
-Connection exceptions occur when the client is unable to connect to the server for various reasons such as network issues, server-side routing being disabled, or the database being unavailable, etc.
+Connection exceptions occur when the client (e.g. Browser/Bloom/Cypher Shell) is unable to connect to the server for various reasons such as network issues, server-side routing being disabled, or the database being unavailable, etc.
 
 === 08000