Edited ch06.asciidoc with Atlas code editor

ch06.asciidoc

@@ -12,7 +12,7 @@ In this chapter we will examine all the various forms of transactions, what they
 [[tx_structure]]
 === Transactions in Detail
 
-((("use cases", "buying coffee")))In <<ch02_bitcoin_overview>>, we looked at the transaction Alice used to pay for coffee at Bob's coffee shop using a block explorer (<<alices_transactions_to_bobs_cafe>>).
+((("use cases", "buying coffee", id="alicesix")))In <<ch02_bitcoin_overview>>, we looked at the transaction Alice used to pay for coffee at Bob's coffee shop using a block explorer (<<alices_transactions_to_bobs_cafe>>).
 
 The block explorer application shows a transaction from Alice's "address" to Bob's "address." This is a much simplified view of what is contained in a transaction. In fact, as we will see in this chapter, much of the information shown is constructed by the block explorer and is not actually in the transaction.
 
@@ -283,7 +283,7 @@ Hints:
 * The transaction ID is serialized in reversed byte order, so it starts with (hex) +18+ and ends with +79+
 * The output index is a 4-byte group of zeros, easy to identify
 * The length of the +scriptSig+ is 139 bytes, or +8b+ in hex
-* The sequence number is set to +FFFFFFFF+, again easy to identify
+* The sequence number is set to +FFFFFFFF+, again easy to identify((("", startref="alicesix")))
 
 [[tx_fees]]
 ==== Transaction Fees