update the format of the GQLSTATUS codes

Author: renetapopova

modules/ROOT/pages/database-administration/aliases/manage-aliases-composite-databases.adoc

@@ -118,10 +118,10 @@ CREATE ALIAS yard FOR DATABASE garden
 [source, output, role="noheader"]
 ----
 Failed to create the specified database alias 'yard': Database 'garden' is composite.
-
-42NA6, error: syntax error or access rule violation - invalid alias target. Aliases are not allowed to target composite databases.
 ----
 
+From 5.26 onwards, the error message also contains the GQLSTATUS code `42NA6` and the status description `error: syntax error or access rule violation - invalid alias target. Aliases are not allowed to target composite databases.`
+
 == Alter local and remote database aliases in composite databases
 
 Local and remote database aliases belonging to a composite database can be altered using the `ALTER ALIAS` command.
@@ -355,8 +355,8 @@ DROP ALIAS $aliasname FOR DATABASE
 ----
 Failed to delete the specified database alias 'foo.bar': Database alias does not exist.
 ----
-//"GQLSTATUS": "50N00",
-//     "statusDescription": "error: general processing exception - internal error. Internal exception raised { $msgTitle }: Failed to create the specified database alias 'foo.bar'. Database alias does not exist."
+
+//From 5.26 onwards, the error message also contains the GQLSTATUS code `50N00` and the status description `error: general processing exception - internal error. Internal exception raised { $msgTitle }: Failed to create the specified database alias 'foo.bar'. Database alias does not exist.`
 
 Had the composite database `foo` not existed, the database alias `foo.bar` would have been dropped.
 

modules/ROOT/pages/database-internals/concurrent-data-access.adoc

@@ -295,12 +295,7 @@ Since locks are used, deadlocks can happen.
 A deadlock occurs when two transactions are blocked by each other because they are attempting to concurrently modify a node or a relationship that is locked by the other transaction.
 In such a scenario, neither of the transactions will be able to proceed.
 When Neo4j detects a deadlock, the transaction is terminated with the transient error message code `Neo.TransientError.Transaction.DeadlockDetected`.
-From 5.25 onwards, the error also contains the following additional GQLSTATUS code and information along with the Neo4j exception:
-[soruce, json, role="noheader"]
-----
-"GQLSTATUS": "50N05",
-     "statusDescription": "error: general processing exception - deadlock detected. Deadlock detected while trying to acquire locks. See log for more details."
-----
+From 5.25 onwards, the error message also contains the GQLSTATUS code `50N05` and the status description `error: general processing exception - deadlock detected. Deadlock detected while trying to acquire locks. See log for more details.` along with the Neo4j exception.
 
 All locks acquired by the transaction are still held but will be released when the transaction finishes.
 Once the locks are released, other transactions that were waiting for locks held by the transaction causing the deadlock can proceed.