update vector index known issue fixes (#705) (#708)

Co-authored-by: Matthew Parnell <[email protected]>

modules/ROOT/pages/indexes-for-vector-search.adoc

@@ -414,11 +414,11 @@ The procedures are still usable, just not visible.
 ====
 Vector indexes configured with dimensionality greater than `2048` in Neo4j 5.11 should continue to work after the limitation is applied.
 ====
-|
+| Neo4j 5.12
 
 d| The validation for xref:indexes-vector-similarity-cosine[cosine similarity] verifies that the vector's {l2-norm} can be represented finitely in {ieee-754} *double* precision, rather than in _single_ precision.
 This can lead to certain large component vectors being incorrectly indexed, and return a similarity score of `±0.0`.
-a| // Neo4j 5.12    pending PR
+| Neo4j 5.12
 
 | {link-procedures-reference}#procedure_db_index_vector_queryNodes[`db.index.vector.queryNodes`] query vector validation is incorrect with a xref:indexes-vector-similarity-cosine[cosine] vector index. The {l2-norm} validation only considers the last component of the vector. If that component is `±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 `±0.0`.
 
@@ -427,7 +427,7 @@ a| // Neo4j 5.12    pending PR
 For {l2-norm}alized vectors (unit vectors), thus having unit length image:l2norm_is_1.svg["The l2-norm of vector v equals 1"], Euclidean and cosine similarity functions produce the same similarity ordering.
 It is _recommended_ to normalize your vectors (if needed), and use a xref:indexes-vector-similarity-euclidean[Euclidean] vector index.
 ====
-a| // Neo4j 5.12    pending PR
+| Neo4j 5.12
 
 | The vector index `createStatement` field from xref:indexes-for-search-performance.adoc#indexes-list-indexes[`SHOW INDEXES`] does not correctly escape single quotes in index names, labels, and property keys.
 | Neo4j 5.12
@@ -462,7 +462,7 @@ The older Neo4j versions will fail to understand the transaction.
 ====
 Ensure that all cluster members have been updated to use Neo4j 5.11 (or a newer version) before calling `dbms.upgrade()` on the `system` database. Once committed, vector indexes can be safely created on the cluster.
 ====
-a| // Neo4j 5.12    pending PR
+| Neo4j 5.12
 
 |===