f three comments better, three clearer comments best

Author: TheBlueMatt

lightning/src/ln/channelmanager.rs

@@ -1297,9 +1297,9 @@ pub(super) struct PeerState<SP: Deref> where SP::Target: SignerProvider {
 	/// Note that any pending [`BackgroundEvent::MonitorUpdateRegeneratedOnStartup`]s which are
 	/// sitting in [`ChannelManager::pending_background_events`] will *also* be tracked here. This
 	/// avoids a race condition during [`ChannelManager::pending_background_events`] processing
-	/// where we complete one [`ChannelMonitorUpdate`] (but there are more pending) but we conclude
-	/// all pending [`ChannelMonitorUpdate`]s have completed and its safe to run post-completion
-	/// actions.
+	/// where we complete one [`ChannelMonitorUpdate`] (but there are more pending as background
+	/// events) but we conclude all pending [`ChannelMonitorUpdate`]s have completed and its safe
+	/// to run post-completion actions.
 	in_flight_monitor_updates: BTreeMap<OutPoint, Vec<ChannelMonitorUpdate>>,
 	/// Map from a specific channel to some action(s) that should be taken when all pending
 	/// [`ChannelMonitorUpdate`]s for the channel complete updating.
@@ -2962,9 +2962,9 @@ macro_rules! locked_close_channel {
 				// We want to track the in-flight update both in `in_flight_monitor_updates` and in
 				// `pending_background_events` to avoid a race condition during
 				// `pending_background_events` processing where we complete one
-				// `ChannelMonitorUpdate` (but there are more pending) but we conclude that all
-				// pending `ChannelMonitorUpdate`s have completed and its safe to run
-				// post-completion actions. We could work around that with some effort, but its
+				// `ChannelMonitorUpdate` (but there are more pending as background events) but we
+				// conclude that all pending `ChannelMonitorUpdate`s have completed and its safe to
+				// run post-completion actions. We could work around that with some effort, but its
 				// simpler to just track updates twice.
 				let in_flight_updates = $peer_state.in_flight_monitor_updates.entry(funding_txo)
 					.or_insert_with(Vec::new);