f Nits

Author: tnull

README.md

@@ -13,14 +13,16 @@ section.
 
 Status
 ------
-The project implements all of the [BOLT specifications](https://github.com/lightning/bolts) in the
-1.0 spec. The implementation has pretty good test coverage that is expected to continue to improve.
-It is also anticipated that as developers begin using the API, the lessons from that will result in
-changes to the API, so any developer using this API at this stage should be prepared to embrace
-that. The current state is sufficient for a developer or project to experiment with it.
+The project implements all of the [BOLT
+specifications](https://github.com/lightning/bolts) in the spec. The
+implementation has pretty good test coverage that is expected to continue to
+improve. It is also anticipated that as developers begin using the API, the
+lessons from that will result in changes to the API, so any developer using this
+API at this stage should be prepared to embrace that. The current state is
+sufficient for a developer or project to experiment with it.
 
-Communications for Rust-Lightning and Lightning Development Kit happens through our LDK
-[Discord](https://discord.gg/5AcknnMfBw) channels.
+Communications for Rust-Lightning and Lightning Development Kit happens through
+our LDK [Discord](https://discord.gg/5AcknnMfBw) channels.
 
 Crates
 -----------
@@ -51,17 +53,19 @@ node without needing to worry about getting all of the Lightning state machine,
 routing, and on-chain punishment code (and other chain interactions) exactly
 correct. Note that Rust-Lightning isn't, in itself, a node. There are various
 working/in progress demos which could be used as a node today, but if you "just"
-want a generic Lightning node, you're almost certainly better off with
-[Core Lightning](https://github.com/ElementsProject/lightning) or
-[LND](https://github.com/lightningnetwork/lnd) - if, on the other hand, you want to integrate
-Lightning with custom features such as your own chain sync, your own key management, your
-own data storage/backup logic, etc., LDK is likely your only option. Some
-Rust-Lightning utilities such as those in [`chan_utils`](./lightning/src/ln/chan_utils.rs) are also
-suitable for use in non-LN Bitcoin applications such as DLCs and bulletin boards.
-
-A sample node which fetches blockchain data and manages on-chain funds via the Bitcoin Core
-RPC/REST interface is available [here](../ldk-sample). The individual pieces of that demo are be
-composable, so you can pick the off-the-shelf parts you want and replace the rest.
+want a generic Lightning node, you're almost certainly better off with [Core
+Lightning](https://github.com/ElementsProject/lightning) or
+[LND](https://github.com/lightningnetwork/lnd) - if, on the other hand, you want
+to integrate Lightning with custom features such as your own chain sync, your
+own key management, your own data storage/backup logic, etc., LDK is likely your
+only option. Some Rust-Lightning utilities such as those in
+[`chan_utils`](./lightning/src/ln/chan_utils.rs) are also suitable for use in
+non-LN Bitcoin applications such as DLCs and bulletin boards.
+
+A sample node which fetches blockchain data and manages on-chain funds via the
+Bitcoin Core RPC/REST interface is available [here](../ldk-sample). The
+individual pieces of that demo are be composable, so you can pick the
+off-the-shelf parts you want and replace the rest.
 
 In general, Rust-Lightning does not provide (but LDK has implementations of):
 * on-disk storage - you can store the channel state any way you want - whether