cypher 5 specific procedure formatting

Author: JPryce-Aklundh

modules/ROOT/pages/indexes/semantic-indexes/vector-indexes.adoc

@@ -110,7 +110,7 @@ In this example, the vector dimension is explicitly set to `1536` and the vector
 To read more about the available similarity functions, see xref:indexes/semantic-indexes/vector-indexes.adoc#similarity-functions[].
 
 [NOTE]
-Prior to Neo4j 5.15, node vector indexes were created using the link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_index_vector_createNodeIndex[`db.index.vector.createNodeIndex`] procedure.
+Prior to Neo4j 5.15, node vector indexes were created using the link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_index_vector_createNodeIndex[`db.index.vector.createNodeIndex()`] procedure.
 
 You can also create a vector index for relationships with a particular type on a given property using the following syntax:
 
@@ -240,7 +240,7 @@ Note that all movies returned have a plot centred around criminal family organiz
 The `score` results are  returned in _descending order_, where the best matching result entry is put first (in this case, `The Godfather` has a similarity score of `1.0`, which is to be expected as the index was queried with this specific property).
 If the query vector itself is not wanted, adding the predicate `WHERE score < 1` removes identical vectors.
 
-To query a relationship vector index, use the link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_index_vector_queryRelationships[`db.index.vector.queryRelationships`] procedure.
+To query a relationship vector index, use the link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_index_vector_queryRelationships[`db.index.vector.queryRelationships()`] procedure.
 
 .Signature for `db.index.vector.queryRelationships()` label:new[Introduced in 5.18]
 [source,syntax]
@@ -483,7 +483,7 @@ image::euclidean_similarity_equation.svg["The Euclidean of vector v and vector u
 | Usage | Procedure | Description
 
 | Create node vector index.
-| link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_index_vector_createNodeIndex[`db.index.vector.createNodeIndex`]
+| link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_index_vector_createNodeIndex[`db.index.vector.createNodeIndex()`]
 | Create a vector index for the specified label and property with the given vector dimension using the given similarity function.
 Replaced by the `CREATE VECTOR INDEX` command.
 
@@ -564,7 +564,7 @@ The types are still enforced as `LIST<INTEGER \| FLOAT>`.
 
 [TIP]
 --
-Use the procedure `db.index.vector.createNodeIndex` to create the a vector index.
+Use the procedure `db.index.vector.createNodeIndex()` to create the a vector index.
 Procedure signature:
 [source,syntax,role="noheader"]
 ----
@@ -611,9 +611,9 @@ To work around this issue if you need to run multiple vector index queries and m
 
 | xref:clauses/listing-procedures.adoc[`SHOW PROCEDURES`] does not show the vector index procedures:
 
-* link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_create_setVectorProperty[`db.create.setVectorProperty`]
-* link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_index_vector_createNodeIndex[`db.index.vector.createNodeIndex`]
-* link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_index_vector_queryNodes[`db.index.vector.queryNodes`]
+* link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_create_setVectorProperty[`db.create.setVectorProperty()`]
+* link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_index_vector_createNodeIndex[`db.index.vector.createNodeIndex()`]
+* link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_index_vector_queryNodes[`db.index.vector.queryNodes()`]
 
 [NOTE]
 --
@@ -636,7 +636,7 @@ d| The validation for xref:indexes/semantic-indexes/vector-indexes.adoc#similari
 This can lead to certain large component vectors being incorrectly indexed, and return a similarity score of `&plusmn;0.0`.
 | Neo4j 5.12
 
-| link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_index_vector_queryNodes[`db.index.vector.queryNodes`] query vector validation is incorrect with a xref:indexes/semantic-indexes/vector-indexes.adoc#similarity-functions[cosine] vector index. The {l2-norm} validation only considers the last component of the vector. If that component is `&plusmn;0.0`, an otherwise valid query vector will be thrown as invalid. This can also result in some invalid vectors being used to query, and return a similarity score of `&plusmn;0.0`.
+| link:{neo4j-docs-base-uri}/operations-manual/current/procedures/#procedure_db_index_vector_queryNodes[`db.index.vector.queryNodes()`] query vector validation is incorrect with a xref:indexes/semantic-indexes/vector-indexes.adoc#similarity-functions[cosine] vector index. The {l2-norm} validation only considers the last component of the vector. If that component is `&plusmn;0.0`, an otherwise valid query vector will be thrown as invalid. This can also result in some invalid vectors being used to query, and return a similarity score of `&plusmn;0.0`.
 
 [TIP]
 --