fixes for the test failures

Author: renetapopova

modules/ROOT/pages/procedures.adoc

@@ -213,15 +213,15 @@ For more information, see the link:{neo4j-docs-base-uri}/cdc/{page-version}/[CDC
 | *Replaced by* 3+| xref:procedures.adoc#db_cdc_earliest[`db.cdc.earliest()`]
 |===
 
-[role=label--enterprise-edition label--new-5.13 label--beta label--deprecated-5.17]
+[role=label--enterprise-edition label--new-5.13 label--beta label--deprecated-5.17 label--admin-only]
 [[procedure_cdc_query]]
 === cdc.query()
 
 
 .Details
 |===
 | *Syntax* 3+m| cdc.query([ from selectors ]) :: (id, txId, seq, metadata, event)
-| *Description* 3+a| Query changes that happened from the provided change identifier.
+| *Description* 3+a| Query changes happened from the provided change identifier.
 .3+| *Input arguments* | *Name* | *Type* | *Description*
 | `from` | `STRING` | The change identifier to query changes from.
 | `selectors` | `LIST<MAP>` | An optional list of selectors to filter out changes.
@@ -334,6 +334,19 @@ Since Neo4j 5.23, it can be run with the `SERVER MANAGEMENT` privilege.
 It will still run with the `Admin` privilege, but that should be considered deprecated.
 ====
 
+[[procedure_dbms_cluster_movetonextdiscoveryversion]]
+[role=label--enterprise-edition label--new-5.26 label--admin-only ]
+.dbms.cluster.moveToNextDiscoveryVersion()
+[cols="<15s,<85"]
+|===
+| Description
+a| The procedure triggers a switch to the next discovery service version for all known members of the cluster (as listed in the system database and discovery).
+For example, if the current member's discovery version is V1_ONLY, it will switch all members to V1_OVER_V2. In case of failure, the user must manually resolve the issue.
+| Signature
+m| dbms.cluster.moveToNextDiscoveryVersion()
+| Mode
+m|DBMS
+|===
 
 [role=label--enterprise-edition label--new-5.23]
 [[procedure_dbms_cluster_deallocateDatabaseFromServer]]
@@ -644,19 +657,6 @@ It will still run with the `Admin` privilege, but that should be considered depr
 |===
 
 
-[role=label--enterprise-edition label--new-5.26 label--admin-only ]
-[[procedure_dbms_cluster_movetonextdiscoveryversion]]
-=== dbms.cluster.moveToNextDiscoveryVersion()
-
-.Details
-|===
-| *Syntax* 3+m| dbms.cluster.moveToNextDiscoveryVersion()
-| *Description* 3+a| The procedure triggers a switch to the next discovery service version for all known members of the cluster (as listed in the system database and discovery).
-For example, if the current member's discovery version is V1_ONLY, it will switch all members to V1_OVER_V2. In case of failure, the user must manually resolve the issue.
-| *Mode* 3+| DBMS
-|===
-
-
 [role=label--enterprise-edition label--new-5.24 label--admin-only]
 [[procedure_dbms_cluster_statusCheck]]
 === dbms.cluster.statusCheck()
@@ -1280,6 +1280,29 @@ Use the `db.index.vector.queryNodes` procedure to query the named index.
 As of Neo4j 5.15, vector indexes can be created with the Cypher Command `CREATE VECTOR INDEX`.
 For more information, see the link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/indexes/semantic-indexes/vector-indexes/#create-vector-index[Cypher Manual -> Create a vector index].
 
+[role=label--new-5.18]
+[[procedure_db_index_vector_createrelationshipindex]]
+
+=== db.index.vector.queryNodes()
+
+
+.Details
+|===
+| *Syntax* 3+m| db.index.vector.queryNodes(indexName, numberOfNearestNeighbours, query) :: (node, score)
+| *Description* 3+a| Query the given node vector index.
+Returns requested number of nearest neighbors to the provided query vector, and their similarity score to that query vector, based on the configured similarity function for the index.
+The similarity score is a value between [0, 1]; where 0 indicates least similar, 1 most similar.
+
+.4+| *Input arguments* | *Name* | *Type* | *Description*
+| `indexName` | `STRING` | The name of the vector index.
+| `numberOfNearestNeighbours` | `INTEGER` | The size of the vector neighbourhood.
+| `query` | `ANY` | The object to find approximate matches for.
+.3+| *Return arguments* | *Name* | *Type* | *Description*
+| `node` | `NODE` | A node which contains a vector property similar to the query object.
+| `score` | `FLOAT` | The score measuring how similar the node property is to the query object.
+| *Mode* 3+| READ
+|===
+
 [role=label--new-5.18]
 [[procedure_db_index_vector_queryrelationships]]
 === db.index.vector.queryRelationships()
@@ -1312,7 +1335,13 @@ The similarity score is a value between [0, 1]; where 0 indicates least similar,
 .Details
 |===
 | *Syntax* 3+m| genai.vector.encodeBatch(resources, provider, configuration) :: (index, resource, vector)
-| *Description* 3+a|  Generate several vector embeddings with a single API request.
+| *Description* 3+a|  Encode a given batch of resources as vectors using the named provider.
+For each element in the given resource LIST this returns:
+
+* the corresponding 'index' within that LIST,
+* the original 'resource' element itself,
+* and the encoded 'vector'.
+
 .4+| *Input arguments* | *Name* | *Type* | *Description*
 | `resources` | `LIST<STRING>` | The object to transform into an embedding.
 | `provider` | `STRING` | The GenAI provider to use.
@@ -1341,7 +1370,7 @@ The types are still enforced as `LIST<INTEGER | FLOAT>`.
 .Details
 |===
 | *Syntax* 3+m| genai.vector.listEncodingProviders() :: (name, requiredConfigType, otionalConfigType, defaultConfig)
-| *Description* 3+a| List the available GenAI providers.
+| *Description* 3+a| Lists the available vector embedding providers.
 .5+| *Return arguments* | *Name* | *Type* | *Description*
 | `name` | `STRING` | The name of the GenAI provider.
 | `requiredConfigType` | `STRING` | The signature of the required config map.
@@ -1402,7 +1431,7 @@ For more information, see the link:{neo4j-docs-base-uri}/cypher-manual/{page-ver
 
 
 [[procedure_db_index_fulltext_awaiteventuallyconsistentindexrefresh]]
-=== db.index.fulltext.waitEventuallyConsistentIndexRefresh()
+=== db.index.fulltext.awaitEventuallyConsistentIndexRefresh()
 
 
 .Details