Apply editorial suggestions from code review

Co-authored-by: Reneta Popova <[email protected]>

Author: mnd999

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

@@ -4,10 +4,10 @@
 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 element types, and relationship element types may only define a property once.
+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 with :
+For example, try to set a graph type as follows:
 
 [source,cypher]
 ----
@@ -16,14 +16,14 @@ ALTER CURRENT GRAPH TYPE SET {
 }
 ----
 
-An error will be thrown with GQLSTATUS 22NC1 and the status description:
+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.
 ----
 
-This can be corrected by removing the duplicate property key definition or naming the property keys uniquely:
+To fix this, remove the duplicate property key definition or uniquely name the property keys:
 
 [source, cypher]
 ----

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

@@ -4,11 +4,11 @@
 error: data exception - node element type is ineffectual. 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 have some effect.
+When defining a graph type, node element types must have some effect; otherwise, they are not allowed.
 Ineffectual node element types are not permitted.
 
 == Example scenario
-For example, try to set a graph type with :
+For example, try to set a graph type as follows:
 
 [source,cypher]
 ----
@@ -17,14 +17,14 @@ ALTER CURRENT GRAPH TYPE SET {
 }
 ----
 
-An error will be thrown with GQLSTATUS 22NC2 and the status description:
+The query returns an error with GQLSTATUS 22NC2 and the status description:
 
 [source]
 ----
 error: data exception - node element type is ineffectual. The node element type `Node` must contain one or more implied labels, or at least one property type.
 ----
 
-This can be corrected by defining at least one property type or by adding an implied label e.g.:
+To fix this, define at least one property type or add an implied label, for example:
 
 [source,cypher]
 ----

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

@@ -4,7 +4,8 @@
 error: data exception - relationship element type is ineffectual. 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:
+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
@@ -20,14 +21,14 @@ ALTER CURRENT GRAPH TYPE SET {
 }
 ----
 
-An error will be thrown with GQLSTATUS 22NC3 and the status description:
+The query returns an error with GQLSTATUS 22NC3 and the status description:
 
 [source]
 ----
 error: data exception - relationship element type is ineffectual. The relationship element type `REL` must define a source or destination, or at least one property type.
 ----
 
-This can be corrected by defining at least one property type or by adding a node element type e.g.:
+To fix this, define at least one property type or add a node element type, for example:
 
 [source,cypher]
 ----

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

@@ -5,11 +5,11 @@ error: data exception - a label cannot both identifying and implied. The label(s
 
 == Explanation
 When defining a graph type, labels and relationships must be assigned clear roles.
-A label cannot be both "identifying" (used to uniquely identify nodes) and "implied" (automatically assigned based on other schema rules) at the same time.
+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:
+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]
 ----
@@ -19,14 +19,14 @@ ALTER CURRENT GRAPH TYPE SET {
 }
 ----
 
-An error will be thrown with GQLSTATUS 22NC4 and the status description:
+The query returns an error with GQLSTATUS 22NC4 and the status description:
 
 [source]
 ----
 error: data exception - a label cannot both identifying and implied. The label(s) `Person` are defined as both identifying and implied.
 ----
 
-There are several ways to correct this, but one approch may be to add another label to both nodes and capture the property type on `name` there:
+One way to fix this is to add another label to both nodes and capture the property type on `name` there:
 
 [source,cypher]
 ----

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

@@ -9,8 +9,8 @@ If the referenced node or relationship type does not exist, the operation cannot
 
 == Example scenarios
 
-=== Node element reference not found ===
-For example, try to set a graph type with an identiying node element reference that does not exist:
+=== 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]
 ----
@@ -19,13 +19,13 @@ ALTER CURRENT GRAPH TYPE SET {
 }
 ----
 
-An error will be thrown with GQLSTATUS 22NC5 and the status description:
+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 =>)' was not found.
 ----
-In this case, the reference could be corrected to be non-identifying, or the node type element could be defined before this operation:
+In this case, you can make the reference to be non-identifying, or you can define the node type element before this operation:
 
 [source,cypher]
 ----
@@ -34,8 +34,8 @@ ALTER CURRENT GRAPH TYPE SET {
 }
 ----
 
-=== Relationship element reference not found ===
-For example, try to set a graph type with a relationship element reference that does not exist:
+=== 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]
 ----
@@ -45,13 +45,13 @@ ALTER CURRENT GRAPH TYPE SET {
 
 ----
 
-An error will be thrown with GQLSTATUS 22NC5 and the status description:
+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' was not found.
 ----
-In this case, the reference could be corrected by providing a relationship type:
+In this case, the reference could be fixed by providing a relationship type:
 
 [source,cypher]
 ----
@@ -60,22 +60,22 @@ ALTER CURRENT GRAPH TYPE SET {
 }
 ----
 
-=== Element reference ommitted from constraint definition ===
-In this example, a constraint is defined with an empty node element type reference, which is not allowed: 
+=== 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
 ----
 
-An error will be thrown with GQLSTATUS 22NC5 and the status description:
+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 not found.
 ----
-In this case, the reference can be corrected by providing a Label for the constraint:
+In this case, the reference can be fixed by providing a label for the constraint:
 
 [source,cypher]
 ----

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

@@ -6,10 +6,10 @@ The independent constraint `{ <<constrDescrOrName>> }` is using the same label `
 
 == 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 serve as both an identifying label and be referenced in an independent constraint at the same time.
+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:
+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]
 ----
@@ -19,14 +19,14 @@ ALTER CURRENT GRAPH TYPE SET {
 }
 ----
 
-An error will be thrown with GQLSTATUS 22NC6 and the status description:
+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.
 ----
 
-The correct fix is to define the property existence constraint as part of the node element type:
+To fix this, define the property existence constraint as part of the node element type:
 
 [source, cypher]
 ----

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

@@ -6,10 +6,10 @@ The independent constraint `{ <<constrDescrOrName>> }` is using the same relatio
 
 == 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 label cannot serve as both an identifying label and be referenced in an independent constraint at the same time.
+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:
+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]
 ----
@@ -19,14 +19,14 @@ ALTER CURRENT GRAPH TYPE SET {
 }
 ----
 
-An error will be thrown with GQLSTATUS 22NC7 and the status description:
+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.
 ----
 
-The correct fix is to define the property type constraint as part of the relationship element type:
+To fix this, define the property type constraint as part of the relationship element type:
 
 [source, cypher]
 ----

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

@@ -6,13 +6,13 @@ error: data exception - graph type contains duplicated tokens. The graph type in
 == 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 that all labels, relationship types, and aliases are uniquely named within the graph type definition.
+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
 
-Attempt to define two node element types using the same alias.
+For example, try to define two node element types using the same alias as follows:
 
 [source,cypher]
 ----
@@ -22,14 +22,14 @@ ALTER CURRENT GRAPH TYPE SET {
 }
 ----
 
-An error will be thrown with GQLSTATUS 22NC9 and the status description:
+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, relationship type or alias with name 'p' more than once.
 ----
 
-This can be corrected by renaming one of the aliases, for example:
+To fix this, rename one of the aliases, for example:
 
 [source,cypher]
 ----
@@ -41,7 +41,7 @@ ALTER CURRENT GRAPH TYPE SET {
 
 === Identifiers
 
-Attempt to define two relationship element types using the same relationship type.
+For example, try to define two relationship element types using the same relationship type as follows:
 
 [source,cypher]
 ----
@@ -51,14 +51,14 @@ ALTER CURRENT GRAPH TYPE SET {
 }
 ----
 
-An error will be thrown with GQLSTATUS 22NC9 and the status description:
+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, relationship type or alias with name ':REL' more than once.
 ----
 
-In this case, the correction is to delete the duplicate relationship type definition, since they are both equivalent:
+To fix this, delete the duplicate relationship type definition, since they are both equivalent:
 
 [source,cypher]
 ----

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

@@ -8,7 +8,7 @@ Property type and existance constrains cannot be defined as inline constraints o
 They should be defined as part of the property description instead.
 
 == Example scenario
-Attempt to define an existance constraint inline of a node element type as follows:
+For example, try to define an existence constraint inline of a node element type as follows:
 
 [source,cypher]
 ----
@@ -17,14 +17,14 @@ ALTER CURRENT GRAPH TYPE SET {
 }
 ----
 
-An error will be thrown with GQLSTATUS 22NCA and the status description:
+The query returns an error with GQLSTATUS 22NCA 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.
 ----
 
-A correct definition is as follows:
+To fix this, change the query as follows:
 
 [source, cypher]
 ----