From 5ecbf39068b36c3d4253b6d62d4fd0f6ef98f740 Mon Sep 17 00:00:00 2001
From: rating89us <45968869+rating89us@users.noreply.github.com>
Date: Sun, 24 Jan 2021 23:58:15 +0100
Subject: [PATCH] ch06: explaining that the change "gift" goes to the miner

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

diff --git a/ch06.asciidoc b/ch06.asciidoc
index bbc7922e..6295bd3b 100644
--- a/ch06.asciidoc
+++ b/ch06.asciidoc
@@ -344,7 +344,7 @@ For example, if you consume a 20-bitcoin UTXO to make a 1-bitcoin payment, you m
 
 [WARNING]
 ====
-((("warnings and cautions", "change outputs")))If you forget to add a change output in a manually constructed transaction, you will be paying the change as a transaction fee. "Keep the change!" might not be what you intended.
+((("warnings and cautions", "change outputs")))If you forget to add a change output in a manually constructed transaction, you will be paying the change as a transaction fee. Saying "Keep the change!" to the miner might not be what you really intended.
 ====
 
 ((("use cases", "buying coffee")))Let's see how this works in practice, by looking at Alice's coffee purchase again. Alice wants to spend 0.015 bitcoin to pay for coffee. To ensure this transaction is processed promptly, she will want to include a transaction fee, say 0.001. That will mean that the total cost of the transaction will be 0.016. Her wallet must therefore source a set of UTXO that adds up to 0.016 bitcoin or more and, if necessary, create change. Let's say her wallet has a 0.2-bitcoin UTXO available. It will therefore need to consume this UTXO, create one output to Bob's Cafe for 0.015, and a second output with 0.184 bitcoin in change back to her own wallet, leaving 0.001 bitcoin unallocated, as an implicit fee for the transaction.