fixes

Author: JPryce-Aklundh

modules/ROOT/pages/clauses/load-csv.adoc

@@ -708,8 +708,7 @@ person_tmdbId,bio,born,bornIn,died,person_imdbId,name,person_poster,person_url
 ----
 
 [NOTE]
-The query below uses a xref:subqueries/call-subquery.adoc#variable-scope-clause[variable scope clause] (introduced in Neo4j 5.23) to import variables into the `CALL` subquery.
-If you are using an older version of Neo4j, use an xref:subqueries/call-subquery.adoc#importing-with[importing `WITH` clause] instead.
+The below query uses a xref:subqueries/call-subquery.adoc#variable-scope-clause[variable scope clause] to import variables into the `CALL` subquery.
 
 .Query
 // tag::clauses_load_csv_transactions[]

modules/ROOT/pages/clauses/where.adoc

@@ -69,7 +69,6 @@ MATCH (n:Person)
 WHERE n.age < 35
 RETURN n.name AS name, n.age AS age
 ----
-// end::clauses_where_boolean_operations[]
 
 .Result
 [role="queryresult",options="header,footer",cols="2*<m"]
@@ -82,6 +81,7 @@ RETURN n.name AS name, n.age AS age
 |===
 
 .Filter on a relationship property
+// tag::clauses_where_relationship_property[]
 [source, cypher]
 ----
 MATCH (:Person {name:'Andy'})-[k:KNOWS]->(f)

modules/ROOT/pages/clauses/with.adoc

@@ -61,7 +61,6 @@ CREATE (techCorp:Supplier {name: 'TechCorp', email: '[email protected]'}),
        (foodies)-[:SUPPLIES]->(chocolate),
        (foodies)-[:SUPPLIES]->(coffee)
 ----
-// end::clauses_with_variables[]
 
 [[create-new-variables]]
 == Create new variables
@@ -89,14 +88,14 @@ In the below example, the `WITH` clause binds all matched `Customer` nodes to a
 The bound nodes are `MAP` values which can then be referenced from the new variable.
 
 .Create a new variable bound to matched nodes
-// tag::clauses_with_wildcard[]
+// tag::clauses_with_new_variable[]
 [source, cypher]
 ----
 MATCH (c:Customer)-[:BUYS]->(:Product {name: 'Chocolate'})
 WITH c AS customer
 RETURN customer.firstName AS chocolateCustomer
 ----
-// end::clauses_with_wildcard[]
+// end::clauses_with_new_variable[]
 
 .Result
 [role="queryresult",options="header,footer",cols="1*<m"]
@@ -131,7 +130,6 @@ WITH c.name AS chocolateCustomers
 RETURN chocolateCustomers,
        p.price AS chocolatePrice
 ----
-// end::clauses_with_wildcard[]
 
 .Error message
 [source, error]
@@ -140,6 +138,7 @@ Variable `p` not defined
 ----
 
 .Retain all variables with `WITH *`
+// tag::clauses_with_all_variables[]
 [source, cypher]
 ----
 MATCH (supplier:Supplier)-[r]->(product:Product)
@@ -148,6 +147,7 @@ RETURN supplier.name AS company,
        type(r) AS relType,
        product.name AS product
 ----
+// end::clauses_with_all_variables[]
 
 .Result
 [role="queryresult",options="header,footer",cols="3*<m"]
@@ -169,6 +169,7 @@ More specifically, a variable imported into a `CALL` subquery will be available
 In the below example, the `x` variable is imported to the inside scope of a `CALL` subquery, and is successfully referenced  by the `RETURN` clause even though the preceding `WITH` neglects to list it.
 
 .Variables cannot be de-scoped in the inner scope of a subquery
+// tag::clauses_with_subquery[]
 [source, cypher]
 ----
 WITH 11 AS x
@@ -179,6 +180,7 @@ CALL (x) {
 }
 RETURN x, a
 ----
+// end::clauses_with_subquery[]
 
 .Result
 [role="queryresult",options="header,footer",cols="2*<m"]
@@ -200,6 +202,7 @@ For more information, see xref:subqueries/call-subquery.adoc#import-variables[`C
 In the below query, the value of the xref:expressions/string-operators.adoc[`STRING` concatenation] expression is bound to a new variable `customerFullName`, and the value from the expression `chocolate.price * (1 - customer.discount)` is bound to `chocolateNetPrice`, both of which are then available in the `RETURN` clause.
 
 .Bind values to variables
+// tag::clauses_with_bind_values[]
 [source, cypher]
 ----
 MATCH (customer:Customer)-[:BUYS]->(chocolate:Product {name: 'Chocolate'})
@@ -208,6 +211,7 @@ WITH customer.firstName || ' ' || customer.lastName AS customerFullName,
 RETURN customerFullName,
        chocolateNetPrice
 ----
+// end::clauses_with_bind_values[]
 
 .Result
 [role="queryresult",options="header,footer",cols="2*<m"]
@@ -224,6 +228,7 @@ RETURN customerFullName,
 Because `WITH` can be used to assign variables to the values of expressions, it can be used to chain expressions.
 
 .Chain expressions using `WITH`
+// tag::clauses_with_chain_expressions[]
 [source, cypher]
 ----
 MATCH (p:Product)
@@ -240,6 +245,7 @@ RETURN p.name AS product,
        discountCategory
 ORDER BY price
 ----
+// end::clauses_with_chain_expressions[]
 
 .Result
 [role="queryresult",options="header,footer", cols="4*<m"]
@@ -267,6 +273,7 @@ In this example, the xref:functions/aggregating.adoc#functions-sum[`sum()`] func
 The xref:functions/aggregating.adoc#functions-collect[`collect()`] function is used to collect each product into  `LIST` values bound to the `productsBought` variable.
 
 .`WITH` performing aggregations
+// tag::clauses_with_aggregations[]
 [source, cypher]
 ----
 MATCH (c:Customer)-[:BUYS]->(p:Product)
@@ -278,6 +285,8 @@ RETURN customer,
        productsBought
 ORDER BY totalSpent DESC
 ----
+// end::clauses_with_aggregations[]
+
 
 .Result
 [role="queryresult",options="header,footer", cols="3*<m"]
@@ -303,13 +312,15 @@ ORDER BY totalSpent DESC
 In the below query, `WITH DISTINCT` is used to remove any duplicate `discount` property values from `Customer` nodes.
 
 .`WITH DISTINCT` to remove duplicate values
+// tag::clauses_with_remove_duplicates[]
 [source, cypher]
 ----
 MATCH (c:Customer)
 WITH DISTINCT c.discount AS discountRates
 RETURN discountRates
 ORDER BY discountRates
 ----
+// end::clauses_with_remove_duplicates[]
 
 .Result
 [role="queryresult",options="header,footer", cols="1*<m"]
@@ -395,6 +406,7 @@ In the next example, `LIMIT` is used to only retain the top 3 customers with the
 Then, the xref:clauses/set.adoc[`SET`] assigns a new property (`topSpender = true`) to those customers who have spent the most.
 
 .Limit results with `LIMIT`
+// tag::clauses_with_ordering_pagination[]
 [source, cypher]
 ----
 MATCH (c:Customer)-[:BUYS]->(p:Product)
@@ -407,6 +419,7 @@ RETURN c.firstName AS customer,
        totalSpent,
        c.topSpender AS topSpender
 ----
+// end::clauses_with_ordering_pagination[]
 
 [role="queryresult",options="header,footer", cols="3*<m"]
 |===
@@ -509,6 +522,7 @@ In the below query, `WITH` and `WHERE` are used to filter out any `Supplier` nod
 Note the use of `DISTINCT` inside `collect()` to remove any duplicate `Customer` nodes.
 
 .Filter property values using `WITH` and `WHERE`
+// tag::clauses_with_filtering[]
 [source, cypher]
 ----
 MATCH (s:Supplier)-[:SUPPLIES]->(p:Product)<-[:BUYS]-(c:Customer)
@@ -520,6 +534,7 @@ RETURN s.name AS supplier,
        totalSales,
        uniqueCustomers
 ----
+// end::clauses_with_filtering[]
 
 [role="queryresult",options="header,footer", cols="3*<m"]
 |===