post-review corrections (non-graph types pages)

Author: JPryce-Aklundh

modules/ROOT/pages/clauses/index.adoc

@@ -266,10 +266,10 @@ m| xref::indexes/search-performance-indexes/index-hints.adoc#query-using-join-hi
 
 |===
 
-[[index-and-constraint-clauses]]
-== Index and constraint clauses
+[[index-and-schema-clauses]]
+== Index and schema clauses
 
-These comprise clauses to create, show, and drop indexes and constraints.
+These comprise clauses to manage indexes, constraints, and graph types.
 
 [options="header"]
 |===
@@ -278,8 +278,15 @@ These comprise clauses to create, show, and drop indexes and constraints.
 m| xref:indexes/syntax.adoc[CREATE \| SHOW  \| DROP INDEX]
 | Create, show or drop an index.
 
-m| xref::schema/syntax.adoc[CREATE \| SHOW \| DROP CONSTRAINT]
+m| xref::schema/syntax.adoc#constraints[CREATE \| SHOW \| DROP CONSTRAINT]
 | Create, show or drop a constraint.
+
+m| xref::schema/syntax.adoc#graph-types[ALTER CURRENT GRAPH TYPE SET \| ADD \| ALTER \|DROP]
+| Set, extend, alter or drop elements in a graph type.
+
+m| xref::schema/syntax.adoc#list-graph-types[SHOW CURRENT GRAPH TYPE]
+| Show the full graph type.
+
 |===
 
 [[administration-clauses]]

modules/ROOT/pages/deprecations-additions-removals-compatibility.adoc

@@ -132,7 +132,8 @@ label:new[]
 [source, cypher, role="noheader"]
 ----
 ALTER CURRENT GRAPH DROP {
-  (:Pet =>)
+  (:Pet =>),
+  CONSTRAINT pet_address
 }
 ----
 
@@ -2415,7 +2416,7 @@ CREATE CONSTRAINT name FOR ()-[r:TYPE]-() REQUIRE r.prop IS :: <PROPERTY TYPE>
 ----
 a|
 
-Extended xref::constraints/managing-constraints.adoc#create-property-type-constraint-union-type[node and relationship property type constraints].
+Extended xref::schema/constraints/create-constraints.adoc#create-property-type-constraint-union-type[node and relationship property type constraints].
 Closed dynamic union types (`type1 \| type2 \| ...`) are now supported, allowing for types such as:
 
 * `INTEGER \| FLOAT`
@@ -2497,7 +2498,7 @@ CREATE CONSTRAINT name FOR ()-[r:TYPE]-() REQUIRE r.prop IS :: <PROPERTY TYPE>
 ----
 a|
 
-Extended xref::constraints/managing-constraints.adoc#type-constraints-allowed-properties[node and relationship property type constraints].
+Extended xref::schema/constraints/create-constraints.adoc#type-constraints-allowed-properties[node and relationship property type constraints].
 The new supported types are:
 
 * `LIST<BOOLEAN NOT NULL>`
@@ -2655,7 +2656,7 @@ CREATE CONSTRAINT name FOR ()-[r:TYPE]-() REQUIRE r.prop IS :: <PROPERTY TYPE>
 ----
 a|
 
-Added xref::constraints/managing-constraints.adoc#create-property-type-constraints[node and relationship property type constraints].
+Added xref::schema/constraints/create-constraints.adoc#create-property-type-constraints[node and relationship property type constraints].
 The available property types are:
 
 * `BOOLEAN`

modules/ROOT/pages/introduction/cypher-neo4j.adoc

@@ -33,12 +33,12 @@ All users have full access rights.
 a|
 xref:schema/graph-types/index.adoc[] and the following individual constraints:
 
-* xref::constraints/managing-constraints.adoc#create-property-existence-constraints[node and relationship property existence constraints]
-* xref::constraints/managing-constraints.adoc#create-property-type-constraints[node and relationship property type constraints]
-* xref::constraints/managing-constraints.adoc#create-property-uniqueness-constraints[node and relationship property uniqueness constraints]
-* xref::constraints/managing-constraints.adoc#create-key-constraints[node and relationship key constraints]
+* xref::schema/constraints/create-constraints.adoc#create-property-existence-constraints[node and relationship property existence constraints]
+* xref::schema/constraints/create-constraints.adoc#create-property-type-constraints[node and relationship property type constraints]
+* xref::schema/constraints/create-constraints.adoc#create-property-uniqueness-constraints[node and relationship property uniqueness constraints]
+* xref::schema/constraints/create-constraints.adoc#create-key-constraints[node and relationship key constraints]
 a|
-Only xref::constraints/managing-constraints.adoc#create-property-uniqueness-constraints[node and relationship property uniqueness constraints].
+Only xref::schema/constraints/create-constraints.adoc#create-property-uniqueness-constraints[node and relationship property uniqueness constraints].
 
 | Runtimes
 a|

modules/ROOT/pages/introduction/cypher-overview.adoc

@@ -35,7 +35,7 @@ However, there are some important differences between the two:
 
 *Cypher is schema-flexible*::
 
-While it is both possible and advised to enforce an xref:schema/index.adoc[open schemas] with Neo4j, Cypher and Neo4j offers a greater degree of schema-flexibility than SQL and a relational database.
+While it is both possible and advised to enforce an xref:schema/index.adoc[open schema] with Neo4j using xref:schema/graph-types/index.adoc[graph types]/xref:schema/constraints/index.adoc[constraints] and xref:indexes/search-performance-indexes/index.adoc[indexes], Cypher and Neo4j offers a greater degree of schema-flexibility than SQL and a relational database.
 More specifically, nodes and relationships in a Neo4j database do not have to have a specific property set to them because other nodes or relationships in the same graph have that property (unless there is an xref:schema/constraints/create-constraints.adoc#create-property-existence-constraints[property existence constraint] created on that specific property).
 This means that users are not required to use a fixed schema to represent data and that they can add new attributes and relationships as their graphs evolve.
 

modules/ROOT/pages/schema/constraints/create-constraints.adoc

@@ -876,7 +876,7 @@ The index makes these checks much faster by enabling direct lookups instead of s
 Cypher will use the indexes with an owning constraint in the same way that it utilizes other search-performance indexes.
 For more information about how indexes impact query performance, see xref:indexes/search-performance-indexes/using-indexes.adoc[].
 
-These indexes are listed in the `owningConstraint` column returned by the xref:indexes/search-performance-indexes/managing-indexes.adoc#list-indexes[`SHOW INDEX`] command, and the `ownedIndex` column returned by the xref:schema/constraints/drop-constraints.adoc[`SHOW CONSTRAINT`] command.
+These indexes are listed in the `owningConstraint` column returned by the xref:indexes/search-performance-indexes/managing-indexes.adoc#list-indexes[`SHOW INDEX`] command, and the `ownedIndex` column returned by the xref:schema/constraints/list-constraints.adoc[`SHOW CONSTRAINT`] command.
 
 .List constraints with backing indexes
 ======

modules/ROOT/pages/schema/constraints/drop-constraints.adoc

@@ -1,9 +1,8 @@
 :description: Information about droppping Neo4j's constraints.
-[[drop-constraint]]
 = Drop constraints
 
 Constraints are dropped using the `DROP CONSTRAINT` command.
-For the full command syntax to drop constraints, see xref:schema/syntax.adoc#drop-constraint[Syntax -> DROP CONSTRAINT].
+For the full command syntax to drop constraints, see xref:schema/syntax.adoc#drop-constraint[Syntax -> Drop constraints].
 The constraints dropped on this page are created on the page xref:schema/constraints/create-constraints.adoc[].
 
 [NOTE]
@@ -73,6 +72,19 @@ Removed 1 constraint.
 
 ======
 
+[NOTE]
+====
+Constraints that are created as part of xref:schema/graph-types/set-graph-types.adoc#node-element-types[node] or xref:schema/graph-types/set-graph-types.adoc#relationship-element-types[relationship element types] in a xref:schema/graph-types/index.adoc[graph type] cannot be dropped with the `DROP CONSTRAINT constraint_name` command.
+This includes the following constraints:
+
+* Property existence and property type constraints on identifying labels or relationship types
+* Node label existence constraints
+* Relationship source and target label constraints
+
+These constraints can only be dropped by dropping the full node or relationship element type.
+For more information, see xref:schema/graph-types/drop-graph-type-elements.adoc#drop-element-types[Drop node and relationship element types]
+====
+
 [[drop-constraint-with-parameter]]
 == Drop a constraint with a parameter
 

modules/ROOT/pages/schema/constraints/index.adoc

@@ -11,8 +11,9 @@ The following constraints are available in Neo4j:
 * xref:schema/constraints/create-constraints.adoc#create-property-type-constraints[Property type constraints]: ensure that a property has the required property type for all nodes with a specific label or for all relationships with a specific type. label:enterprise-edition[]
 * xref:schema/constraints/create-constraints.adoc#create-key-constraints[Key constraints]: ensure that all properties exist and that the combined property values are unique for all nodes with a specific label or all relationships with a specific type.label:enterprise-edition[]
 
-For information about listing and dropping constraints, see:
+For more information index-backed constraints, constraint creation failures and data violation scenarios, as well as listing and dropping constraints, see:
 
+* xref:schema/constraints/create-constraints.adoc[]
 * xref:schema/constraints/list-constraints.adoc[]
 * xref:schema/constraints/drop-constraints.adoc[]
 
@@ -25,5 +26,5 @@ Not all constraint types can be created using this syntax, however, and maintain
 
 *It is, therefore, recommended to define a schema using a graph type, which offers both additional, more sophisticated constraint types and a more holistic and simplified approach for constraining and maintaining the shape of the data in a graph.*
 
-For more information, see xref:schema/graph-types/index.adoc[]
+For more information, see xref:schema/graph-types/index.adoc[].
 ====

modules/ROOT/pages/schema/constraints/list-constraints.adoc

@@ -1,10 +1,9 @@
-
 :description: Information about listing Neo4j's constraints.
 = Show constraints
 
 To list all constraints with the default output columns, use `SHOW CONSTRAINTS`.
 If all columns are required, use `SHOW CONSTRAINTS YIELD *`.
-For the full command syntax to list constraints, see xref:schema/syntax.adoc#list-constraints[Syntax -> SHOW CONSTRAINTS].
+For the full command syntax to list constraints, see xref:schema/syntax.adoc#list-constraints[Syntax -> Show constraints].
 The constraints listed on this page are created on the page xref:schema/constraints/create-constraints.adoc[].
 
 [NOTE]
@@ -18,7 +17,7 @@ For more information, see the following sections of the xref:schema/graph-types/
 ====
 
 One of the output columns from `SHOW CONSTRAINTS` is the name of the constraint.
-This can be used to drop the constraint with the xref::constraints/managing-constraints.adoc#drop-constraint[`DROP CONSTRAINT` command].
+This can be used to drop the constraint with the xref::schema/constraints/drop-constraints.adoc[`DROP CONSTRAINT` command].
 
 [NOTE]
 Listing constraints requires the link:{neo4j-docs-base-uri}/operations-manual/current/authentication-authorization/database-administration/#access-control-database-administration-constraints[`SHOW CONSTRAINTS` privilege].
@@ -256,7 +255,7 @@ YIELD name, type, createStatement
 | STRING
 
 | type
-| The ConstraintType of this constraint (`NODE_PROPERTY_UNIQUENESS`, `RELATIONSHIP_PROPERTY_UNIQUENESS`, `NODE_PROPERTY_EXISTENCE`, `RELATIONSHIP_PROPERTY_EXISTENCE`, `NODE_PROPERTY_TYPE`, `RELATIONSHIP_PROPERTY_TYPE`, `NODE_KEY`, or `RELATIONSHIP_KEY`). label:default-output[]
+| The ConstraintType of this constraint (`NODE_PROPERTY_UNIQUENESS`, `RELATIONSHIP_PROPERTY_UNIQUENESS`, `NODE_PROPERTY_EXISTENCE`, `RELATIONSHIP_PROPERTY_EXISTENCE`, `NODE_PROPERTY_TYPE`, `RELATIONSHIP_PROPERTY_TYPE`, `NODE_LABEL_EXISTENCE`, `RELATIONSHIP_SOURCE_LABEL`, `RELATIONSHIP_TARGET_LABEL`, `NODE_KEY`, or `RELATIONSHIP_KEY`). label:default-output[]
 
 | STRING
 
@@ -270,11 +269,11 @@ The list returned will only include a single value (the name of the constrained
 | LIST<STRING>
 
 | properties
-| The properties of this constraint (`null` for node label existence, relationship source label, and relationship target constraints which do not constrain properties). label:default-output[]
+| The properties of this constraint, or `null` for node label existence, relationship source label, and relationship target constraints which do not constrain properties. label:default-output[]
 | LIST<STRING>
 
 | enforcedLabel
-| The implied labels required by a node element type or the source node and target node labels required by a relationship element type. label:default-output[] label:cypher[Cypher 25 only] label:new[Introduced in Neo4j 2025.xx]
+| The implied labels required by a node label existence constraint or the source node and target node labels required by a relationship source or target label constraint. label:default-output[] label:cypher[Cypher 25 only] label:new[Introduced in Neo4j 2025.xx]
 | STRING
 
 | ownedIndex
@@ -295,7 +294,7 @@ label:default-output[]
 | MAP
 
 | createStatement
-| Statement used to create the constraint (`null` for node label existence, relationship source label, and relationship target constraints, as well as property existence and property constraints defined on an identifying node label or relationship type of a node or relationship element type).
+| Statement used to create the constraint, or `null` for constraints with `dependent` classification.
 | STRING
 
 |===

modules/ROOT/pages/schema/graph-types/set-graph-types.adoc

@@ -289,6 +289,7 @@ The `REQUIRE` keyword can also be used as an alternative syntax to define severa
 
 Property uniqueness and key constraints can also be created using the `CONSTRAINT … FOR … REQUIRE` syntax.
 If so, they can be given a name which can be used in the `ALTER CURRENT GRAPH TYPE DROP` or `DROP CONSTRAINT` commands (if a name is not explicitly given, a name will be assigned).
+The given name must be unique among both indexes and constraints.
 For more information, see xref:schema/graph-types/drop-graph-type-elements.adoc#drop-constraints-on-identifying-and-non-identifying-labels-and-types[Drop constraints on identifying and non-identifying node labels and relationship types].
 
 The following two examples define the same key constraint on an identifying node label.
@@ -469,7 +470,9 @@ It is also possible to include constraints in a graph type on implied node label
 This can be a useful tool if the data model requires certain attributes for nodes or relationships with non-identifying labels or types.
 
 [NOTE]
-Constraints on non-identifying node labels and relationship types can be explicitly named when defined.This can be useful when see xref:schema/graph-types/drop-graph-type-elements.adoc#drop-constraints-on-identifying-and-non-identifying-labels-and-types[Drop constraints on identifying and non-identifying node labels and relationship types] (if a name is not explicitly given, a name will be assigned).
+Constraints on non-identifying node labels and relationship types can be explicitly named when defined.
+This can be useful when see xref:schema/graph-types/drop-graph-type-elements.adoc#drop-constraints-on-identifying-and-non-identifying-labels-and-types[Drop constraints on identifying and non-identifying node labels and relationship types] (if a name is not explicitly given, a name will be assigned).
+The given name must be unique among both indexes and constraints.
 
 Property uniqueness and key constraints can be defined against any node label or relationship type in the graph, regardless of whether they serve as identifying node labels or relationship types (an example of a key constraint defined against the identifying node label of a node element type can be found xref:schema/graph-types/set-graph-types.adoc#naming-property-uniqueness-and-key-constraints[above]).
 

modules/ROOT/pages/schema/index.adoc

@@ -1,4 +1,4 @@
-:description: Information about using a schema in Neo4j.
+:description: Information about using a schema in Neo4j for ensuring data integrity.
 = Schema
 
 Neo4j is a natively schema-free database.