Custom tx timeout can be set to any value (neo4j#2282) (neo4j#2285)

This is true since Neo4j 5.13.

---------

Co-authored-by: Robsdedude <[email protected]>

Author: NataliaIvakina

modules/ROOT/pages/database-internals/transaction-management.adoc

@@ -54,13 +54,12 @@ db.transaction.timeout=10s
 ====
 
 Configuring transaction timeout does not affect transactions executed with custom timeouts (e.g., via the Java API or Neo4j Drivers), as the custom timeout overrides the value set for `db.transaction.timeout`.
-Note that the timeout value can only be overridden to a value smaller than that configured by `db.transaction.timeout`.
-You can set the transaction timeout to any value, even larger than configured by `db.transaction.timeout`.
+Custom timeouts can be set to any value, even larger than configured by `db.transaction.timeout`.
 
 
 == Manage transactions
 
 Transactions can be managed using the Cypher commands `SHOW TRANSACTIONS` and `TERMINATE TRANSACTIONS`.
 The `TERMINATE TRANSACTIONS` command can be combined with multiple `SHOW TRANSACTIONS` and `TERMINATE TRANSACTIONS` commands in the same query.
 
-For more information, see link:{neo4j-docs-base-uri}/cypher-manual/current/clauses/transaction-clauses/[Cypher manual -> Transaction commands].
+For more information, see link:{neo4j-docs-base-uri}/cypher-manual/current/clauses/transaction-clauses/[Cypher manual -> Transaction commands].