Tidy up docs

Author: jurvis

lightning/src/ln/channelmanager.rs

@@ -1726,7 +1726,7 @@ where
 	///
 	/// This can be useful for payments that may have been prepared, but ultimately not sent, as a
 	/// result of a crash. If such a payment exists, is not listed here, and an
-	/// [`Event::PaymentSent`] event has yet to be received, you may consider retrying the payment.
+	/// [`Event::PaymentSent`] has not been received, you may consider retrying the payment.
 	///
 	/// [`Event::PaymentSent`]: events::Event::PaymentSent
 	pub fn list_recent_payments(&self) -> Vec<RecentPaymentDetails> {
@@ -2508,10 +2508,10 @@ where
 	/// irrevocably committed to on our end. In such a case, do NOT retry the payment with a
 	/// different route unless you intend to pay twice!
 	///
-	/// Additionally,  if the process of sending a payment begins, but we crash before send_payment
-	/// returns (or prior to MonitorUpdate completion if you're using
-	/// [`ChannelMonitorUpdateStatus::InProgress`]), the payment may be lost on restart. See
-	/// [`ChannelManager::list_recent_payments`] for more information.
+	/// Thus, in order to ensure duplicate payments are not sent, if we begin the process of sending
+	/// a payment, but crash before `send_payment` returns (or prior to [`ChannelMonitorUpdate`]
+	/// persistence if you're using [`ChannelMonitorUpdateStatus::InProgress`]), the payment may be
+	/// lost on restart. See [`ChannelManager::list_recent_payments`] for more information.
 	///
 	/// payment_secret is unrelated to payment_hash (or PaymentPreimage) and exists to authenticate
 	/// the sender to the recipient and prevent payment-probing (deanonymization) attacks. For