diff --git a/_includes/devdoc/guide_dash_features.md b/_includes/devdoc/guide_dash_features.md
index eec5cd6b..9ffa7204 100644
--- a/_includes/devdoc/guide_dash_features.md
+++ b/_includes/devdoc/guide_dash_features.md
@@ -182,9 +182,9 @@ Dash's ChainLock feature leverages [LLMQ Signing Requests/Sessions](#llmq-signin
 to reduce uncertainty when receiving funds and remove the possibility of 51%
 mining attacks.
 
-For each block, an LLMQ of a few hundred masternodes is selected and each
+For each block, an LLMQ of a few hundred masternodes (300-400) is selected and each
 participating member signs the first block that it sees extending the active
-chain at the current height. If enough members (e.g. >= 60%) see the same block
+chain at the current height. If enough members (at least 240) see the same block
 as the first block, they will be able to create a `clsig` message and propagate
 it to all nodes in the network.
 
@@ -193,6 +193,11 @@ any descendants) at the same height that do not match the block specified in the
 `clsig` message. This makes the decision on the active chain quick, easy and
 unambiguous. It also makes reorganizations below this block impossible.
 
+When LLMQ-based InstantSend is enabled, a ChainLock is only attempted once all
+transactions in the block are locked via InstantSend. If a block contains
+unlocked transactions, retroactive InstantSend locks are established prior to
+a ChainLock.
+
 Please read [DIP8 ChainLocks](https://github.com/dashpay/dips/blob/master/dip-0008.md)
 for additional details.