clarified the additions entry

Author: rsill-neo4j

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

@@ -37,17 +37,26 @@ label:functionality[]
 label:updated[]
 [source, cypher]
 ----
-MATCH (c:Customer)-[:BUYS]->(p:Product)
-RETURN c AS customer, p AS product
-
-NEXT
-
-RETURN product.name AS product,
-       COUNT(customer) AS numberOfCustomers
+MATCH (p:Product) WHERE p.name <> "Coffee"
+CALL (p) {
+    MATCH (p)<-[:BUYS]-(c:Customer)-[:BUYS]->(otherProduct)
+    RETURN c, otherProduct
+    NEXT
+    RETURN count(DISTINCT c) AS customers, 0 AS customersAlsoBuyingCoffee
+    UNION
+    FILTER otherProduct.name = "Coffee"
+    RETURN 0 as customers, count(DISTINCT c) AS customersAlsoBuyingCoffee
+    NEXT
+    RETURN max(customers) AS customers, max(customersAlsoBuyingCoffee) AS customersAlsoBuyingCoffee
+}
+RETURN p.name AS product,
+       round(toFloat(customersAlsoBuyingCoffee) * 100 / customers, 1) AS percentageOfCustomersAlsoBuyingCoffee
+  ORDER BY product
 ----
 
-| `NEXT` now correctly supports aggregations, updating queries and `DISTINCT` in the context `UNION`, `USE` and wrapped in braces.
-In Neo4j 2025.06 and Cypher 25, such queries yielded incorrect results while they created an error in Neo4j 2025.07 and Cypher 25. 
+| `NEXT` now correctly supports aggregations in the context of `UNION` and `CALL`.
+In Neo4j 2025.06, such queries yielded incorrect results while they created an error in Neo4j 2025.07.
+For more information on `NEXT`, see xref:queries/composed-queries/sequential-queries.adoc[].
 
 a|
 label:functionality[]

modules/ROOT/pages/queries/composed-queries/sequential-queries.adoc

@@ -359,7 +359,7 @@ RETURN p.name AS product,
 |===
 
 This example computes the percentage of customers that also bought coffee for each non-coffee product.
-For each product `p` the subquery finds all pairs of a customer `c` of product `p` and another product `otherProduct` that customer has also bought.
+For each product `p` the subquery finds all pairs of a customer `c` of product `p` and another product `otherProduct` that the customer has also bought.
 The first `NEXT` passes these pairs as a whole into a `UNION`, so that the query can:
 
 . count all customers in the first branch of the union.
@@ -368,6 +368,12 @@ The first `NEXT` passes these pairs as a whole into a `UNION`, so that the query
 The `UNION` produces two rows -- one from each branch.
 The second `NEXT` passes these two rows as a whole to a query that aggregates them into a single row, which is the result of the `CALL` subquery.
 
+[NOTE]
+====
+The example above produced a different result in Neo4j 2025.06 and an error in 2025.07.
+Neo4j 2025.08 correctly supports aggregations in the context of `UNION` and `CALL`.
+====
+
 [NOTE]
 ====
 `NEXT` cannot be used inside a `CALL` subquery that uses the (deprecated) xref:subqueries/call-subquery.adoc#importing-with[importing `WITH`] syntax.