s/Rust-Lightning/rust-lightning/g

Author: tnull

README.md

@@ -1,11 +1,11 @@
-Rust-Lightning
+`rust-lightning`
 ==============
 
 [![Crate](https://img.shields.io/crates/v/lightning.svg?logo=rust)](https://crates.io/crates/lightning)
 [![Documentation](https://img.shields.io/static/v1?logo=read-the-docs&label=docs.rs&message=lightning&color=informational)](https://docs.rs/lightning/)
 [![Safety Dance](https://img.shields.io/badge/unsafe-forbidden-success.svg)](https://github.com/rust-secure-code/safety-dance/)
 
-Rust-Lightning is a Bitcoin Lightning library written in Rust. The main crate,
+`rust-lightning` is a Bitcoin Lightning library written in Rust. The main crate,
 `lightning`, does not handle networking, persistence, or any other I/O. Thus,
 it is runtime-agnostic, but users must implement basic networking logic, chain
 interactions, and disk storage. More information is available in the `About`
@@ -21,7 +21,7 @@ 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
+Communications for `rust-lightning` and Lightning Development Kit happens through
 our LDK [Discord](https://discord.gg/5AcknnMfBw) channels.
 
 Crates
@@ -38,30 +38,30 @@ Crates
   [BOLT #11](https://github.com/lightning/bolts/blob/master/11-payment-encoding.md)
   Lightning invoices.
 5. [lightning-net-tokio](./lightning-net-tokio)
-  Implementation of the rust-lightning network stack using the
-  [Tokio](https://github.com/tokio-rs/tokio) `async` runtime. For Rust-Lightning
+  Implementation of the `rust-lightning` network stack using the
+  [Tokio](https://github.com/tokio-rs/tokio) `async` runtime. For `rust-lightning`
   clients which wish to make direct connections to Lightning P2P nodes, this is
   a simple alternative to implementing the required network stack, especially
   for those already using Tokio.
 6. [lightning-persister](./lightning-persister)
-  Implements utilities to manage Rust-Lightning channel data persistence and retrieval.
+  Implements utilities to manage `rust-lightning` channel data persistence and retrieval.
   Persisting channel data is crucial to avoiding loss of channel funds.
 7. [lightning-rapid-gossip-sync](./lightning-rapid-gossip-sync)
   Client for rapid gossip graph syncing, aimed primarily at mobile clients.
 
 About
 -----------
-LDK/Rust-Lightning is a generic library which allows you to build a Lightning
+LDK/`rust-lightning` is a generic library which allows you to build a Lightning
 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
+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
+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.
 
@@ -71,7 +71,7 @@ Bitcoin Core RPC/REST interface is available
 that demo are 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):
+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
   Google Drive/iCloud, a local disk, any key-value store/database/a remote
   server, or any combination of them - we provide a clean API that provides
@@ -113,26 +113,26 @@ Design Goal
 The goal is to provide a full-featured but also incredibly flexible Lightning
 implementation, allowing the user to decide how they wish to use it. With that
 in mind, everything should be exposed via simple, composable APIs. More
-information about Rust-Lightning's flexibility is provided in the `About`
+information about `rust-lightning`'s flexibility is provided in the `About`
 section above.
 
 For security reasons, do not add new dependencies. Really do not add new
 non-optional/non-test/non-library dependencies. Really really do not add
 dependencies with dependencies. Do convince Andrew to cut down dependency usage
-in rust-bitcoin.
+in `rust-bitcoin`.
 
-Rust-Lightning vs. LDK (Lightning Development Kit)
+`rust-lightning` vs. LDK (Lightning Development Kit)
 -------------
-Rust-Lightning refers to the core `lightning` crate within this repo, whereas
-LDK encompasses Rust-Lightning and all of its sample modules and crates (e.g.
+`rust-lightning` refers to the core `lightning` crate within this repo, whereas
+LDK encompasses `rust-lightning` and all of its sample modules and crates (e.g.
 the `lightning-persister` crate), language bindings, sample node
-implementation(s), and other tools built around using Rust-Lightning for
+implementation(s), and other tools built around using `rust-lightning` for
 Lightning integration or building a Lightning node.
 
 Tagline
 -------
 
-*"Rust-Lightning, not Rusty's Lightning!"*
+*"`rust-lightning`, not Rusty's Lightning!"*
 
 Contributing
 ------------
@@ -142,7 +142,7 @@ Contributors are warmly welcome, see [CONTRIBUTING.md](CONTRIBUTING.md).
 Project Architecture
 ---------------------
 
-For a Rust-Lightning high-level API introduction, see [ARCH.md](ARCH.md).
+For a `rust-lightning` high-level API introduction, see [ARCH.md](ARCH.md).
 
 License is either Apache-2.0 or MIT, at the option of the user (ie dual-license
 Apache-2.0 and MIT).