Fix a heading mistake and the index generation message (neo4j#314)

Author: renetapopova

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

@@ -1,4 +1,4 @@
-// This is an automatically generated file. Do not edit it directly. It is generated from the templates/gql-index-template.adoc file and should be edited there.
+// THIS IS AN AUTOMATICALLY GENERATED FILE. DO NOT EDIT IT. THE STRUCTURE IS GENERATED FROM templates/gql-index-template.adoc AND THE CODES ARE POPULATED BY THE SCRIPTS LOCATED IN THE scripts/ FOLDER.
 
 
 :description: This section describes the GQLSTATUS errors that Neo4j can return, grouped by category, and an example of when they can occur.
@@ -107,7 +107,7 @@ Status description:: error: connection exception - general driver database error
 [[data-exceptions]]
 == Data exceptions
 
-Database exceptions occur when a client request contains the wrong format, types, or other unsupported input.
+Data exceptions occur when a client request contains the wrong format, types, or other unsupported input.
 Some examples are data and constraint creation, which conflicts with existing constraints, properties of non-storable type, and spatial and temporal values with invalid components.
 
 === xref:errors/gql-errors/22000.adoc[22000]
@@ -465,9 +465,10 @@ Status description:: error: data exception - not a valid CIDR IP. `{ <<input>> }
 
 Status description:: error: data exception - new password cannot be the same as the old password. Expected the new password to be different from the old password.
 
+[role=label--changed-2025.05]
 === xref:errors/gql-errors/22N90.adoc[22N90]
 
-Status description:: error: data exception - property type unsupported in constraint. `{ <<item>> }` is not supported in property type constraints.
+Status description:: error: data exception - property type unsupported in constraint. `{ <<valueType>> }` is not supported in property type constraints.
 
 === xref:errors/gql-errors/22N91.adoc[22N91]
 
@@ -579,7 +580,7 @@ Status description:: error: data exception - invalid Neo4j type. `{ <<input>> }`
 
 === xref:errors/gql-errors/22NB9.adoc[22NB9]
 
-Status description:: error: data exception - invalid inner list type. Lists cannot have `{ <<item>> }` as an inner type in this context.
+Status description:: error: data exception - invalid inner list type. Lists cannot have `{ <<typeDescription>> }` as an inner type in this context.
 
 
 [[invalid-transaction-state]]

modules/ROOT/templates/gql-index-template.adoc

@@ -24,7 +24,7 @@ Connection exceptions occur when the client (e.g. Browser/Bloom/Cypher Shell) is
 [[data-exceptions]]
 == Data exceptions
 
-Database exceptions occur when a client request contains the wrong format, types, or other unsupported input.
+Data exceptions occur when a client request contains the wrong format, types, or other unsupported input.
 Some examples are data and constraint creation, which conflicts with existing constraints, properties of non-storable type, and spatial and temporal values with invalid components.
 
 {codes_starting_with:'22'}

scripts/generate-gql-error-index-from-template.py

@@ -140,7 +140,7 @@ def generate_from_template(template_file, errors_dir, output_file, include_descr
 
     # Write the result to the output file
     with open(output_file, 'w') as f:
-        f.write("// This is an automatically generated file. Do not edit it directly. It is generated from the templates/gql-index-template.adoc file and should be edited there.\n")
+        f.write("// THIS IS AN AUTOMATICALLY GENERATED FILE. DO NOT EDIT IT. THE STRUCTURE IS GENERATED FROM templates/gql-index-template.adoc AND THE CODES ARE POPULATED BY THE SCRIPTS LOCATED IN THE scripts/ FOLDER.\n")
         f.write(template_content)
 
     print(f'Generated index file at: {output_file}')