vector page cleanup

Author: JPryce-Aklundh

modules/ROOT/pages/values-and-types/vector.adoc

@@ -177,7 +177,7 @@ Embeddings stored as `VECTOR` property values can be indexed and searched semant
 [[vector-type-normalization]]
 == VECTOR type normalization 
 
-Cypher runs a normalization algorithm on all `VECTOR` types, converting them into a consistent, deterministic form for equivalent types.
+Cypher runs a normalization algorithm on all `VECTOR` types, converting them into a consistent form for equivalent types.
 The following rules apply to `VECTOR` normalization:
 
 * A `VECTOR` type without a defined coordinate type or dimension encompasses all others.
@@ -188,43 +188,43 @@ The following rules apply to `VECTOR` normalization:
 .`VECTOR` type normalization
 [cols="3,3,5", options="header"]
 |===
-| Compared types |Normalized Result |Reason
+| Compared types | Normalized Result | Reason
 
-|`VECTOR \| VECTOR<FLOAT32>(12345)`
-|`VECTOR`
-|`VECTOR` is the supertype and encompasses all others.
+| `VECTOR \| VECTOR<FLOAT32>(12345)`
+| `VECTOR`
+| `VECTOR` is the supertype and encompasses all others.
 
-|`VECTOR<FLOAT32> \| VECTOR(12345)`
-|`VECTOR<FLOAT32> \| VECTOR(12345)`
-|Cannot be normalized — one lacks a dimension, the other lacks a type.
+| `VECTOR<FLOAT32> \| VECTOR(12345)`
+| `VECTOR<FLOAT32> \| VECTOR(12345)`
+| Cannot be normalized — one vector lacks a dimension, the other lacks a coordinate type.
 
-|`VECTOR<FLOAT32> \| VECTOR<FLOAT32>(12345)`
-|`VECTOR<FLOAT32>`
-|Same type, one without dimension encompasses the other.
+| `VECTOR<FLOAT32> \| VECTOR<FLOAT32>(12345)`
+| `VECTOR<FLOAT32>`
+| Same type, the vector without a defined dimension encompasses the other.
 
-|`VECTOR(12345) \| VECTOR<FLOAT32>(12345)`
-|`VECTOR(12345)`
-|Same dimension, one without type encompasses the other.
+| `VECTOR(12345) \| VECTOR<FLOAT32>(12345)`
+| `VECTOR(12345)`
+| Same dimension, the vector without a defined coordinate type encompasses the other.
 
-|`VECTOR<FLOAT32> \| VECTOR<INTEGER64>`
-|`VECTOR<FLOAT32> \| VECTOR<INTEGER64>`
-|Cannot be normalized — coordinate types differ.
+| `VECTOR<FLOAT32> \| VECTOR<INTEGER64>`
+| `VECTOR<FLOAT32> \| VECTOR<INTEGER64>`
+| Cannot be normalized — coordinate types differ.
 
-|`VECTOR(1234) \| VECTOR(12345)`
-|`VECTOR(1234) \| VECTOR(12345)`
-|Cannot be normalized — dimensions differ.
+| `VECTOR(1234) \| VECTOR(12345)`
+| `VECTOR(1234) \| VECTOR(12345)`
+| Cannot be normalized — dimensions differ.
 
-|`VECTOR<FLOAT32>(1234) \| VECTOR<FLOAT64>(1234)`
-|`VECTOR<FLOAT32>(1234) \| VECTOR<FLOAT64>(1234)`
-|Cannot be normalized — types differ, even if dimensions match.
+| `VECTOR<FLOAT32>(1234) \| VECTOR<FLOAT64>(1234)`
+| `VECTOR<FLOAT32>(1234) \| VECTOR<FLOAT64>(1234)`
+| Cannot be normalized — coordinate types differ, even if dimensions match.
 |===
 
 For normalization of other types, see xref:values-and-types/property-structural-constructed.adoc#type-normalization[Property, structural, and constructed values -> Type normalization].
 
 [[ordering-vector-types]]
 == Ordering VECTOR types
 
-The `VECTOR` supertypes are ordered ascendingly from the most general to the more specific forms:
+The `VECTOR` supertypes are ordered in the following ascending order.
 
 * `VECTOR`
 * `VECTOR<TYPE>`
@@ -280,7 +280,7 @@ Within the same coordinate type, `VECTOR` types are ordered by their dimension,
 | `VECTOR<INTEGER16>(1234)`
 | `LIST<INTEGER>`
 | A < B
-| `VECTOR` values are ordered before `LIST` values
+| `VECTOR` values are ordered before `LIST` values.
 
 |===