diff --git a/technical-deep-dive/security.md b/technical-deep-dive/security.md
index 0edf24e..e4d753c 100644
--- a/technical-deep-dive/security.md
+++ b/technical-deep-dive/security.md
@@ -14,10 +14,10 @@ See more full details [here](https://dev.thorchain.org/bifrost/how-bifrost-works
 
 ## Outbound Transaction Throttling
 
-To prevent large amounts of funds from leaving the network in an instant, large outbound transactions are throttled from immediately leaving the network. Each block has an outbound value limit (currently 1000 RUNE worth) and each outbound transaction has a maximum time limit that it can be processed. This has three effects:
+To prevent large amounts of funds from leaving the network in an instant, large outbound transactions are throttled from immediately leaving the network. Each block has an outbound value limit controlled by `MinTxOutVolumeThreshold` and each outbound transaction has a maximum time limit that it can be processed. This has three effects:
 
 - Each outbound transaction to compete for the next outbound block, else, it will be processed in the following block, effectively throttling the total outbound capacity of the network. This is independent of [conf-counting](https://docs.thorchain.org/chain-clients/overview#confirmation-counting).
-- Large outbounds to spread across multiple blocks, up to 720 blocks (approx one hour).
+- Large outbounds to spread across multiple blocks. The initial delay is capped by `MaxTxOutOffset`, then the network searches for an available slot up to `TxOutDelayMax` if blocks are full.
 - Ensures one large outbound request of $1,000,000 is handled the same as one million $1 outbound requests.
 
 This feature is controlled by several [Mimir](constants-and-mimir.md#outbound-transactions) values that can be changed by Node Operators as required. [Relevant PR](https://gitlab.com/thorchain/thornode/-/merge_requests/1844).