generate the index file and editorial updates

Author: renetapopova

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

@@ -1,10 +1,10 @@
 = 22ND3
 
 == Status description
-error: data exception - wrong property for vector search filtering. The property `{ <<propKey>> }` has not been added as an additional property for the vector index `{ <<idx>> }`.
+error: data exception - wrong property for vector search filtering. The property `{ <<propKey>> }` has not been added as an additional property to the vector index `{ <<idx>> }`.
 
 == Example scenario
-For example, assuming that you have a vector index created by
+For example, assuming that you have a vector index created by the following command:
 
 [source,cypher]
 ----
@@ -14,7 +14,7 @@ FOR (m:Movie) ON m.embedding
 WITH [m.rating]
 ----
 
-When using another property key than `rating` in a vector search filter:
+When using a property key other than `rating` in a vector search filter:
 
 [source,cypher]
 ----
@@ -33,10 +33,11 @@ You will receive an error with GQLSTATUS 22ND3 and status description:
 
 [source]
 ----
-error: data exception - wrong property for vector search filtering. The property `votes` has not been added as an additional property for the vector index 'moviePlots'.
+error: data exception - wrong property for vector search filtering. The property `votes` has not been added as an additional property to the vector index 'moviePlots'.
 ----
 
 == Possible solution
+
 If you want to use the property `votes` for vector search filtering, it must be an additional property of the vector index.
 This can be achieved by dropping and re-creating the vector index like this:
 

modules/ROOT/pages/errors/gql-errors/42I73.adoc

@@ -1,10 +1,10 @@
 = 42I73
 
 == Status description
-error: syntax error or access rule violation - invalid predicate for vector search filtering. A vector search filter must consist of one or more predicates joined by AND, and the combined predicates for each property must specify either an exact value (e.g. x.prop = 1), an open range (e.g. x.prop >= 1), or a between range (e.g. x.prop > 1 AND x.prop < 100). `{ <<expr>> }` does not fulfill this.
+error: syntax error or access rule violation - invalid predicate for vector search filtering. A vector search filter must consist of one or more predicates joined by `AND`, and the combined predicates for each property must specify either an exact value (e.g. `x.prop = 1`), an open range (e.g. `x.prop >= 1`), or a between range (e.g. `x.prop > 1 AND x.prop < 100`). `{ <<expr>> }` does not fulfill this.
 
 == Example scenarios
-For example, assuming that you have a vector index created by:
+For example, assuming that you have a vector index created by the following command:
 
 [source,cypher]
 ----
@@ -14,6 +14,9 @@ FOR (m:Movie) ON m.embedding
 WITH [m.rating]
 ----
 
+
+.Using `NOT` inside a vector search filter
+=====
 When trying to use `NOT` inside a vector search filter:
 
 [source,cypher]
@@ -33,9 +36,12 @@ You will receive an error with GQLSTATUS xref:errors/gql-errors/42001.adoc[42001
 
 [source]
 ----
-error: syntax error or access rule violation - invalid predicate for vector search filtering. A vector search filter must consist of one or more predicates joined by AND, and the combined predicates for each property must specify either an exact value (e.g. x.prop = 1), an open range (e.g. x.prop >= 1), or a between range (e.g. x.prop > 1 AND x.prop < 100). `NOT movie.rating = 8` does not fulfill this.
+error: syntax error or access rule violation - invalid predicate for vector search filtering. A vector search filter must consist of one or more predicates joined by AND, and the combined predicates for each property must specify either an exact value (e.g. `x.prop = 1`), an open range (e.g. `x.prop >= 1`), or a between range (e.g. `x.prop > 1 AND x.prop < 100`). `NOT movie.rating = 8` does not fulfill this.
 ----
+=====
 
+.Using multiple open ranges on the same property inside a vector search filter
+=====
 When trying to use multiple open ranges on the same property inside a vector search filter:
 
 [source,cypher]
@@ -55,8 +61,9 @@ You will receive an error with GQLSTATUS xref:errors/gql-errors/42001.adoc[42001
 
 [source]
 ----
-error: syntax error or access rule violation - invalid predicate for vector search filtering. A vector search filter must consist of one or more predicates joined by AND, and the combined predicates for each property must specify either an exact value (e.g. x.prop = 1), an open range (e.g. x.prop >= 1), or a between range (e.g. x.prop > 1 AND x.prop < 100). `movie.rating > 6 AND movie.rating > 8` does not fulfill this.
+error: syntax error or access rule violation - invalid predicate for vector search filtering. A vector search filter must consist of one or more predicates joined by AND, and the combined predicates for each property must specify either an exact value (e.g. `x.prop = 1`), an open range (e.g. `x.prop >= 1`), or a between range (e.g. `x.prop > 1 AND x.prop < 100`). `movie.rating > 6 AND movie.rating > 8` does not fulfill this.
 ----
+=====
 
 == Possible solution
 Certain predicates are possible to rewrite so they adhere to the rules of vector search filtering.

modules/ROOT/pages/errors/gql-errors/42I74.adoc

@@ -4,7 +4,7 @@
 error: syntax error or access rule violation - wrong variable for vector search filtering. The variable `{ <<variable>>1 }` in a vector search filter property predicate must be the same as the search clause binding variable `{ <<variable>>2 }`.
 
 == Example scenario
-For example, assuming that you have a vector index created by:
+For example, assuming that you have a vector index created by the following command:
 
 [source,cypher]
 ----
@@ -14,7 +14,7 @@ FOR (m:Movie) ON m.embedding
 WITH [m.rating]
 ----
 
-When trying to use another variable than `movie` in the vector search filter in the following query:
+When trying to use a variable other than `movie` in the vector search filter in the following query:
 
 [source,cypher]
 ----

modules/ROOT/pages/errors/gql-errors/42I75.adoc

@@ -4,7 +4,7 @@
 error: syntax error or access rule violation - self-referencing in vector search. The expression `{ <<expr>> }` in the search clause may not depend on the search clause binding variable `{ <<variable>> }`.
 
 == Example scenarios
-For example, assuming that you have a vector index created by:
+For example, assuming that you have a vector index created by the following command:
 
 [source,cypher]
 ----
@@ -14,6 +14,8 @@ FOR (m:Movie) ON m.embedding
 WITH [m.rating]
 ----
 
+.Using the search binding variable in the `FOR` subclause of a vector search
+=====
 When trying to use the search binding variable `movie` in the `FOR` subclause in the following query:
 
 [source,cypher]
@@ -34,7 +36,10 @@ You will receive an error with GQLSTATUS xref:errors/gql-errors/42001.adoc[42001
 ----
 error: syntax error or access rule violation - self-referencing in vector search. The expression `movie.embedding` in the search clause may not depend on the search clause binding variable `movie`.
 ----
+=====
 
+.Using the search binding variable in the `WHERE` subclause of a vector search
+=====
 When trying to use the search binding variable `movie` in the RHS of the predicate in the `WHERE` subclause in the following query:
 
 [source,cypher]
@@ -57,6 +62,7 @@ You will receive an error with GQLSTATUS xref:errors/gql-errors/42001.adoc[42001
 ----
 error: syntax error or access rule violation - self-referencing in vector search. The expression `movie.year` in the search clause may not depend on the search clause binding variable `movie`.
 ----
+=====
 
 ifndef::backend-pdf[]
 [discrete.glossary]

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

@@ -714,6 +714,10 @@ Status description:: error: data exception - operation not allowed for roles tha
 
 Status description:: error: data exception - operation not allowed for roles with `DENY` privileges. Invalid input: `'{ <<query>> }'` is not allowed for roles with `DENY` privileges.
 
+=== xref:errors/gql-errors/22ND3.adoc[22ND3]
+
+Status description:: error: data exception - wrong property for vector search filtering. The property `{ <<propKey>> }` has not been added as an additional property to the vector index `{ <<idx>> }`.
+
 
 [[invalid-transaction-state]]
 == Invalid transaction state
@@ -1155,6 +1159,18 @@ Status description:: error: syntax error or access rule violation - unsupported
 
 Status description:: error: syntax error or access rule violation - mismatched pattern. Pattern, `{ <<input>>1 }`, does not match input, `{ <<input>>2 }`. Verify that the pattern is valid for constructing `{ <<valueType>> }`.
 
+=== xref:errors/gql-errors/42I73.adoc[42I73]
+
+Status description:: error: syntax error or access rule violation - invalid predicate for vector search filtering. A vector search filter must consist of one or more predicates joined by `AND`, and the combined predicates for each property must specify either an exact value (e.g. `x.prop = 1`), an open range (e.g. `x.prop >= 1`), or a between range (e.g. `x.prop > 1 AND x.prop < 100`). `{ <<expr>> }` does not fulfill this.
+
+=== xref:errors/gql-errors/42I74.adoc[42I74]
+
+Status description:: error: syntax error or access rule violation - wrong variable for vector search filtering. The variable `{ <<variable>>1 }` in a vector search filter property predicate must be the same as the search clause binding variable `{ <<variable>>2 }`.
+
+=== xref:errors/gql-errors/42I75.adoc[42I75]
+
+Status description:: error: syntax error or access rule violation - self-referencing in vector search. The expression `{ <<expr>> }` in the search clause may not depend on the search clause binding variable `{ <<variable>> }`.
+
 === xref:errors/gql-errors/42N00.adoc[42N00]
 
 Status description:: error: syntax error or access rule violation - graph reference not found. A graph reference with the name `{ <<db>> }` was not found. Verify that the spelling is correct.