diff --git a/03_how_ln_works.asciidoc b/03_how_ln_works.asciidoc
index ef6f120..7cfbfeb 100644
--- a/03_how_ln_works.asciidoc
+++ b/03_how_ln_works.asciidoc
@@ -218,7 +218,7 @@ But if they share their half with the other channel partner, then the other part
 In order to update the balance and receive a signature from Bob, Alice will have to share her half of the revocation secret of the current commitment transaction with Bob.
 
 Obviously, for every new update of the channel balance new revocation secrets have to be created and saved. 
-As long as a channel remains open, all revocation secrets ever created for this specific channel need to be keep as they might be needed in the future.
+As long as a channel remains open, all revocation secrets ever created for this specific channel need to be kept as they might be needed in the future.
 Luckily, the secrets are rather small and it is only the channel partners who need to keep them, not the entire network.
 Nevertheless, managing and storing the revocation secrets is one of the more elaborate parts of Lightning nodes that require node operators to maintain backups.
 Other technologies such as Watchtower services or switching to the aforementioned "eltoo" channels might be future strategies to mitigate these issues.