diff --git a/content/concepts/consensus-network/transaction-queue.md b/content/concepts/consensus-network/transaction-queue.md
index 8a8a071d4b..3c77a65741 100644
--- a/content/concepts/consensus-network/transaction-queue.md
+++ b/content/concepts/consensus-network/transaction-queue.md
@@ -30,7 +30,10 @@ The `rippled` server uses a variety of heuristics to estimate which transactions
 
 * Transactions must be properly-formed and [authorized](transaction-basics.html#authorizing-transactions) with valid signatures.
 * Transactions with an `AccountTxnID` field cannot be queued.
-* A single sending address can have at most 10 transactions queued at the same time. In order for a transaction to be queued, the sender must have enough XRP to pay all the XRP costs of all the sender's queued transactions including both the `Fee` fields and the sum of the XRP that each transaction could send. [New in: rippled 0.32.0][]
+* A single sending address can have at most 10 transactions queued at the same time. In order for a transaction to be queued, the sender must have enough XRP to pay all the XRP costs of all the sender's queued transactions, including all of the following:
+    - The `Fee` fields of all queued transactions.
+    - The sum amount the XRP that each transaction could send.
+    - The amount of XRP the account must keep in [reserve](reserves.html). [Updated in: rippled 1.2.0][New in: rippled 1.2.0]
 * If a transaction affects how the sending address authorizes transactions, no other transactions from the same address can be queued behind it. [New in: rippled 0.32.0][]
 * If a transaction includes a `LastLedgerSequence` field, the value of that field must be at least **the current ledger index + 2**.