Apply suggestions from code review

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

Author: 3 people

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

@@ -5,7 +5,7 @@ error: data exception - graph type element not found. The `{ <<entityType>> }` e
 
 == 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 this error is returned to indicate the missing element.
+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
 
@@ -25,7 +25,7 @@ The query returns an error with GQLSTATUS 22NC5 and the status description:
 ----
 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 to be non-identifying, or you can define the node type element before this operation:
+In this case, you can make the reference non-identifying, or you can define the node type element before this operation:
 
 [source,cypher]
 ----

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

@@ -1,7 +1,7 @@
 = 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.more than once.
+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.
@@ -10,6 +10,7 @@ To resolve this error, ensure all labels, relationship types, and aliases are un
 
 == 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: