f changelog tweaks

Author: TheBlueMatt

CHANGELOG.md

@@ -15,7 +15,7 @@
    `Payee` is further stored in the `Route` object returned and provided in the
    `RouteParameters` contained in `Event::PaymentPathFailed` (#1059).
  * `ChannelMonitor`s must now be persisted after calls which provide new block
-   data, prior to `MonitorEvent`s being passed back to `ChanelManager` for
+   data, prior to `MonitorEvent`s being passed back to `ChannelManager` for
    processing. If you are using a `ChainMonitor` this is handled for you.
    The `Persist` API has been updated to `Option`ally take the
    `ChannelMonitorUpdate` as persistence events that result from chain data no
@@ -41,6 +41,11 @@
    messages between pings to ensure we should always receive pongs in a timely
    manner. Together, these should significantly reduce instances of us failing
    to remain connected to a peer during initial gossip sync (#1137).
+ * If a payment is sent, creating an outbound HTLC and sending it to our
+   counterparty (implying the `ChannelMonitor` was persisted on disk), but the
+   `ChannelManager` was not persisted prior to shutdown/crash, no
+   `Event::PaymentPathFailed` event will be generated if the HTLC is eventually
+   failed on chain (#1104).
 
 ## Serialization Compatibility
  * All above new Events/fields are ignored by prior clients. All above new