diff --git a/03_how_ln_works.asciidoc b/03_how_ln_works.asciidoc
index 0b4e021..7322c07 100644
--- a/03_how_ln_works.asciidoc
+++ b/03_how_ln_works.asciidoc
@@ -348,7 +348,7 @@ After all, that's what commitment transactions are for - they offer a guarantee
 Once you broadcast the last commitment transaction to the Bitcoin network and it is confirmed, it will create two spendable outputs, one for you and one for your partner.
 As we discussed previously, the Bitcoin network has no way of knowing if this was the most recent commitment transaction or an old one which was published to steal from your partner.
 Hence this commitment transaction will give a slight "advantage" to your partner.
-The partner who initiated the force close will their output encumbered by a timelock, and the other partner's output will be spendable immediately.
+The partner who initiated the force close will have their output encumbered by a timelock, and the other partner's output will be spendable immediately.
 In the case that you broadcasted an earlier commitment transaction, the timelock delay gives your partner the opportunity to "dispute" the transaction using the revocation secret and punish you for cheating.
 
 When publishing a commitment transaction during a force close, the on-chain fees will be higher than a mutual close for several reasons: