f! docs

Author: wpaulino

lightning/src/util/events.rs

@@ -397,8 +397,9 @@ pub enum BumpTransactionEvent {
 		/// commitment transaction confirms.
 		pending_htlcs: Vec<HTLCOutputInCommitment>,
 	},
-	/// Indicates that a channel featuring anchor outputs has HTLC(s) that need to be resolved
-	/// onchain. With the zero-HTLC-transaction-fee variant of anchor outputs, the pre-signed HTLC
+	/// Indicates that a channel featuring anchor outputs has unilaterally closed on-chain by a
+	/// holder commitment transaction and its HTLC(s) need to be resolved on-chain. With the
+	/// zero-HTLC-transaction-fee variant of anchor outputs, the pre-signed HTLC
 	/// transactions have a zero fee, thus requiring additional inputs and/or outputs to be attached
 	/// for a timely confirmation within the chain. These additional inputs and/or outputs must be
 	/// appended to the resulting HTLC transaction to meet the target feerate. Failure to meet the
@@ -419,8 +420,9 @@ pub enum BumpTransactionEvent {
 	/// the [Replace-By-Fee
 	/// rules](https://github.com/bitcoin/bitcoin/blob/master/doc/policy/mempool-replacements.md)
 	/// for fee bumps to be accepted into the mempool, and eventually the chain. As the frequency of
-	/// these events is not user-controlled, users may ignore/drop the event if they are no longer
-	/// able to commit external confirmed funds to the HTLC transaction.
+	/// these events is not user-controlled, users may ignore/drop the event if either they are no
+	/// longer able to commit external confirmed funds to the HTLC transaction or the fee committed
+	/// to the HTLC transaction is greater in value than the HTLCs being claimed.
 	///
 	/// [`InMemorySigner`]: crate::chain::keysinterface::InMemorySigner
 	/// [`KeysManager::derive_channel_keys`]: crate::chain::keysinterface::KeysManager::derive_channel_keys