review suggestions

Author: rsill-neo4j

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

@@ -85,8 +85,6 @@ NEXT
 In the following example, `NEXT` passes the variable `customer` to the second query:
 
 .Passing a variable to another query via `NEXT`
-====
-.Query
 [source, cypher]
 ----
 MATCH (c:Customer)-[:BUYS]->(:Product {name: 'Chocolate'})
@@ -108,12 +106,9 @@ RETURN customer.firstName AS chocolateCustomer
 
 1+d|Rows: 3
 |===
-====
 
 
 .Passing multiple variables to another query via `NEXT`
-====
-.Query
 [source, cypher]
 ----
 MATCH (c:Customer)-[:BUYS]->(p:Product {name: 'Chocolate'})
@@ -137,25 +132,23 @@ RETURN customer.firstName AS chocolateCustomer,
 
 2+d|Rows: 3
 |===
-====
 
 [NOTE]
 ====
 When followed by a `NEXT` clause, expressions in a `RETURN` clause must either be variables that have been introduced before or they must be aliased with `AS`.
 ====
 
+Variables which are local to a query and which are not explicitly returned are not accessible by subsequent queries in the context of `NEXT`. This allows you to control variable scope similarly to what you can do with `WITH`, see xref:clauses/with.adoc#variable-scope[Control variables in scope].
+
 
 == Interactions with `CALL` subqueries
 
 `NEXT` can serve as a more readable alternative to `CALL` subqueries.
 
-[[call-subquery-rewrite]]
-.Rewriting a query with a `CALL` subquery
+[.tabbed-example]
 ====
-[cols="1,1"]
-|===
-a|
-.`CALL` subquery
+[.include-with-CALL-subquery]
+======
 [source, cypher]
 ----
 MATCH (p:Product)
@@ -165,8 +158,9 @@ CALL (p) {
 }
 RETURN p.name as product, customers
 ----
-a|
-.`NEXT`
+======
+[.include-with-NEXT]
+======
 [source, cypher]
 ----
 MATCH (p:Product)
@@ -181,7 +175,8 @@ NEXT
 
 RETURN p.name as product, customers
 ----
-|===
+======
+====
 
 .Result
 [role="queryresult",options="header,footer",cols="2*<m"]
@@ -195,12 +190,10 @@ RETURN p.name as product, customers
 | "Coffee"     | ["Mateo", "Hannah", "Niko"]
 2+d|Rows: 5
 |===
-====
 
 Even though the query which uses `NEXT` has more lines, it is divided into three segments which are easy to read.
 It also avoids the parentheses and indentation of the `CALL` subquery.
 
-Variables which are local to a query and which are not explicitly returned are not accessible by subsequent queries in the context of `NEXT`. This allows you to control variable scope similarly to what you can do with `WITH`, see xref:clauses/with.adoc#variable-scope[Control variables in scope].
 [NOTE]
 ====
 `NEXT` cannot be used inside a `CALL` subquery that uses the (deprecated) xref:subqueries/call-subquery.adoc#importing-with[importing `WITH`] syntax.
@@ -209,10 +202,7 @@ Variables which are local to a query and which are not explicitly returned are n
 
 == Interactions with conditional queries
 
-[[next-and-conditional]]
-. Conditional queries in `NEXT`
-====
-.Query
+.Conditional queries in `NEXT`
 [source, cypher]
 ----
 MATCH (c:Customer)-[:BUYS]->(:Product)<-[:SUPPLIES]-(s:Supplier)
@@ -252,7 +242,6 @@ ELSE
 
 2+d|Rows: 7
 |===
-====
 
 In the query above, customers are assigned personality types based on the products they purchased.
 The second query is a conditional query that returns different base personality types for different suppliers the customers purchased from.
@@ -262,10 +251,7 @@ Finally, the fourth query is another conditional query which subsumes multiple b
 
 == Interactions with `UNION` queries
 
-[[next-and-union]]
 .`NEXT` in a query using `UNION`
-====
-.Query
 [source, cypher]
 ----
 MATCH (c:Customer)-[:BUYS]->(:Product{name: "Laptop"})
@@ -294,7 +280,6 @@ RETURN customer AS customer, count(customer) as numberOfProducts
 
 2+d|Rows: 6
 |===
-====
 
 In this example, the list of customer names from the first query has a duplicate entry for "Mateo" who bought both a laptop and coffee.
 The use of `UNION ALL` added him to the list twice.