f grammar and wording tweaks

Author: TheBlueMatt

CHANGELOG.md

@@ -21,7 +21,7 @@
    growth during initial start up from many GiB to several MiB (#1145).
  * The `allow_wallclock_use` feature has been removed in favor of only using
    the `std` and `no-std` features (#1212).
- * `NetworkGraph` can now remove channels which we haven't heard updates for in
+ * `NetworkGraph` can now remove channels that we haven't heard updates for in
    two weeks with `NetworkGraph::remove_stale_channels{,with_time}`. The first
    is called automatically if a `NetGraphMsgHandler` is passed to
    `BackgroundProcessor::start` (#1212).
@@ -35,11 +35,12 @@
    `routing::scoring` module instead of being in the `routing` module (#1166).
  * The `Time` parameter to `ScorerWithTime` is no longer longer exposed,
    instead being fixed based on the `std`/`no-std` feature (#1184).
- * `ChannelDetails::balance_msat` was added to access a channel's balance
-   without the reserve values, lining up with on-chain claim amounts (#1203).
+ * `ChannelDetails::balance_msat` was added to fetch a channel's balance
+   without subtracting the reserve values, lining up with on-chain claim amounts
+   less on-chain fees (#1203).
  * An explicit `UserConfig::accept_inbound_channels` flag is now provided,
    removing the need to set `min_funding_satoshis` to > 21 million BTC (#1173).
- * Inbound Channels which fail to see the funding transaction confirm within
+ * Inbound channels that fail to see the funding transaction confirm within
    2016 blocks are automatically force-closed with
    `ClosureReason::FundingTimedOut` (#1083).
  * We now accept a channel_reserve value of 0 from counterparties, as it is
@@ -53,30 +54,31 @@
  * Fixed a race condition in `InvoicePayer` where paths may be retried after
    the retry count has been exceeded. In this case the
    `Event::PaymentPathFailed::all_paths_failed` field is not a reliable payment
-   failure indicator. There is no acceptable alternative indicator (#1202).
+   failure indicator. There was no acceptable alternative indicator,
+   `Event::PaymentFailed` as been added to provide one (#1202).
  * Reduced the blocks-before-timeout we expect of outgoing HTLCs before
    refusing to forward. This check was overly strict and resulted in refusing
-   to forward some HTLCs to a next hop which had a lower security threshold
-   than us (#1119).
+   to forward som HTLCs to a next hop that had a lower security threshold than
+   us (#1119).
  * LDK no longer attempt to update the channel fee for outbound channels when
    we cannot afford the new fee. This could have caused force-closure by our
    channel counterparty (#1054).
  * Fixed several bugs which may have prevented the reliable broadcast of our
    own channel announcements and updates (#1169).
  * Fixed a rare bug which may have resulted in spurious route finding failures
    when using last-hop hints and MPP with large value payments (#1168).
- * `KeysManager::spend_spendable_outputs` no longer adds a change output which
+ * `KeysManager::spend_spendable_outputs` no longer adds a change output that
    is below the dust threshold for non-standard change scripts (#1131).
- * Fixed a minor memory leak when attempting to send a payment which fails due
+ * Fixed a minor memory leak when attempting to send a payment that fails due
    to an error when updating the `ChannelMonitor` (#1143).
- * Fixed a bug where a `FeeEstimator` which returns values which are rounded to
-   the next sat/vbyte may result in force-closures (#1208).
+ * Fixed a bug where a `FeeEstimator` that returns values rounded to the next
+   sat/vbyte may result in force-closures (#1208).
  * Handle MPP timeout HTLC error codes, instead of considering the recipient to
    have sent an invalid error, removing them from the network graph (#1148)
 
 ## Serialization Compatibility
- * All above new Events/fields are ignored by prior clients. All above new
-   Events/fields are not present when reading objects serialized by prior
+ * All above new events/fields are ignored by prior clients. All above new
+   events/fields are not present when reading objects serialized by prior
    versions of the library.
  * Payment secrets are now generated deterministically. This reduces the memory
    footprint for inbound payments, however, newly-generated inbound payments