diff --git a/modules/ROOT/content-nav.adoc b/modules/ROOT/content-nav.adoc
index 62efe6d8..5f75c4b6 100644
--- a/modules/ROOT/content-nav.adoc
+++ b/modules/ROOT/content-nav.adoc
@@ -159,6 +159,21 @@
 **** xref:errors/gql-errors/22NBD.adoc[]
 **** xref:errors/gql-errors/22NBE.adoc[]
 **** xref:errors/gql-errors/22NBF.adoc[]
+**** xref:errors/gql-errors/22NC1.adoc[]
+**** xref:errors/gql-errors/22NC2.adoc[]
+**** xref:errors/gql-errors/22NC3.adoc[]
+**** xref:errors/gql-errors/22NC4.adoc[]
+**** xref:errors/gql-errors/22NC5.adoc[]
+**** xref:errors/gql-errors/22NC6.adoc[]
+**** xref:errors/gql-errors/22NC7.adoc[]
+**** xref:errors/gql-errors/22NC8.adoc[]
+**** xref:errors/gql-errors/22NC9.adoc[]
+**** xref:errors/gql-errors/22NCA.adoc[]
+**** xref:errors/gql-errors/22NCB.adoc[]
+**** xref:errors/gql-errors/22NCC.adoc[]
+**** xref:errors/gql-errors/22NCD.adoc[]
+**** xref:errors/gql-errors/22NCE.adoc[]
+**** xref:errors/gql-errors/22NCF.adoc[]
 *** xref:errors/gql-errors/index.adoc#invalid-transaction-state[Invalid transaction state]
 **** xref:errors/gql-errors/25G02.adoc[]
 **** xref:errors/gql-errors/25N01.adoc[]
diff --git a/modules/ROOT/pages/errors/gql-errors/22NC1.adoc b/modules/ROOT/pages/errors/gql-errors/22NC1.adoc
new file mode 100644
index 00000000..8549fb3a
--- /dev/null
+++ b/modules/ROOT/pages/errors/gql-errors/22NC1.adoc
@@ -0,0 +1,41 @@
+:page-role: new-2025.x cypher-25
+= 22NC1
+
+== Status description
+error: data exception - graph type element contains duplicated tokens. The graph type element includes a property key with name `{ <<propKey>> }` more than once.
+
+== Explanation
+When defining a graph type, node and relationship element types may only define a property once.
+
+== Example scenario
+For example, try to set a graph type as follows:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+    (n:Node => {prop::STRING, prop::INTEGER})
+}
+----
+
+The query returns an error with GQLSTATUS 22NC1 and the status description:
+
+[source]
+----
+error: data exception - graph type element contains duplicated tokens. The graph type element includes a property key with name `prop` more than once.
+----
+
+To fix this, remove the duplicate property key definition or uniquely name the property keys:
+
+[source, cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+    (p:Node => {prop :: STRING, prop2 :: INTEGER})
+}
+----
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]
\ No newline at end of file
diff --git a/modules/ROOT/pages/errors/gql-errors/22NC2.adoc b/modules/ROOT/pages/errors/gql-errors/22NC2.adoc
new file mode 100644
index 00000000..ca3e341c
--- /dev/null
+++ b/modules/ROOT/pages/errors/gql-errors/22NC2.adoc
@@ -0,0 +1,41 @@
+:page-role: new-2025.x cypher-25
+= 22NC2
+
+== Status description
+error: data exception - node element type has no effect. The node element type `{ <<label>> }` must contain one or more implied labels, or at least one property type.
+
+== Explanation
+When defining a graph type, node element types must have some effect; otherwise, they are not allowed.
+
+== Example scenario
+For example, try to set a graph type as follows:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+    (n:Node => )
+}
+----
+
+The query returns an error with GQLSTATUS 22NC2 and the status description:
+
+[source]
+----
+error: data exception - node element type is has no effect. The node element type `Node` must contain one or more implied labels, or at least one property type.
+----
+
+To fix this, define at least one property type or add an implied label, for example:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+    (n:Node => { prop :: ANY NOT NULL })
+}
+----
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]
diff --git a/modules/ROOT/pages/errors/gql-errors/22NC3.adoc b/modules/ROOT/pages/errors/gql-errors/22NC3.adoc
new file mode 100644
index 00000000..24cb92f3
--- /dev/null
+++ b/modules/ROOT/pages/errors/gql-errors/22NC3.adoc
@@ -0,0 +1,46 @@
+:page-role: new-2025.x cypher-25
+= 22NC3
+
+== Status description
+error: data exception - relationship element type has no effect. The relationship element type `{ <<relType>> }` must define a source, destination, or at least one property type.
+
+== Explanation
+When defining a graph type, relationship element types must have some effect.
+To be effective, a relationship element type must define at least one of the following:
+
+* a source node element type or label
+* a destination node element type or label
+* at least one property type
+
+== Example scenario
+For example, try to set a graph type as follows:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+    ()-[:REL =>]->()
+}
+----
+
+The query returns an error with GQLSTATUS 22NC3 and the status description:
+
+[source]
+----
+error: data exception - relationship element type has no effect. The relationship element type `REL` must define a source or destination, or at least one property type.
+----
+
+To fix this, define at least one property type or add a node element type, for example:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+    ()-[:REL => {prop: ANY NOT NULL }]->()
+}
+----
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]
diff --git a/modules/ROOT/pages/errors/gql-errors/22NC4.adoc b/modules/ROOT/pages/errors/gql-errors/22NC4.adoc
new file mode 100644
index 00000000..8caa2c42
--- /dev/null
+++ b/modules/ROOT/pages/errors/gql-errors/22NC4.adoc
@@ -0,0 +1,46 @@
+:page-role: new-2025.x cypher-25
+= 22NC4
+
+== Status description
+error: data exception - a label cannot be both identifying and implied. The label(s) `{ <<labelList>> }` are defined as both identifying and implied.
+
+== Explanation
+When defining a graph type, labels and relationships must be assigned clear roles.
+A label cannot be both "identifying" (to uniquely identify nodes) and "implied" (automatically assigned based on other schema rules) at the same time.
+Attempting to define a label as both will result in this error, as it creates ambiguity in the schema definition and node identification process.
+
+== Example scenario
+For example, try to set a graph type which defines the node element types `Person` and `Student` with the label `Person` also declared as an implied label on the `Student` node element type as follows:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+    (p:Person => {name :: STRING}),
+    (s:Student => :Person )
+}
+----
+
+The query returns an error with GQLSTATUS 22NC4 and the status description:
+
+[source]
+----
+error: data exception - a label cannot be both identifying and implied. The label(s) `Person` are defined as both identifying and implied.
+----
+
+One way to fix this is to add another label to both nodes and capture the property type on `name` there:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+    (p:Person => :Named),
+    (s:Student => :Named),
+    CONSTRAINT FOR (:Named) REQUIRE name IS :: STRING
+}
+----
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]
diff --git a/modules/ROOT/pages/errors/gql-errors/22NC5.adoc b/modules/ROOT/pages/errors/gql-errors/22NC5.adoc
new file mode 100644
index 00000000..82884136
--- /dev/null
+++ b/modules/ROOT/pages/errors/gql-errors/22NC5.adoc
@@ -0,0 +1,95 @@
+:page-role: new-2025.x cypher-25
+= 22NC5
+
+== Status description
+error: data exception - graph type element not found. The `{ <<entityType>> }` element type referenced by `{ <<graphTypeReference>> }` does not exist.
+
+== Explanation
+This error occurs when a graph type definition references an element type (such as a node or relationship) using an alias that has not been defined, or by an identifying reference where there is no graph type element identified by that reference.
+If the referenced node or relationship type does not exist, the operation cannot proceed and will return an error to indicate the missing element.
+
+== Example scenarios
+
+=== Node element reference does not exist
+For example, try to set a graph type with an identifying node element reference that does not exist as follows:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+  (:Node =>)-[e:REL => { prop :: STRING }]->()
+}
+----
+
+The query returns an error with GQLSTATUS 22NC5 and the status description:
+
+[source]
+----
+error: data exception - graph type element not found. The node type element referenced by '(:Node =>)' does not exist.
+----
+In this case, you can make the reference non-identifying, or you can define the node type element before this operation:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+  (:Node)-[e:REL => { prop :: STRING }]->()
+}
+----
+
+=== Relationship element reference does not exist
+For example, try to set a graph type with a relationship element reference that does not exist as follows:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+  CONSTRAINT FOR ()-[b]->() REQUIRE (b.prop) IS KEY
+}
+
+----
+
+The query returns an error with GQLSTATUS 22NC5 and the status description:
+
+[source]
+----
+error: data exception - graph type element not found. The relationship type element referenced by 'b' does not exist.
+----
+In this case, the reference could be fixed by providing a relationship type:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+  CONSTRAINT FOR ()-[b:REL]->() REQUIRE (b.prop) IS KEY
+}
+----
+
+=== Element reference omitted from constraint definition
+For example, try to define a constraint with an empty node element type reference, which is not allowed as follows:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+    CONSTRAINT FOR () REQUIRE n.prop IS UNIQUE
+}
+----
+
+The query returns an error with GQLSTATUS 22NC5 and the status description:
+
+[source]
+----
+error: data exception - graph type element not found. The node type element referenced by 'n' was does not exist.
+----
+In this case, the reference can be fixed by providing a label for the constraint:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+    CONSTRAINT FOR (n:Node) REQUIRE n.prop IS UNIQUE
+}
+----
+
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]
diff --git a/modules/ROOT/pages/errors/gql-errors/22NC6.adoc b/modules/ROOT/pages/errors/gql-errors/22NC6.adoc
new file mode 100644
index 00000000..7f3efcc9
--- /dev/null
+++ b/modules/ROOT/pages/errors/gql-errors/22NC6.adoc
@@ -0,0 +1,44 @@
+:page-role: new-2025.x cypher-25
+= 22NC6
+
+== Status description
+error: data exception - independent constraint and node element type have the same label.
+The independent constraint `{ <<constrDescrOrName>> }` is using the same label `{ <<label>> }` as a node element type.
+
+== Explanation
+This error occurs when a label is used both as an identifying label (defining a node element type) and as part of an independent constraint.
+A label cannot simultaneously serve as an identifying label and be referenced in an independent constraint.
+
+== Example scenario
+For example, try to set a property existence constraint on a property for the label `:Person`, where `:Person` is also defined as an identifying label in the graph type as follows:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+    (p:Person => {name :: STRING}),
+    CONSTRAINT FOR (p:Person =>) REQUIRE p.name IS NOT NULL
+}
+----
+
+The query returns an error with GQLSTATUS 22NC6 and the status description:
+
+[source]
+----
+error: data exception - independent constraint and node element type have the same label. The independent constraint 'Constraint( type='NODE_PROPERTY_EXISTENCE', schema=(:`Person` {`name`}) )' is using the same label `Person` as a node element type.
+----
+
+To fix this, define the property existence constraint as part of the node element type:
+
+[source, cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+    (p:Person => {name :: STRING NOT NULL})
+}
+----
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]
diff --git a/modules/ROOT/pages/errors/gql-errors/22NC7.adoc b/modules/ROOT/pages/errors/gql-errors/22NC7.adoc
new file mode 100644
index 00000000..9a083e30
--- /dev/null
+++ b/modules/ROOT/pages/errors/gql-errors/22NC7.adoc
@@ -0,0 +1,44 @@
+:page-role: new-2025.x cypher-25
+= 22NC7
+
+== Status description
+error: data exception - independent constraint and relationship element type have the same relationship type.
+The independent constraint `{ <<constrDescrOrName>> }` is using the same relationship type `{ <<relType>> }` as a relationship element type.
+
+== Explanation
+This error occurs when a relationship type is used both as an identifying relationship type (defining a relationship element type) and as part of an independent constraint.
+A relationship type cannot simultaneously serve as an identifying relationship type and be referenced in an independent constraint.
+
+== Example scenario
+For example, try to set a property type constraint on a property for the relationship type `:REL`, where `:REL` is also defined as an identifying relationship type in the graph type as follows:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+    ()-[:REL => {name :: ANY NOT NULL}]->(),
+    CONSTRAINT FOR ()-[r:REL =>]->() REQUIRE r.name IS :: STRING
+}
+----
+
+The query returns an error with GQLSTATUS 22NC7 and the status description:
+
+[source]
+----
+error: data exception - independent constraint and relationship element type have the same relationship type. The independent constraint 'Constraint( type='RELATIONSHIP_PROPERTY_TYPE', schema=()-[:`REL` {`name`}]-(), propertyType=STRING )' is using the same relationship type `REL` as a relationship element type.
+----
+
+To fix this, define the property type constraint as part of the relationship element type:
+
+[source, cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+    ()-[:REL => {name :: STRING NOT NULL}]->()
+}
+----
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]
diff --git a/modules/ROOT/pages/errors/gql-errors/22NC8.adoc b/modules/ROOT/pages/errors/gql-errors/22NC8.adoc
new file mode 100644
index 00000000..be6f6b42
--- /dev/null
+++ b/modules/ROOT/pages/errors/gql-errors/22NC8.adoc
@@ -0,0 +1,77 @@
+:page-role: new-2025.x cypher-25
+= 22NC8
+
+== Status description
+error: data exception - graph type contains duplicated tokens. The graph type includes a label, a relationship type, or an alias with the name `{ <<token>> }` more than once.
+
+== Explanation
+This error occurs when a graph type definition attempts to use the same name for more than one label, relationship type, or alias within the same scope.
+Each label, relationship type, or alias must have a unique name to avoid ambiguity in the graph schema.
+To resolve this error, ensure all labels, relationship types, and aliases are uniquely named within the graph type definition.
+
+== Example scenarios
+Let's take the following example scenarios:
+
+=== Aliases
+
+For example, try to define two node element types using the same alias as follows:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+  ( p: Person => { prop :: STRING } ),
+  ( p: Property => { prop :: STRING } )
+}
+----
+
+The query returns an error with GQLSTATUS 22NC9 and the status description:
+
+[source]
+----
+error: data exception - graph type contains duplicated tokens. The graph type includes a label, a relationship type, or an alias with the name 'p' more than once.
+----
+
+To fix this, rename one of the aliases, for example:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+  ( pers: Person => { prop :: STRING } ),
+  ( prop: Property => { prop :: STRING } )
+}
+----
+
+=== Identifiers
+
+For example, try to define two relationship element types using the same relationship type as follows:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+  ()-[n:REL => { prop :: STRING }]->(),
+  ()-[m:REL => { prop :: STRING }]->()
+}
+----
+
+The query returns an error with GQLSTATUS 22NC9 and the status description:
+
+[source]
+----
+error: data exception - graph type contains duplicated tokens. The graph type includes a label, a relationship type, or an alias with the name ':REL' more than once.
+----
+
+To fix this, delete the duplicate relationship type definition, since they are both equivalent:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+  ()-[n:REL => { prop :: STRING }]->()
+}
+----
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]
diff --git a/modules/ROOT/pages/errors/gql-errors/22NC9.adoc b/modules/ROOT/pages/errors/gql-errors/22NC9.adoc
new file mode 100644
index 00000000..ce0151cb
--- /dev/null
+++ b/modules/ROOT/pages/errors/gql-errors/22NC9.adoc
@@ -0,0 +1,42 @@
+:page-role: new-2025.x cypher-25
+= 22NC9
+
+== Status description
+error: data exception - invalid element type constraints in graph type. A `{ <<entityType>>1 }` element type property `{ <<context>> }` constraint cannot be specified inline of a `{ <<entityType>>2 }` element type.
+
+== Explanation
+Property type and existence constraints must be defined as part of the property description, not as inline constraints on graph type elements.
+
+== Example scenario
+For example, try to define an existence constraint inline of a node element type as follows:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+    (p:Person => {name :: STRING, age :: INT}) REQUIRE p.studId IS NOT NULL
+}
+----
+
+The query returns an error with GQLSTATUS 22NC9 and the status description:
+
+[source]
+----
+error: data exception - invalid element type constraints in graph type. A node element type property existence constraint cannot be specified inline of a node element type.
+----
+
+To fix this, change the query as follows:
+
+[source, cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+    (p :Person => {name :: STRING, age :: INT, studId :: ANY NOT NULL })
+}
+----
+
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]
diff --git a/modules/ROOT/pages/errors/gql-errors/22NCA.adoc b/modules/ROOT/pages/errors/gql-errors/22NCA.adoc
new file mode 100644
index 00000000..eb52094a
--- /dev/null
+++ b/modules/ROOT/pages/errors/gql-errors/22NCA.adoc
@@ -0,0 +1,53 @@
+:page-role: new-2025.x cypher-25
+= 22NCA
+
+== Status description
+error: data exception - node element type already exists. A node element type identified by the label `{ <<label>> }` already exists in the graph type.
+
+== Explanation
+
+This error occurs when attempting to add a new node element type to the graph type, but a node element type with the same label already exists.
+
+== Example scenario
+
+Given the existing graph type:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+    (p:Person => {name :: STRING })
+}
+----
+
+Execute the query:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE ADD {
+    (p:Person => {name :: STRING, age :: INT })
+}
+----
+
+The query returns an error with GQLSTATUS 22NCA and the status description:
+
+[source]
+----
+error: data exception - node element type already exists. A node element type identified by the label `:Person` already exists in the graph type.
+----
+
+To fix this, change the query as follows:
+
+[source, cypher]
+----
+ALTER CURRENT GRAPH TYPE ALTER {
+    (p:Person => {name :: STRING, age :: INT })
+}
+----
+
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]
diff --git a/modules/ROOT/pages/errors/gql-errors/22NCB.adoc b/modules/ROOT/pages/errors/gql-errors/22NCB.adoc
new file mode 100644
index 00000000..ee622089
--- /dev/null
+++ b/modules/ROOT/pages/errors/gql-errors/22NCB.adoc
@@ -0,0 +1,53 @@
+:page-role: new-2025.x cypher-25
+= 22NCB
+
+== Status description
+error: data exception - relationship element type already exists. A relationship element type identified by the relationship type `{ <<relType>> }` already exists in the graph type.
+
+== Explanation
+
+This error occurs when attempting to add a new relationship element type to the graph type, but a relationship element type with the same type already exists.
+
+== Example scenario
+
+Given the existing graph type:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+    ()-[r:REL => {name :: STRING }]->()
+}
+----
+
+Execute the query:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE ADD {
+     ()-[r:REL => {name :: STRING, age :: INT }]->()
+}
+----
+
+The query returns an error with GQLSTATUS 22NCB and the status description:
+
+[source]
+----
+error: data exception - relationship element type already exists. A relationship element type identified by the relationship type `REL` already exists in the graph type.
+----
+
+To fix this, change the query as follows:
+
+[source, cypher]
+----
+ALTER CURRENT GRAPH TYPE ALTER {
+     ()-[r:REL => {name :: STRING, age :: INT }]->()
+}
+----
+
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]
diff --git a/modules/ROOT/pages/errors/gql-errors/22NCC.adoc b/modules/ROOT/pages/errors/gql-errors/22NCC.adoc
new file mode 100644
index 00000000..44749f1e
--- /dev/null
+++ b/modules/ROOT/pages/errors/gql-errors/22NCC.adoc
@@ -0,0 +1,53 @@
+:page-role: new-2025.x cypher-25
+= 22NCC
+
+== Status description
+error: data exception - node element type specified incorrectly. The node element type `{ <<graphTypeElement>>1 }` identified by the label `{ <<label>> }` is different to the one specified in the query `{ <<graphTypeElement>>2 }`.
+
+== Explanation
+This error occurs when attempting to drop a node element type from the graph type, but the specified element type does not match the existing one for the given label. 
+
+When dropping an element type, it is not necessary to specify the full element type; you can simply specify the label.
+If you do specify an element type, it must match exactly with the existing one in the graph type.
+
+== Example scenario
+Given the following graph type:
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+    (p:Person => {name :: STRING })
+}
+----
+
+Execute the query:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE DROP {
+    (p:Person => :Student)
+}
+----
+
+The query returns an error with GQLSTATUS 22NCC and the status description:
+
+[source]
+----
+error: data exception - node element type specified incorrectly. The node element type (`p`:`Person` => {`name` :: STRING }) identified by the label `Person` is different to the one specified in the query (`p`:`Person` => :`Student`).
+----
+
+To fix this, change the query as follows:
+
+[source, cypher]
+----
+ALTER CURRENT GRAPH TYPE DROP {
+    (p:Person => )
+}
+----
+It is not necessary to specify the full element type to drop it. 
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]
diff --git a/modules/ROOT/pages/errors/gql-errors/22NCD.adoc b/modules/ROOT/pages/errors/gql-errors/22NCD.adoc
new file mode 100644
index 00000000..442d2d30
--- /dev/null
+++ b/modules/ROOT/pages/errors/gql-errors/22NCD.adoc
@@ -0,0 +1,54 @@
+:page-role: new-2025.x cypher-25
+= 22NCD
+
+== Status description
+error: data exception - relationship element type specified incorrectly. The relationship element type `{ <<graphTypeElement>>1 }` identified by the relationship type `{ <<relType>> }` is different to the one specified in the query `{ <<graphTypeElement>>2 }`.
+
+== Explanation
+This error occurs when attempting to drop a relationship element type from the graph type, but the specified element type does not match the existing one for the given relationship type. 
+
+When dropping an element type, it is not necessary to specify the full element type; you can simply specify the relationship type.
+If you do specify an element type, it must match exactly with the existing one in the graph type.
+
+== Example scenario
+Given the following graph type:
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+    ()-[r:REL => {name :: STRING }]->()
+}
+----
+
+Execute the query:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE DROP {
+     ()-[r:REL => {name :: STRING, age :: INT }]->()
+}
+----
+
+The query returns an error with GQLSTATUS 22NCD and the status description:
+
+[source]
+----
+error: data exception - relationship element type specified incorrectly. The relationship element type ()-[r:`REL` => {`name` :: STRING }]->() identified by the relationship type `REL` is different to the one specified in the query ()-[`r`:`REL` => {`name` :: STRING, `age` :: INT }]->().
+----
+
+To fix this, change the query as follows:
+
+[source, cypher]
+----
+ALTER CURRENT GRAPH TYPE DROP {
+     ()-[r:REL => ]->()
+}
+----
+It is not necessary to specify the full element type to drop it. 
+
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]
diff --git a/modules/ROOT/pages/errors/gql-errors/22NCE.adoc b/modules/ROOT/pages/errors/gql-errors/22NCE.adoc
new file mode 100644
index 00000000..3dba9ace
--- /dev/null
+++ b/modules/ROOT/pages/errors/gql-errors/22NCE.adoc
@@ -0,0 +1,54 @@
+:page-role: new-2025.x cypher-25
+= 22NCE
+
+== Status description
+error: data exception - node element type in use. The node element type identified by the label `{ <<label>> }` is referenced in the graph type element `{ <<graphTypeReference>> }` and cannot be dropped.
+
+== Explanation
+This error occurs when attempting to drop a node element type from the graph type, but the node element type is still being referenced by a relationship element type in the graph type.
+To successfully drop the node element type, you must first drop any relationship element types that reference it or remove it from the relationship element types.
+
+== Example scenario
+Given the following graph type:
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+    (p:Person => {name :: STRING }),
+    (p)-[:DRIVES]->(:Car)
+}
+----
+
+Execute the query:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE DROP {
+    (p:Person => )
+}
+----
+
+The query returns an error with GQLSTATUS 22NCE and the status description:
+
+[source]
+----
+error: data exception - node element type in use. The node element type identified by the label `Car` is referenced in the graph type element '()-[:`DRIVES` =>]->()' and cannot be dropped.
+----
+
+To fix this and drop both types, change the query as follows:
+
+[source, cypher]
+----
+ALTER CURRENT GRAPH TYPE DROP {
+    (:Person => ),
+    ()-[:DRIVES]->()
+}
+
+----
+
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]
diff --git a/modules/ROOT/pages/errors/gql-errors/22NCF.adoc b/modules/ROOT/pages/errors/gql-errors/22NCF.adoc
new file mode 100644
index 00000000..a6f17847
--- /dev/null
+++ b/modules/ROOT/pages/errors/gql-errors/22NCF.adoc
@@ -0,0 +1,128 @@
+:page-role: new-2025.x cypher-25
+= 22NCF
+
+== Status description
+error: data exception - graph type constraint not supported. Graph type constraint definitions are not supported in the `{ <<graphTypeOperation>> }` operation.
+
+== Explanation
+This error occurs when you try to specify a graph type constraint using the `DROP` or `ALTER` operations, which does not support such operations. 
+Graph type constraints may only be dropped by name when using the `DROP` operation, and are completely invalid when using `ALTER`.
+This also applies to graph type constraints defined inline of the graph type elements using `IS KEY` and `IS UNIQUE`.
+
+== Example scenario
+
+=== `ALTER` an existing constraint
+
+Given the existing graph type:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+    CONSTRAINT c1 FOR (s:Student) REQUIRE s.studentId :: INTEGER
+}
+----
+
+Execute the query:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE ALTER {
+    CONSTRAINT c1 FOR (s:Student) REQUIRE s.studentId :: STRING 
+}
+----
+
+The query returns an error with GQLSTATUS 22NCF and the status description:
+
+
+[source]
+----
+error: data exception - graph type constraint not supported. Graph type constraint definitions are not supported in the `ALTER GRAPH TYPE ALTER` operation.
+----
+
+To fix this, change the query as follows:
+
+[source, cypher]
+----
+ALTER CURRENT GRAPH TYPE DROP {
+    CONSTRAINT c1
+}
+
+ALTER CURRENT GRAPH TYPE ADD {
+    CONSTRAINT c1 FOR (s:Student) REQUIRE s.studentId :: STRING 
+}
+----
+
+=== Remove a `KEY` constraint using `ALTER`
+
+Given the existing graph type:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE SET {
+    ( :Person => {name :: STRING })
+}
+----
+
+Execute the query:
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE ALTER {
+    ( :Person => {name :: STRING IS KEY } )
+}
+----
+
+The query returns an error with GQLSTATUS 22NCF and the status description:
+
+
+[source]
+----
+error: data exception - graph type constraint not supported. Graph type constraint definitions are not supported in the `ALTER GRAPH TYPE ALTER` operation.
+----
+
+To fix this, change the query as follows:
+
+[source, cypher]
+----
+ALTER CURRENT GRAPH TYPE ADD {
+    CONSTRAINT nameForKeyConstraint FOR (p:Person) REQUIRE p.name IS KEY
+}
+
+----
+
+=== `DROP` an undesignated constraint
+
+For example, try to drop an undesignated constraint with an `ALTER CURRENT GRAPH TYPE DROP` query.
+
+[source,cypher]
+----
+ALTER CURRENT GRAPH TYPE DROP { 
+    ( :Person => {name :: STRING IS KEY}) 
+}
+----
+
+The query returns an error with GQLSTATUS 22NCF and the status description:
+
+
+[source]
+----
+error: data exception - graph type constraint not supported. Graph type constraint definitions are not supported in the `ALTER GRAPH TYPE DROP` operation.
+----
+
+To fix this, change the query as follows:
+
+[source, cypher]
+----
+ALTER CURRENT GRAPH TYPE DROP { 
+    CONSTRAINT nameOfKeyConstraint
+}
+
+----
+
+
+ifndef::backend-pdf[]
+[discrete.glossary]
+== Glossary
+
+include::partial$glossary.adoc[]
+endif::[]
diff --git a/modules/ROOT/pages/errors/gql-errors/index.adoc b/modules/ROOT/pages/errors/gql-errors/index.adoc
index d9ebd090..ad6af659 100644
--- a/modules/ROOT/pages/errors/gql-errors/index.adoc
+++ b/modules/ROOT/pages/errors/gql-errors/index.adoc
@@ -649,6 +649,68 @@ Status description:: error: data exception - invalid vector dimensions. Invalid
 
 Status description:: error: data exception - property value too big. Property value of type `{ <<typeDescription>> }` is too big (more than `{ <<bytes>> }` bytes): `{ <<value>> }`
 
+=== xref:errors/gql-errors/22NC1.adoc[22NC1]
+
+Status description:: error: data exception - graph type element contains duplicated tokens. The graph type element includes a property key with name `{ <<propKey>> }` more than once.
+
+=== xref:errors/gql-errors/22NC2.adoc[22NC2]
+
+Status description:: error: data exception - node element type has no effect. The node element type `{ <<label>> }` must contain one or more implied labels, or at least one property type.
+
+=== xref:errors/gql-errors/22NC3.adoc[22NC3]
+
+Status description:: error: data exception - relationship element type has no effect. The relationship element type `{ <<relType>> }` must define a source, destination, or at least one property type.
+
+=== xref:errors/gql-errors/22NC4.adoc[22NC4]
+
+Status description:: error: data exception - a label cannot be both identifying and implied. The label(s) `{ <<labelList>> }` are defined as both identifying and implied.
+
+=== xref:errors/gql-errors/22NC5.adoc[22NC5]
+
+Status description:: error: data exception - graph type element not found. The `{ <<entityType>> }` element type referenced by `{ <<graphTypeReference>> }` does not exist.
+
+=== xref:errors/gql-errors/22NC6.adoc[22NC6]
+
+Status description:: error: data exception - independent constraint and node element type have the same label.
+The independent constraint `{ <<constrDescrOrName>> }` is using the same label `{ <<label>> }` as a node element type.
+
+=== xref:errors/gql-errors/22NC7.adoc[22NC7]
+
+Status description:: error: data exception - independent constraint and relationship element type have the same relationship type.
+The independent constraint `{ <<constrDescrOrName>> }` is using the same relationship type `{ <<relType>> }` as a relationship element type.
+
+=== xref:errors/gql-errors/22NC8.adoc[22NC8]
+
+Status description:: error: data exception - graph type contains duplicated tokens. The graph type includes a label, a relationship type, or an alias with the name `{ <<token>> }` more than once.
+
+=== xref:errors/gql-errors/22NC9.adoc[22NC9]
+
+Status description:: error: data exception - invalid element type constraints in graph type. A `{ <<entityType>>1 }` element type property `{ <<context>> }` constraint cannot be specified inline of a `{ <<entityType>>2 }` element type.
+
+=== xref:errors/gql-errors/22NCA.adoc[22NCA]
+
+Status description:: error: data exception - node element type already exists. A node element type identified by the label `{ <<label>> }` already exists in the graph type.
+
+=== xref:errors/gql-errors/22NCB.adoc[22NCB]
+
+Status description:: error: data exception - relationship element type already exists. A relationship element type identified by the relationship type `{ <<relType>> }` already exists in the graph type.
+
+=== xref:errors/gql-errors/22NCC.adoc[22NCC]
+
+Status description:: error: data exception - node element type specified incorrectly. The node element type `{ <<graphTypeElement>> }` identified by the label `{ <<label>> }` is different to the one specified in the query `{ <<graphTypeElement>> }`. 
+
+=== xref:errors/gql-errors/22NCD.adoc[22NCD]
+
+Status description:: error: data exception - relationship element type specified incorrectly. The relationship element type `{ <<graphTypeElement>> }` identified by the relationship type `{ <<relType>> }` is different to the one specified in the query `{ <<graphTypeElement>> }`.
+
+=== xref:errors/gql-errors/22NCE.adoc[22NCE]
+
+Status description:: error: data exception - node element type in use. The node element type identified by the label `{ <<label>> }` is referenced in the graph type element `{ <<graphTypeReference>> }`` and cannot be dropped.
+
+=== xref:errors/gql-errors/22NCF.adoc[22NCF]
+
+Status description:: error: data exception - graph type constraint not supported. Graph type constraint definitions are not supported in the `{ <<graphTypeOperation>> }` operation.
+
 
 [[invalid-transaction-state]]
 == Invalid transaction state
diff --git a/modules/ROOT/partials/glossary.adoc b/modules/ROOT/partials/glossary.adoc
index 7b4c159c..c2b9573a 100644
--- a/modules/ROOT/partials/glossary.adoc
+++ b/modules/ROOT/partials/glossary.adoc
@@ -46,6 +46,9 @@
 [[funType]]$funType:: Function type, e.g. non-deterministic or aggregate.
 [[graph]]$graph:: The name of a graph, for example, `myGraph`.
 [[graphTypeDependence]]$graphTypeDependence:: Graph type dependencency for constraint, one of `UNDESIGNATED`, `INDEPENDENT`, or `DEPENDENT`.
+[[graphTypeElement]]$graphTypeElement:: An element of a graph type, for example `(:Node => { name :: STRING})`, or `(:Source)-[:REL =>]->(:Target)`. 
+[[graphTypeReference]]$graphTypeReference:: Graph type reference, for example, `(:Node =>)` or `p`.
+[[graphTypeOperation]]$graphTypeOperation:: Graph type operation, for example, one of `SET`, `ADD`, `DROP` or `ALTER`.
 [[hint]]$hint:: Freeform description of a hint, for example, `USING INDEX n:N(prop)`.
 [[hintList]]$hintList:: A list of free form descriptions of hints like `USING INDEX n:N(prop)`.
 [[idx]]$idx:: Index name, `my_index`.