X-Git-Url: http://git.bitcoin.ninja/index.cgi?a=blobdiff_plain;f=README.md;h=a4ab59b53833afd6e672d1d67686a233b98f67ff;hb=refs%2Fheads%2F2023-12-no-async-signing;hp=824a2875b6331a51d293f47aaaa2f83c3fada7ee;hpb=6817762841c96bbe3f16156de454e0362d79d300;p=rust-lightning

diff --git a/README.md b/README.md
index 824a2875..a4ab59b5 100644
--- a/README.md
+++ b/README.md
@@ -94,7 +94,7 @@ In general, `rust-lightning` does not provide (but LDK has implementations of):
   wanted to run your full Lightning node on a hardware wallet, you could, by
   piping the Lightning network messages over USB/serial and then sending them in
   a TCP socket from another machine.
-* private keys - again we have "default implementations", but users can chose to
+* private keys - again we have "default implementations", but users can choose to
   provide private keys to RL/LDK in any way they wish following a simple API. We
   even support a generic API for signing transactions, allowing users to run
   RL/LDK without any private keys in memory/putting private keys only on
@@ -105,8 +105,8 @@ https://vimeo.com/showcase/8372504/video/412818125
 
 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
+The goal is to provide a fully-featured and incredibly flexible Lightning
+implementation, allowing users 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`
 section above.