f fix up docs val suggested

Author: TheBlueMatt

lightning/src/ln/channelmanager.rs

@@ -443,13 +443,13 @@ pub struct ChannelManager<Signer: Sign, M: Deref, T: Deref, K: Deref, F: Deref,
 	pending_inbound_payments: Mutex<HashMap<PaymentHash, PendingInboundPayment>>,
 
 	/// The session_priv bytes of outbound payments which are pending resolution.
-	/// The authoritative of these HTLCs resides either within Channels or ChannelMonitors (if the
-	/// channel has been force-closed), however we track them here to prevent duplicative
+	/// The authoritative state of these HTLCs resides either within Channels or ChannelMonitors
+	/// (if the channel has been force-closed), however we track them here to prevent duplicative
 	/// PaymentSent/PaymentFailed events. Specifically, in the case of a duplicative
 	/// update_fulfill_htlc message after a reconnect, we may "claim" a payment twice.
-	/// Additionally, for channels which have been force-closed, because the ChannelMonitor event
-	/// is ultimately handled by us, and we aren't supposed to generate duplicative events unless we
-	/// haven't been re-serialized, we have to de-duplicate them here.
+	/// Additionally, for channels which have been force-closed, a ChannelMonitor may not be
+	/// re-serialized after generating a claim event (even if this ChannelManager is), resulting in
+	/// us "claiming" a payment twice.
 	/// Locked *after* channel_state.
 	outbound_pending_payments: Mutex<HashSet<[u8; 32]>>,