Update modules/ROOT/pages/subqueries/subqueries-in-transactions.adoc

Co-authored-by: Jens Pryce-Åklundh <[email protected]>

Author: henriknyman

modules/ROOT/pages/subqueries/subqueries-in-transactions.adoc

@@ -1069,8 +1069,8 @@ The result shows that all transactions are now successful:
 
 Deadlock resolution and transaction retries are time-consuming, making deadlock avoidance a preferred strategy.
 This can be achieved by dividing a task into two distinct subqueries: a data-independent subquery run in parallel with maximum concurrency, and a data-dependent subquery executed serially (i.e.  one transaction at a time) to avoid deadlocks.
-In this example nodes and properties are created in a concurrent subquery, while the relationships are then created in a serial subquery.
-This way we can benefit from the performance of concurrent transactions while avoiding the deadlocks that slow down the overall performance.
+In the below example, nodes and properties are created in a concurrent subquery, while the relationships connecting those nodes are created in a serial subquery.
+This method benefits from the performance of concurrent transactions while avoiding deadlocks.
 
 .Query splitting up the transactional subquery in a data-independent concurrent subquery followed by a data-dependent serial subquery to avoid deadlocks
 // tag::subqueries_in_transactions_deadlock_example_2[]