post review update

modules/ROOT/pages/indexes/search-performance-indexes/managing-indexes.adoc

@@ -1043,13 +1043,13 @@ If an index with that name exists it is removed, if not the command fails.
 
 _This feature was introduced in Neo4j 5.16._
 
-The following statement will attempt to drop the index named `node_range_index_name` using a parameter for the index name.
+The following statement will attempt to drop the index named `range_index_param` using a parameter for the index name.
 
 .Parameters
 [source,javascript, indent=0]
 ----
 {
-  "name": "node_range_index_name"
+  "name": "range_index_param"
 }
 ----
 

modules/ROOT/pages/indexes/semantic-indexes/full-text-indexes.adoc

@@ -36,8 +36,7 @@ If no name is given when created, a random name will be assigned to the full-tex
 
 The `CREATE FULLTEXT INDEX` command is optionally idempotent.
 This mean that its default behavior is to throw an error if an attempt is made to create the same index twice.
-If `IF NOT EXISTS` is appended to the command, no error is thrown and nothing happens should an index with the same name or same schema and index type already exist.
-It may still throw an error if conflicting constraints exist, such as constraints with the same name or schema and backing index type.
+If `IF NOT EXISTS` is appended to the command, no error is thrown and nothing happens should an index with the same name or a full-text index on the same schema already exist.
 As of Neo4j 5.16, the index name can also be given as a parameter, `CREATE FULLTEXT INDEX $name FOR ...`.
 
 [TIP]
@@ -69,8 +68,6 @@ This statement creates a full-text index named `communications` on the `message`
 CREATE FULLTEXT INDEX communications FOR ()-[r:REVIEWED|EMAILED]-() ON EACH [r.message]
 ----
 
-Full-text indexes follow the same xref:indexes/index.adoc#naming-rules-and-recommendations[naming rules and best-practices] as search-performance indexes.
-
 [[tokenization-analyzers]]
 === Tokenization and analyzers
 

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

@@ -342,7 +342,7 @@ The following example shows how to define embeddings as Cypher parameters by mat
 ----
 MATCH (n:Node {id: $id})
 CALL db.create.setNodeVectorProperty(n, 'propertyKey', $vector)
-RETURN node
+RETURN n
 ----
 
 Furthermore, you can also use a list parameter containing several `MATCH` criteria and embeddings to update multiple nodes in an `UNWIND` clause.