f fully fix case

Author: TheBlueMatt

CHANGELOG.md

@@ -43,10 +43,10 @@
    a while to receive a pong from them. Further, we avoid sending too many
    gossip messages between pings to ensure we should always receive pongs in a
    timely manner (#1137).
- * If a payment is sent, creating an outbound HTLC and sending it to our
+ * If a payment was 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 was be generated if the HTLC is eventually
+   `Event::PaymentPathFailed` event was generated if the HTLC is eventually
    failed on chain. Events are now consistent irrespective of `ChannelManager`
    persistence or non-persistence (#1104).