editorial fixes

Author: JPryce-Aklundh

modules/ROOT/pages/clauses/match.adoc

@@ -86,8 +86,8 @@ RETURN movie.title
 |===
 
 
-[[match-label-expressions]]
-=== MATCH using label expressions
+[[match-node-label-expressions]]
+=== MATCH using node label expressions
 
 .Node pattern using the `OR` (`|`) label expression
 [source, cypher]
@@ -128,7 +128,7 @@ The above query uses the xref:functions/list.adoc#functions-labels[`labels()`] a
 2+|Rows: 1
 |===
 
-For a full list of all label expressions supported by Cypher, see xref:patterns/reference.adoc#label-expressions[Patterns -> Label expressions].
+For a list of all label expressions supported by Cypher, see xref:patterns/reference.adoc#label-expressions[Patterns -> Label expressions].
 
 [[find-relationships]]
 == Find relationships
@@ -250,10 +250,10 @@ RETURN actor.name AS actor
 |Rows: 3
 |===
 
-[[match-on-multiple-relationship-types]]
-=== Filter on multiple relationship types
+[[match-relationship-type-expressions]]
+=== MATCH using relationship type expressions
 
-It is possible to match for a pattern containing one out of several relationship types using the `OR` symbol, `|`.
+It is possible to match a pattern containing one of several relationship types using the `OR` symbol, `|`.
 
 .Relationship pattern including either `ACTED_IN` or `DIRECTED` relationship types
 [source, cypher]
@@ -273,7 +273,9 @@ RETURN person.name AS person
 |Rows: 4
 |===
 
-As relationships have exactly one type each, `()-[:A&B]->()` will never match a relationship.
+As relationships can only have exactly one type each, `()-[:A&B]->()` will never match a relationship.
+
+For a list of all relationship type expressions supported by Cypher, see xref:patterns/reference.adoc#label-expressions[Patterns -> Label expressions].
 
 [[multiple-relationships]]
 === Find multiple relationships
@@ -300,7 +302,7 @@ RETURN movie.title AS movieTitle, director.name AS director
 
 The `MATCH` clause is often paired with a `WHERE` sub-clause, 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, the `WHERE` clause should always be placed with its corresponding `MATCH` clause.
+Thus, always place the `WHERE` clause with its corresponding `MATCH` clause.
 
 .Simple `WHERE` predicate
 [source, cypher]
@@ -426,7 +428,7 @@ For more information about how `MATCH` is used to find patterns of varying compl
 
 == Multiple MATCH clauses, the WITH clause, and clause composition
 
-In Cypher, a query’s behavior is defined by its clauses.
+In Cypher, the behavior of a query is defined by its clauses.
 Each clause takes the current graph state and a table of intermediate results, processes them, and passes the updated graph state and results to the next clause.
 The first clause starts with the graph's initial state and an empty table, while the final clause produces the query's result.
 
@@ -453,7 +455,7 @@ RETURN director.name AS director, movie.title AS movieTitle
 
 A variable can be implicitly carried over to the following clause by being referenced in another operation.
 A variable can also be explicitly passed to the following clause using the xref:clauses/with.adoc[`WITH`] clause.
-If a variable is neither implicitly nor explicitly carried over to its following clause, it will be discarded and unavailable for reference later in the query.
+If a variable is neither implicitly nor explicitly carried over to its following clause, it will be discarded and is not available for reference later in the query.
 
 .Using `WITH` and multiple `MATCH` clauses
 [source, cypher]
@@ -465,11 +467,10 @@ LIMIT 1 // <3>
 MATCH (actors)-[:ACTED_IN]->(movies) // <4>
 RETURN actors.name AS actor, movieCount, collect(movies.title) AS movies
 ----
-<1> The `Person` and `Movie` nodes matched in this step are stored in variables.
-which are then passed on to the second row of the query.
-<2> The `movies` variable is here implicitly imported by its occurrence in the `count()` function.
+<1> The `Person` and `Movie` nodes matched in this step are stored in variables, which are then passed on to the second row of the query.
+<2> The `movies` variable is implicitly imported by its occurrence in the `count()` function.
 The `WITH` clause explicitly imports the `actors` variable.
-<3> An xref:clauses/order-by.adoc[`ORDER BY`]  clause orders the results by `movieCount` in descending order, ensuring that the `Person` with the highest number of movies appears at the top, and xref:clauses/limit.adoc[`LIMIT] 1` ensures that all other `Person` nodes are discarded.
+<3> An xref:clauses/order-by.adoc[`ORDER BY`] clause orders the results by `movieCount` in descending order, ensuring that the `Person` with the highest number of movies appears at the top, and xref:clauses/limit.adoc[`LIMIT] 1` ensures that all other `Person` nodes are discarded.
 <4> The second `MATCH` clause finds all `Movie` nodes associated with the `Person` nodes currently bound to the `actors` variable.
 
 [NOTE]