standardise

Author: JPryce-Aklundh

modules/ROOT/content-nav.adoc

@@ -33,6 +33,7 @@
 ** **Write**
 ** xref:clauses/create.adoc[]
 ** xref:clauses/delete.adoc[]
+** xref::clauses/delete.adoc#delete-all-nodes-and-relationships[DETACH DELETE]
 ** xref:clauses/foreach.adoc[]
 ** xref:clauses/remove.adoc[]
 ** xref:clauses/set.adoc[]

modules/ROOT/pages/clauses/index.adoc

@@ -5,8 +5,8 @@
 
 This section contains information on all the clauses and subclauses in the Cypher query language.
 
-[[reading-clauses]]
-== Reading clauses
+[[read-clauses]]
+== Read clauses
 
 These comprise clauses that read data from the database.
 
@@ -17,7 +17,6 @@ This set is refined and augmented by subsequent parts of the query.
 |===
 | Clause | Description
 
-
 m| xref::clauses/filter.adoc[FILTER]
 | Adds filters to queries.
 label:new[Introduced in Neo4j 2025.06]
@@ -30,8 +29,8 @@ m| xref::clauses/optional-match.adoc[OPTIONAL MATCH]
 
 |===
 
-[[projecting-clauses]]
-== Projecting clauses
+[[projection-clauses]]
+== Projection clauses
 
 These comprise clauses that define which expressions to return in the result set.
 The returned expressions may all be aliased using `AS`.
@@ -58,10 +57,10 @@ m| xref::clauses/with.adoc[WITH ... [AS]]
 
 |===
 
-[[reading-sub-clauses]]
+[[projection-subclauses]]
 == Projection subclauses
 
-These comprise sub-clauses that must operate as part of reading clauses.
+These comprise subclauses that must operate as part of reading clauses.
 
 [options="header"]
 |===
@@ -70,19 +69,19 @@ These comprise sub-clauses that must operate as part of reading clauses.
 m| xref::clauses/where.adoc[WHERE]
 | Adds constraints to the patterns in a `MATCH` or `OPTIONAL MATCH` clause or filters the results of a `WITH` clause.
 
+m| xref::clauses/limit.adoc[LIMIT]
+| Constrains the number of rows in the output.
+
 m| xref::clauses/order-by.adoc[ORDER BY [ASC[ENDING\] \| DESC[ENDING\]\]]
-| A sub-clause following `RETURN` or `WITH`, specifying that the output should be sorted in either ascending (the default) or descending order.
+| A subclause following `RETURN` or `WITH`, specifying that the output should be sorted in either ascending (the default) or descending order.
 
 m| xref::clauses/skip.adoc[SKIP] / xref::clauses/skip.adoc#offset-synonym[`OFFSET`]
 | Defines from which row to start including the rows in the output.
 
-m| xref::clauses/limit.adoc[LIMIT]
-| Constrains the number of rows in the output.
-
 |===
 
-[[writing-clauses]]
-== Writing clauses
+[[write-clauses]]
+== Write clauses
 
 These comprise clauses that write the data to the database.
 
@@ -98,24 +97,24 @@ a|
 Delete nodes, relationships or paths.
 Any node to be deleted must also have all associated relationships explicitly deleted.
 
-m| xref::clauses/delete.adoc[DETACH DELETE]
+m| xref::clauses/delete.adoc#delete-all-nodes-and-relationships[DETACH DELETE]
 a|
 Delete a node or set of nodes.
 All associated relationships will automatically be deleted.
 
+m| xref::clauses/foreach.adoc[FOREACH]
+| Update data within a list, whether components of a path, or the result of aggregation.
+
 m| xref::clauses/set.adoc[SET]
 | Update labels on nodes and properties on nodes and relationships.
 
 m| xref::clauses/remove.adoc[REMOVE]
 | Remove properties and labels from nodes and relationships.
 
-m| xref::clauses/foreach.adoc[FOREACH]
-| Update data within a list, whether components of a path, or the result of aggregation.
-
 |===
 
-[[reading-writing-clauses]]
-== Reading/Writing clauses
+[[reade-write-clauses]]
+== Reade/Write clauses
 
 These comprise clauses that both read data from and write data to the database.
 
@@ -127,23 +126,35 @@ m| xref::clauses/merge.adoc[MERGE]
 | Ensures that a pattern exists in the graph. Either the pattern already exists, or it needs to be created.
 
 m| --- xref::clauses/merge.adoc#query-merge-on-create-on-match[ON CREATE]
-| Used in conjunction with `MERGE`, this write sub-clause specifies the actions to take if the pattern needs to be created.
+| Used in conjunction with `MERGE`, this write subclause specifies the actions to take if the pattern needs to be created.
 
 m| --- xref::clauses/merge.adoc#query-merge-on-create-on-match[ON MATCH]
-| Used in conjunction with `MERGE`, this write sub-clause specifies the actions to take if the pattern already exists.
+| Used in conjunction with `MERGE`, this write subclause specifies the actions to take if the pattern already exists.
 
-m| xref::clauses/call.adoc[CALL ... [YIELD ... ]]
-| Invokes a procedure deployed in the database and return any results.
+|===
 
+[[graph-selection-clauses]]
+== Graph selection clauses
+
+[options="header"]
 |===
+| Clause | Description
 
-[[subquery-clauses]]
-== Subquery clauses
+m| xref::clauses/use.adoc[USE]
+| Determines which graph a query, or query part, is executed against.
+
+|===
+
+[[invocation-clauses]]
+== Invocation clauses
 
 [options="header"]
 |===
 |Clause |Description
 
+m| xref::clauses/call.adoc[CALL ... [YIELD ... ]]
+| Invokes a procedure deployed in the database and return any results.
+
 m| xref::subqueries/call-subquery.adoc[CALL { ... }]
 | Evaluates a subquery, typically used for post-union processing or aggregations.
 
@@ -154,35 +165,52 @@ Typically used when modifying or importing large amounts of data.
 
 |===
 
-[[multiple-graphs-clauses]]
-== Graph selection
+[[importing-clauses]]
+== Importing clauses
 
 [options="header"]
 |===
 | Clause | Description
 
-m| xref::clauses/use.adoc[USE]
-| Determines which graph a query, or query part, is executed against.
+m| xref::clauses/load-csv.adoc[LOAD CSV]
+| Use when importing data from CSV files.
 
 |===
 
-[[importing-clauses]]
-== Importing data
+
+[[schema-clauses]]
+== Schema clauses
 
 [options="header"]
 |===
 | Clause | Description
 
-m| xref::clauses/load-csv.adoc[LOAD CSV]
-| Use when importing data from CSV files.
+m| xref:constraints/managing-constraints.adoc#create-constraint[CREATE CONSTRAINT]
+| Create a property existence, property uniqueness, property type, or key constraint.
 
-m| xref::subqueries/subqueries-in-transactions.adoc[CALL { ... } IN TRANSACTIONS]
-| This clause may be used to prevent an out-of-memory error from occurring when importing large amounts of data using `LOAD CSV`.
+m| xref:constraints/managing-constraints.adoc#list-constraints[SHOW CONSTRAINTS]
+| List the available constraints in a database.
+
+m| xref:constraints/managing-constraints.adoc#drop-constraint[DROP CONSTRAINT]
+| Drop a constraint.
+
+m| xref:indexes/search-performance-indexes/managing-indexes.adoc#create-range-index[CREATE INDEX]
+| Create a range, point, text, lookup, fulltext, or vector index.
+
+m| xref:indexes/search-performance-indexes/managing-indexes.adoc#list-indexes[SHOW INDEXES]
+| List the available indexes in a database.
+
+m| xref:indexes/search-performance-indexes/managing-indexes.adoc#drop-indexes[DROP INDEX]
+| Drop an index.
+
+** xref:indexes/search-performance-indexes/managing-indexes.adoc#list-indexes[SHOW INDEXES]
+** xref:indexes/search-performance-indexes/managing-indexes.adoc#drop-indexes[DROP INDEX]
 
 |===
 
-[[listing-functions-and-procedures]]
+[[metadata-clauses]]
 == Metadata clauses
+
 [options="header"]
 |===
 | Clause | Description
@@ -209,30 +237,6 @@ m| xref::constraints/syntax.adoc[CREATE \| SHOW \| DROP CONSTRAINT]
 | Create, show or drop a constraint.
 |===
 
-[[reading-hints]]
-== Hints
-
-These comprise clauses used to specify planner hints when tuning a query.
-More details regarding the usage of these -- and query tuning in general -- can be found in xref::indexes/search-performance-indexes/index-hints.adoc[Planner hints and the USING keyword].
-
-[options="header"]
-|===
-| Hint | Description
-
-m| xref::indexes/search-performance-indexes/index-hints.adoc#query-using-index-hint[USING INDEX]
-| Index hints are used to specify which index, if any, the planner should use as a starting point.
-
-m| xref::indexes/search-performance-indexes/index-hints.adoc#query-using-index-hint[USING INDEX SEEK]
-| Index seek hint instructs the planner to use an index seek for this clause.
-
-m| xref::indexes/search-performance-indexes/index-hints.adoc#query-using-scan-hint[USING SCAN]
-| Scan hints are used to force the planner to do a label scan (followed by a filtering operation) instead of using an index.
-
-m| xref::indexes/search-performance-indexes/index-hints.adoc#query-using-join-hint[USING JOIN]
-| Join hints are used to enforce a join operation at specified points.
-
-|===
-
 
 [[administration-clauses]]
 == Administration clauses

modules/ROOT/pages/clauses/match.adoc

@@ -321,7 +321,7 @@ RETURN movie.title AS movieTitle, director.name AS director
 [[where-predicates]]
 == MATCH with WHERE predicates
 
-The `MATCH` clause is often paired with a `WHERE` sub-clause, which adds predicates to refine the patterns, making them more specific.
+The `MATCH` clause is often paired with a `WHERE` subclause, which adds predicates to refine the patterns, making them more specific.
 These predicates are part of the pattern itself, not just filters applied after matching.
 Thus, always place the `WHERE` clause with its corresponding `MATCH` clause.
 

modules/ROOT/pages/clauses/order-by.adoc

@@ -1,10 +1,10 @@
-:description: `ORDER BY` is a sub-clause following `RETURN` or `WITH`, and it specifies that the output should be sorted and how.
+:description: `ORDER BY` is a subclause following `RETURN` or `WITH`, and it specifies that the output should be sorted and how.
 
 [[query-order]]
 = ORDER BY
 
 `ORDER BY` specifies how the output of a clause should be sorted.
-It be used as a sub-clause following `RETURN` or `WITH`.
+It be used as a subclause following `RETURN` or `WITH`.
 
 `ORDER BY` relies on comparisons to sort the output, see xref:values-and-types/ordering-equality-comparison.adoc[Ordering and comparison of values].
 You can sort on many different values, e.g. node/relationship properties, the node/relationship ids, or on most expressions.
@@ -233,7 +233,7 @@ If it is an aggregating or `DISTINCT` projection, only the variables available i
 If the projection does not alter the output cardinality (which aggregation and `DISTINCT` do), variables available from before the projecting clause are also available.
 When the projection clause shadows already existing variables, only the new variables are available.
 
-It is also not allowed to use aggregating expressions in the `ORDER BY` sub-clause if they are not also listed in the projecting clause.
+It is also not allowed to use aggregating expressions in the `ORDER BY` subclause if they are not also listed in the projecting clause.
 This rule is to make sure that `ORDER BY` does not change the results, only the order of them.
 
 == ORDER BY and indexes

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

@@ -2244,7 +2244,7 @@ label:updated[]
 ALTER DATABASE ... [WAIT [n [SEC[OND[S]]]]\|NOWAIT]
 ----
 a|
-New sub-clause `WAIT` for `ALTER DATABASE`.
+New subclause `WAIT` for `ALTER DATABASE`.
 This enables adding a waiting clause to specify a time limit in which the command must be completed and returned.
 
 a|
@@ -3607,7 +3607,7 @@ label:new[]
 CREATE DATABASE ... TOPOLOGY n PRIMAR{Y\|IES} [m SECONDAR{Y\|IES}]
 ----
 a|
-New sub-clause for `CREATE DATABASE`, to specify the number of servers hosting a database, when creating a database in cluster environments.
+New subclause for `CREATE DATABASE`, to specify the number of servers hosting a database, when creating a database in cluster environments.
 
 a|
 [[cypher-5_0-a_8]]
@@ -3618,7 +3618,7 @@ label:new[]
 ALTER DATABASE ... SET TOPOLOGY n PRIMAR{Y\|IES} [m SECONDAR{Y\|IES}]
 ----
 a|
-New sub-clause for `ALTER DATABASE`, which allows modifying the number of servers hosting a database in cluster environments.
+New subclause for `ALTER DATABASE`, which allows modifying the number of servers hosting a database in cluster environments.
 
 a|
 [[cypher-5_0-a_9]]

modules/ROOT/pages/functions/aggregating.adoc

@@ -823,7 +823,7 @@ The example below will throw an error since `n.x`, which is not a grouping key,
 RETURN n.x + count(*)
 ----
 
-To sort the result set using aggregating functions, the aggregation must be included in the `ORDER BY` sub-clause following the `RETURN` clause.
+To sort the result set using aggregating functions, the aggregation must be included in the `ORDER BY` subclause following the `RETURN` clause.
 
 [[grouping-key-examples]]
 === Examples