format for 5

Author: JPryce-Aklundh

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

@@ -837,7 +837,7 @@ Use the xref:subqueries/subqueries-in-transactions.adoc#status-report[status rep
 When a write transaction occurs, Neo4j takes locks to preserve data consistency while updating.
 For example, when creating or deleting a relationship, a write lock is taken on both the specific relationship and its connected nodes.
 
-A deadlock happens when two transactions are blocked by each other because they are attempting to concurrently modify a node or a relationship that is locked by the other transaction (for more information about locks and deadlocks in Neo4j, see link:{neo4j-docs-base-uri}/operations-manual/current/database-internals/concurrent-data-access/#_locks[Operations Manual -> Concurrent data access].
+A deadlock happens when two transactions are blocked by each other because they are attempting to concurrently modify a node or a relationship that is locked by the other transaction (for more information about locks and deadlocks in Neo4j, see link:{neo4j-docs-base-uri}/operations-manual/current/database-internals/concurrent-data-access/#_locks[Operations Manual -> Concurrent data access]).
 
 A deadlock may occur when using `CALL { ... } IN CONCURRENT TRANSACTIONS` if the transactions for two or more batches try to take the same locks in an order that results in a circular dependency between them.
 If so, the impacted transactions are always rolled back, and an error is thrown unless the query is appended with one of the following error options:
@@ -1057,9 +1057,7 @@ The result shows that all transactions are now successful:
 
 .Click to see an example of failed transactions being retried without using `ON ERROR RETRY`
 [%collapsible]
-=====
-While failed transactions may be more efficiently retried using a link:{neo4j-docs-base-uri}/create-applications[driver], below is an example how failed transactions can be retried within the same Cypher query without using `ON ERROR RETRY`:
-
+====
 
 .Query retrying failed transactions
 [source, cypher]
@@ -1078,7 +1076,7 @@ CALL (row) {
    MERGE (m)-[r:RELEASED_IN]->(y)
 } IN 2 CONCURRENT TRANSACTIONS OF 10 ROWS ON ERROR FAIL
 ----
-=====
+====
 =====
 
 [[restrictions]]