From f7954eee1adda099576e1565748ae8f05e354b29 Mon Sep 17 00:00:00 2001
From: Will Binns <hello@willbinns.org>
Date: Thu, 11 Mar 2021 09:00:22 +0100
Subject: [PATCH] ch12: s/clicks/selects/

---
 ch12.asciidoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/ch12.asciidoc b/ch12.asciidoc
index dbceaf6e..3a9f0677 100644
--- a/ch12.asciidoc
+++ b/ch12.asciidoc
@@ -126,7 +126,7 @@ In the next round, Emma's software creates and signs another commitment transact
 
 In this way, Emma's software continues to send commitment transactions to Fabian's server in exchange for streaming video. The balance of the channel gradually accumulates in favor of Fabian, as Emma consumes more seconds of video. Let's say Emma watches 600 seconds (10 minutes) of video, creating and signing 600 commitment transactions. The last commitment transaction (#600) will have two outputs, splitting the balance of the channel, 6 millibits to Fabian and 30 millibits to Emma.
 
-Finally, Emma clicks "Stop" to stop streaming video. Either Fabian or Emma can now transmit the final state transaction for settlement. This last transaction is the _settlement transaction_ and pays Fabian for all the video Emma consumed, refunding the remainder of the funding transaction to Emma.
+Finally, Emma selects "Stop" to stop streaming video. Either Fabian or Emma can now transmit the final state transaction for settlement. This last transaction is the _settlement transaction_ and pays Fabian for all the video Emma consumed, refunding the remainder of the funding transaction to Emma.
 
 <<video_payment_channel>> shows the channel between Emma and Fabian and the commitment transactions that update the balance of the channel.