Uncollapse limitations and known issues in vector indexes (neo4j#1287)

Author: JPryce-Aklundh

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

@@ -515,11 +515,8 @@ Returns the requested number of approximate nearest neighbor relationships and t
 == Limitations and known issues
 
 As of Neo4j 5.13, the vector index is no longer a beta feature.
-It does, however, still contain some limitations and known issues.
+It does, however, still contain some limitations:
 
-.*Limitations*
-[%collapsible]
-====
 * The query is an _approximate_ nearest neighbor search.
 The requested _k_ nearest neighbors may not be the exact _k_ nearest, but close within the same wider neighborhood.
 
@@ -529,13 +526,11 @@ The requested _k_ nearest neighbors may not be the exact _k_ nearest, but close
 For example, you cannot have one xref:indexes/semantic-indexes/vector-indexes.adoc#similarity-functions[Euclidean] and one xref:indexes/semantic-indexes/vector-indexes.adoc#similarity-functions[cosine] vector index on the same label-property key pair.
 
 * Changes made within the same transaction are not visible to the index.
-====
 
-.*Known issues*
-[%collapsible]
-====
-The following table lists the known issues and, if fixed, the version in which they were fixed:
+Vector indexes also contain some known issues.
+The following table lists the issues and, if fixed, the version in which they were fixed:
 
+.Known issues
 [%header,cols="5a,d"]
 |===
 | Known issues | Fixed in
@@ -686,5 +681,3 @@ Ensure that all cluster members have been updated to use Neo4j 5.11 (or a newer
 
 | Neo4j 5.12
 |===
-
-====