f Clarify counterparty-doesn't-support-Anchors case

Author: tnull

src/config.rs

@@ -113,9 +113,11 @@ pub struct Config {
 	///
 	/// Please refer to [`AnchorChannelsConfig`] for further information on Anchor channels.
 	///
-	/// If set to `Some`, new channels will have Anchors enabled, i.e., will be negotiated with the
-	/// `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.
+	/// If set to `Some`, we'll try to open new channels with Anchors enabled, i.e., new channels
+	/// will be negotiated with the `option_anchors_zero_fee_htlc_tx` channel type if supported by
+	/// the counterparty. Note that this won't prevent us from opening non-Anchor channels if the
+	/// counterparty doesn't support `option_anchors_zero_fee_htlc_tx`. If set to `None`, new
+	/// channels will be negotiated with the legacy `option_static_remotekey` channel type only.
 	///
 	/// **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,