polish

Author: stefano-ottolenghi

modules/ROOT/pages/constraints/managing-constraints.adoc

@@ -344,7 +344,7 @@ Added 1 constraint.
 
 ======
 
-.Create `VECTOR` property type constraints label:cypher[Cypher 25 only] label:new[Introduced in Neo4j 2025.xx]
+.Create `VECTOR` property type constraints label:cypher[Cypher 25 only] label:new[Introduced in Neo4j 2025.10]
 ======
 
 It is necessary to specify both the dimension and the coordinate type of any constrained `VECTOR` properties.
@@ -436,7 +436,7 @@ The allowed property types for property type constraints are:
 * `ZONED DATETIME`
 * `DURATION`
 * `POINT`
-* `VECTOR<TYPE>(DIMENSION)` label:cypher[Cypher 25 only] label:new[Introduced in Neo4j 2025.xx]
+* `VECTOR<TYPE>(DIMENSION)` label:cypher[Cypher 25 only] label:new[Introduced in Neo4j 2025.10]
 * `LIST<BOOLEAN NOT NULL>`
 * `LIST<STRING NOT NULL>`
 * `LIST<INTEGER NOT NULL>`
@@ -451,8 +451,7 @@ The allowed property types for property type constraints are:
 * Any closed dynamic union of the above types, e.g. `INTEGER | FLOAT | STRING`.
 
 [NOTE]
-A property type constraint cannot be created for `LIST<VECTOR<TYPE>(DIMENSION) NOT NULL>`.
-This is because it is not possible to store lists of xref:values-and-types/vector.adoc[`VECTOR`] values.
+Because storing lists of xref:values-and-types/vector.adoc[`VECTOR`] values is not supported, property type constraints cannot be created for `LIST<VECTOR<TYPE>(DIMENSION) NOT NULL>`.
 
 For a complete reference describing all types available in Cypher, see the section on xref::values-and-types/property-structural-constructed.adoc#types-synonyms[types and their synonyms].
 
@@ -737,7 +736,7 @@ Additionally, some constraints cannot coexist and attempting to create them toge
 This includes:
 
 * Property type constraints on the same label/relationship type and property but with different property types.
-This includes `VECTOR` types with differing dimensions or coordinate types.
+This includes `VECTOR` types with different dimensions or coordinate types.
 * Property uniqueness and key constraints on the same label/relationship type and property combination.
 
 However, some constraint types are allowed on the same label/relationship type and property combination.
@@ -1096,7 +1095,7 @@ A constraint cannot be created until the index has been dropped.
 | *Property uniqueness constraint*
 |
 ^| &#x274C;
-| 
+|
 
 | *Property existence constraint*
 ^| &#x274C;
@@ -1263,7 +1262,7 @@ Node(9) with label `Movie` required the property `title` to be of type `STRING`,
 | *Property uniqueness constraint*
 |
 ^| &#x274C;
-| 
+|
 
 | *Property existence constraint*
 ^| &#x274C;
@@ -1365,7 +1364,7 @@ RETURN wrote
 | Query
 
 | Node property uniqueness constraint
-a| 
+a|
 [source]
 ----
 MATCH (n1:Label), (n2:Label)
@@ -1374,7 +1373,7 @@ RETURN n1, n2
 ----
 
 | Relationship property uniqueness constraint
-a| 
+a|
 [source]
 ----
 MATCH ()-[r1:REL_TYPE]->(), ()-[r2:REL_TYPE]->()
@@ -1383,7 +1382,7 @@ RETURN r1, r2
 ----
 
 | Node property existence constraint
-a| 
+a|
 [source]
 ----
 MATCH (n:Label)
@@ -1392,7 +1391,7 @@ RETURN n
 ----
 
 | Relationship property existence constraint
-a| 
+a|
 [source]
 ----
 MATCH ()-[r:REL_TYPE]->()
@@ -1401,7 +1400,7 @@ RETURN r
 ----
 
 | Node property type constraint
-a| 
+a|
 [source]
 ----
 MATCH (n:Label)
@@ -1410,7 +1409,7 @@ RETURN n
 ----
 
 | Relationship property type constraint
-a| 
+a|
 [source]
 ----
 MATCH ()-[r:REL_TYPE]->()
@@ -1419,7 +1418,7 @@ RETURN r
 ----
 
 | Node key constraint
-a| 
+a|
 [source]
 ----
 MATCH (n1:Label), (n2:Label)
@@ -1433,7 +1432,7 @@ RETURN n AS node, 'non-existing' AS reason
 ----
 
 | Relationship key constraint
-a| 
+a|
 [source]
 ----
 MATCH ()-[r1:REL_TYPE]->(), ()-[r2:REL_TYPE]->()
@@ -1701,7 +1700,7 @@ label:default-output[]
 == DROP CONSTRAINT
 
 Constraints are dropped using the `DROP CONSTRAINT` command.
-It is possible to drop a constraint that was created in a later Cypher version than the one currently in use.
+It is possible to drop constraints created in a different Cypher version than the one in use.
 For example, although `VECTOR` property type constraints were added in Cypher 25, such constraints can still be dropped using Cypher 5.
 
 For the full command syntax to drop constraints, see xref:constraints/syntax.adoc#drop-constraint[Syntax -> DROP CONSTRAINT].
@@ -1791,4 +1790,4 @@ DROP CONSTRAINT missing_constraint_name IF EXISTS
 `DROP CONSTRAINT missing_constraint_name IF EXISTS` has no effect. `missing_constraint_name` does not exist.
 ----
 
-======
+======

modules/ROOT/pages/constraints/syntax.adoc

@@ -19,7 +19,7 @@ If a name is not explicitly given, a unique name will be auto-generated.
 [NOTE]
 Creating a constraint requires the link:{neo4j-docs-base-uri}/operations-manual/current/authentication-authorization/database-administration/#access-control-database-administration-constraints[`CREATE CONSTRAINT` privilege].
 
-The `CREATE CONSTRAINT` command is optionally idempotent. 
+The `CREATE CONSTRAINT` command is optionally idempotent.
 This means its default behavior is to throw an error if an attempt is made to create the same constraint twice.
 With the `IF NOT EXISTS` flag, no error is thrown and nothing happens should a constraint with the same name or same schema and constraint type already exist.
 It may still throw an error if conflicting data, indexes, or constraints exist.
@@ -122,7 +122,7 @@ Where `<TYPE>` is one of the following property types:
 * `ZONED DATETIME`
 * `DURATION`
 * `POINT`
-* `VECTOR<TYPE>(DIMENSION)` label:cypher[Cypher 25 only] label:new[Introduced in Neo4j 2025.xx]
+* `VECTOR<TYPE>(DIMENSION)` label:cypher[Cypher 25 only] label:new[Introduced in Neo4j 2025.10]
 * `LIST<BOOLEAN NOT NULL>`
 * `LIST<STRING NOT NULL>`
 * `LIST<INTEGER NOT NULL>`
@@ -137,8 +137,7 @@ Where `<TYPE>` is one of the following property types:
 * Any closed dynamic union of the above types, e.g. `INTEGER | FLOAT | STRING`.
 
 [NOTE]
-A property type constraint cannot be created for `LIST<VECTOR<TYPE>(DIMENSION) NOT NULL>`.
-This is because it is not possible to store lists of `VECTOR` values.
+Because storing lists of xref:values-and-types/vector.adoc[`VECTOR`] values is not supported, property type constraints cannot be created for `LIST<VECTOR<TYPE>(DIMENSION) NOT NULL>`.
 Additionally, `VECTOR` property type constraints must be created with a specific dimension and coordinate value, where the dimension must be greater than `0` and less or equal to `4096`.
 For more information, see xref:values-and-types/vector.adoc[Values and types -> Vectors].
 
@@ -317,4 +316,4 @@ This means its default behavior is to throw an error if an attempt is made to dr
 With the `IF EXISTS` flag, no error is thrown and nothing happens should the constraint not exist.
 Instead, an informational notification is returned detailing that the constraint does not exist.
 
-For examples on how to drop constraints, see  xref:constraints/managing-constraints.adoc#drop-constraint[Create, show, and drop constraints -> DROP CONSTRAINT].
+For examples on how to drop constraints, see  xref:constraints/managing-constraints.adoc#drop-constraint[Create, show, and drop constraints -> DROP CONSTRAINT].