f - use enforcement instead of monitoring

Author: jkczyz

lightning/src/ln/channelmanager.rs

@@ -1093,17 +1093,17 @@ where
 ///
 /// # `ChannelManager` vs `ChannelMonitor`
 ///
-/// It's important to distinguish between the *off-chain* management and *on-chain* monitoring of
+/// It's important to distinguish between the *off-chain* management and *on-chain* enforcement of
 /// lightning channels. [`ChannelManager`] exchanges messages with peers to manage the off-chain
 /// state of each channel. During this process, it generates a [`ChannelMonitor`] for each channel
 /// and a [`ChannelMonitorUpdate`] for each relevant change, notifying its parameterized
 /// [`chain::Watch`] of them.
 ///
 /// An implementation of [`chain::Watch`], such as [`ChainMonitor`], is responsible for aggregating
 /// these [`ChannelMonitor`]s and applying any [`ChannelMonitorUpdate`]s to them. It then monitors
-/// for any pertinent on-chain activity, broadcasting claims as needed.
+/// for any pertinent on-chain activity, enforcing claims as needed.
 ///
-/// This division of off-chain management and on-chain monitoring is what allows for interesting
+/// This division of off-chain management and on-chain enforcement is what allows for interesting
 /// node setups. See the [`chain`] module for further details.
 ///
 /// # Persistence