f grammar + ticks

Author: TheBlueMatt

CHANGELOG.md

@@ -21,13 +21,13 @@
 
 For those moving to the new `ConfirmationTarget`, the new variants in terms of
 the old mempool/low/medium/high priorities are as follows:
- * OnChainSweep = HighPriority
- * MaxAllowedNonAnchorChannelRemoteFee = max(25 * 250, HighPriority * 10)
- * MinAllowedAnchorChannelRemoteFee = MempoolMinimum
- * MinAllowedNonAnchorChannelRemoteFee = Background - 250
- * AnchorChannelFee = Background
- * NonAnchorChannelFee = Normal
- * ChannelCloseMinimum = Background
+ * `OnChainSweep` = `HighPriority`
+ * `MaxAllowedNonAnchorChannelRemoteFee` = `max(25 * 250, HighPriority * 10)`
+ * `MinAllowedAnchorChannelRemoteFee` = `MempoolMinimum`
+ * `MinAllowedNonAnchorChannelRemoteFee` = `Background - 250`
+ * `AnchorChannelFee` = `Background`
+ * `NonAnchorChannelFee` = `Normal`
+ * `ChannelCloseMinimum` = `Background`
 
 ## Bug Fixes
  * Calling `ChannelManager::close_channel[_with_feerate_and_script]` on a
@@ -41,7 +41,7 @@ the old mempool/low/medium/high priorities are as follows:
  * Anchor outputs are now properly considered when calculating the amount
    available to send in HTLCs. This can prevent force-closes in anchor channels
    when sending payments which overflow the available balance (#2674).
- * A peer which sends an `update_fulfill_htlc` message for a forwarded HTLC,
+ * A peer that sends an `update_fulfill_htlc` message for a forwarded HTLC,
    then reconnects prior to sending a `commitment_signed` (thus retransmitting
    their `update_fulfill_htlc`) may result in the channel stalling and being
    unable to make progress (#2661).