From e3316fd1de11130ea8d16bded570f931ecba8b73 Mon Sep 17 00:00:00 2001
From: Bitcoin Txoko <142011724+bitcointxoko@users.noreply.github.com>
Date: Thu, 21 Nov 2024 21:44:49 +0100
Subject: [PATCH] Update ln-03.md

---
 en/ln-03.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/en/ln-03.md b/en/ln-03.md
index 029286f..d756ca2 100644
--- a/en/ln-03.md
+++ b/en/ln-03.md
@@ -73,7 +73,7 @@ OP_ENDIF
 OP_CHECKSIG
 ```
 
-When it's time for Alice and Bob to update state and invalidate the old state, Alice sends Bob her private key for the commitment point `cA2`. With this key, Bob now has both Alice's per commitment point private key `cA1` as well as his own revocation basepoint private key `rB1` which corresponds to the public key `RB1` he sent Alice earlier when Alice was constructing the commitment transaction. So now with these two pieces of information, Bob can derive the private key corresponding to the public key `Rev_A1` and therefore spend via the revocation output. He can calculate the private key as follows:
+When it's time for Alice and Bob to update state and invalidate the old state, Alice sends Bob her private key for the commitment point `cA1`. With this key, Bob now has both Alice's per commitment point private key `cA1` as well as his own revocation basepoint private key `rB1` which corresponds to the public key `RB1` he sent Alice earlier when Alice was constructing the commitment transaction. So now with these two pieces of information, Bob can derive the private key corresponding to the public key `Rev_A1` and therefore spend via the revocation output. He can calculate the private key as follows:
 
 ```
 rev_A1 = r_B1 * sha256( R_B1 || C_A1 ) + c_A1 * sha256( C_A1 || R_B1 )