f clarify the cases somewhat since its not clear

Author: TheBlueMatt

lightning/src/chain/chainmonitor.rs

@@ -832,10 +832,10 @@ where
 	/// that hasn't changed, slowing down startup.
 	///
 	/// Note that this method *can* be used if additional blocks were replayed against the
-	/// [`ChannelMonitor`], and in general can only *not* be used if a [`ChannelMonitorUpdate`] was
-	/// replayed against the [`ChannelMonitor`] which needs to be persisted (i.e. the state has
-	/// changed due to a [`ChannelMonitorUpdate`] such that it may be different after another
-	/// restart).
+	/// [`ChannelMonitor`] or if a [`ChannelMonitorUpdate`] loaded from disk was replayed such that
+	/// it will replayed on startup, and in general can only *not* be used if you directly accessed
+	/// the [`ChannelMonitor`] and changed its state in some way that will not be replayed again on
+	/// a restart.
 	///
 	/// For [`ChannelMonitor`]s which were last serialized by an LDK version prior to 0.1 this will
 	/// fall back to calling [`chain::Watch::watch_channel`] and persisting the [`ChannelMonitor`].