fixes and grammar

Author: JPryce-Aklundh

modules/ROOT/pages/clauses/clause-composition.adoc

@@ -133,7 +133,7 @@ A clause can never observe writes made by a later clause.
 
 As of Cypher 25, read and write clauses can be combined in any order.
 That is, a write clause followed by a read clause no longer requires a separating xref:clauses/with.adoc[`WITH`] clause in order for the read clause to observe the changes made by a preceding write clause.
-For example, the following query, in which the changes made by the a write clause (xref:clauses/set.adoc[`SET`]) is observed by a subsequent `MATCH` clause without an intermediate `WITH` clause, is valid using Cypher 25 but not link:https://neo4j.com/docs/cypher-manual/current/clauses/with/#combine-write-and-read-clauses[Cypher 5].
+For example, the following query, in which the changes made by a write clause (xref:clauses/set.adoc[`SET`]) are observed by a subsequent `MATCH` clause without an intermediate `WITH` clause, is valid using Cypher 25 but not link:https://neo4j.com/docs/cypher-manual/current/clauses/with/#combine-write-and-read-clauses[Cypher 5].
 
 
 .Combine write and read clauses without a separating `WITH` clause

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

@@ -200,7 +200,7 @@ RETURN count(p) AS count
 ----
 
 | Queries no longer require xref:clauses/with.adoc[`WITH`] to transition between reading and writing operations.
-For more information, see xref:clauses/clause-composition.adoc#cypher-clause-composition-rw-queries[Clause composition -> Red-write queries]
+For more information, see xref:clauses/clause-composition.adoc#cypher-clause-composition-rw-queries[Clause composition -> Read-write queries].
 
 a|
 label:functionality[]