f Improve docs

Author: tnull

src/config.rs

@@ -117,7 +117,7 @@ pub struct Config {
 	/// `option_anchors_zero_fee_htlc_tx` channel type. If set to `None`, new channels will be
 	/// negotiated with the legacy `option_static_remotekey` channel type.
 	///
-	/// **Note:** Please note that if set to `None` *after* some Anchor channels have already been
+	/// **Note:** If set to `None` *after* some Anchor channels have already been
 	/// opened, no dedicated emergency on-chain reserve will be maintained for these channels,
 	/// which can be dangerous if only insufficient funds are available at the time of channel
 	/// closure. We *will* however still try to get the Anchor spending transactions confirmed
@@ -152,11 +152,13 @@ impl Default for Config {
 /// opening. This required to estimate what fee rate would be sufficient to still have the
 /// closing transactions be spendable on-chain (i.e., not be considered dust). This legacy
 /// 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 be able to get the
-/// channel closure transactions confirmed on-chain, at least if the channel counterparty can't
-/// be trusted to do this for us.
+/// 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.
 ///
 /// See [BOLT 3] for more technical details on Anchor channels.
 ///
@@ -172,7 +174,7 @@ impl Default for Config {
 /// [BOLT 3]: https://github.com/lightning/bolts/blob/master/03-transactions.md#htlc-timeout-and-htlc-success-transactions
 #[derive(Debug, Clone)]
 pub struct AnchorChannelsConfig {
-	/// A list of peers which we trust to get the required channel closing transactions confirmed
+	/// A list of peers that we trust to get the required channel closing transactions confirmed
 	/// on-chain.
 	///
 	/// Channels with these peers won't count towards the retained on-chain reserve and we won't
@@ -185,8 +187,8 @@ pub struct AnchorChannelsConfig {
 	/// corresponding HTLCs time out.
 	pub trusted_peers_no_reserve: Vec<PublicKey>,
 	/// The amount of satoshis we keep as an emergency reserve in our on-chain wallet in order to
-	/// be able to get the required Anchor output spending and HTLC transactions confirmed when the
-	/// channel is closed.
+	/// have the required Anchor output spending and HTLC transactions confirmed when the channel
+	/// is closed.
 	///
 	/// **Note:** Depending on the fee market at the time of closure, this reserve amount might or
 	/// might not suffice to successfully spend the Anchor output and have the HTLC transactions