f sp and other tweaks from jeff

Author: TheBlueMatt

CHANGELOG.md

@@ -7,11 +7,11 @@
  * Since its last alpha release, `lightning-liquidity` has also gained support
    for acting as an LSPS1 client (#3436).
  * This release includes support for BIP 353 Human Readable Names resolution.
-   With the `dnssec` feature enabled, simply call
-   `ChannelManager::pay_for_offer_from_human_readable_name` with a list of
-   lightnig nodes which have the `dns_resolver` feature flag set (e.g. those
-   running LDK with the new `lightning-dns-resolver::OMDomainResolver` set up
-   to resolve DNS queries for others) and a Human Readable Name (#3346, #3179, #3283).
+   With the `dnssec` feature enabled, simply call `ChannelManager`'s
+   `pay_for_offer_from_human_readable_name` with a list of lightning nodes that
+   have the `dns_resolver` feature flag set (e.g. those running LDK with the
+   new `lightning_dns_resolver::OMDomainResolver` set up to resolve DNS queries
+   for others) and a Human Readable Name (#3346, #3179, #3283).
  * Asynchronous `ChannelMonitorUpdate` persistence (i.e. the use of
    `ChannelMonitorUpdateStatus::InProgress`) is now considered beta-quality.
    There are no known issues with it, though the likelihood of unknown issues
@@ -22,7 +22,7 @@
  * `ChannelMonitor`s no longer need to be re-persisted after deserializing the
    `ChannelManager` before beginning normal operation. As such,
    `ChannelManagerReadArgs::channel_monitors` no longer requires mutable
-   references (#3322).
+   references (#3322). See the Backwards Compatibility section for more info.
  * Additional information is now stored in `ChannelMonitorUpdate`s which may
    increase the average size of `ChannelMonitorUpdate`s when claiming inbound
    payments substantially. The expected maximum size of `ChannelMonitorUpdate`s
@@ -91,7 +91,6 @@
    a preimage for another channel is pending. This fixes an issue where a
    payment preimage needed for another channel claim is lost if events go
    un-processed for 4038 blocks (#3450).
- * Parsing BOLT 12 offers and refunds with uppercase prefixes now works (#3505).
  * `std` builds no longer send the full gossip state to peers that do not
    request it (#3390).
  * `lightning-block-sync` listeners now receive `block_connected` calls, rather
@@ -100,7 +99,7 @@
    locktime made them candidates for inclusion in the mempool (though they would
    be automatically re-broadcasted later, #3453).
  * `ChainMonitor` now persists `ChannelMonitor`s when their `Balance` set first
-   goes empty, making `ChannelMonitor` pruning more reliable on nodes which are
+   goes empty, making `ChannelMonitor` pruning more reliable on nodes that are
    only online briefly (e.g. mobile nodes, #3442).
  * BOLT 12 invoice requests now better handle intermittent internet connectivity
    (e.g. on mobile devices with app interruptions, #3010).