f update comment to remove bogus reference to monitor restoration

Author: TheBlueMatt

lightning/src/ln/channelmanager.rs

@@ -882,13 +882,12 @@ macro_rules! handle_chan_restoration_locked {
 
 			let chanmon_update: Option<ChannelMonitorUpdate> = $chanmon_update; // Force type-checking to resolve
 			if chanmon_update.is_some() {
-				// On reconnect (or monitor restoration), we, by definition, only resend a
-				// funding_locked if there have been no commitment updates, so the only channel
-				// monitor update which could also be associated with a funding_locked would be
-				// the funding_created/funding_signed monitor update. That monitor update failing
-				// implies that we won't send funding_locked until it's been updated, so we can't
-				// have a funding_locked and a monitor update here (so we don't bother to handle it
-				// correctly below).
+				// On reconnect, we, by definition, only resend a funding_locked if there have been
+				// no commitment updates, so the only channel monitor update which could also be
+				// associated with a funding_locked would be the funding_created/funding_signed
+				// monitor update. That monitor update failing implies that we won't send
+				// funding_locked until it's been updated, so we can't have a funding_locked and a
+				// monitor update here (so we don't bother to handle it correctly below).
 				assert!($funding_locked.is_none());
 				// A channel monitor update makes no sense without either a funding_locked or a
 				// commitment update to process after it. Since we can't have a funding_locked, we