f Small doc adjustments

Author: tnull

src/config.rs

@@ -156,11 +156,10 @@ impl Default for Config {
 /// design of pre-anchor channels proved inadequate in the unpredictable, often turbulent, fee
 /// markets we experience today.
 ///
-/// In contrast, Anchor channels allow to determine an adequate fee
-/// rate *at the time of channel closure*, making them much more robust in the face of fee spikes.
-/// In turn, they require to maintain a reserve of on-chain funds to have the channel closure
-/// transactions confirmed on-chain, at least if the channel counterparty can't be trusted to do
-/// this for us.
+/// In contrast, Anchor channels allow to determine an adequate fee rate *at the time of channel
+/// closure*, making them much more robust in the face of fee spikes. In turn, they require to
+/// maintain a reserve of on-chain funds to have the channel closure transactions confirmed
+/// on-chain, at least if the channel counterparty can't be trusted to do this for us.
 ///
 /// See [BOLT 3] for more technical details on Anchor channels.
 ///
@@ -188,9 +187,11 @@ pub struct AnchorChannelsConfig {
 	/// funds stuck *or* even allow the counterparty to steal any in-flight funds after the
 	/// corresponding HTLCs time out.
 	pub trusted_peers_no_reserve: Vec<PublicKey>,
-	/// The amount of satoshis per anchors-negotiated channel with an untrusted peer we keep as an
-	/// emergency reserve in our on-chain wallet in order to have the required Anchor output
-	/// spending and HTLC transactions confirmed when the channel is closed.
+	/// The amount of satoshis per anchors-negotiated channel with an untrusted peer that we keep
+	/// as an emergency reserve in our on-chain wallet.
+	///
+	/// This allows for having the required Anchor output spending and HTLC transactions confirmed
+	/// when the channel is closed.
 	///
 	/// If the channel peer is not marked as trusted via
 	/// [`AnchorChannelsConfig::trusted_peers_no_reserve`], we will always try to spend the Anchor