Edited ch06_transactions.adoc with Atlas code editor

ch06_transactions.adoc

@@ -1116,7 +1116,7 @@ A coinbase transaction can have any other outputs that would be valid in
 a normal transaction.  However, a transaction spending one of those
 outputs cannot be included in any block until after the coinbase
 transaction has received 100 confirmations.  This is called the
-_maturity rule_, and coinbase transaction outputs that don't yet have
+_maturity rule_, and ((("maturity rule")))coinbase transaction outputs that don't yet have
 100 confirmations are called _immature_.
 
 //TODO:stretch goal to describe the reason for the maturity rule and,
@@ -1136,7 +1136,7 @@ unusual problems in software that's not designed to expect((("transactions", "co
 
 === Weight and Vbytes
 
-Each Bitcoin block is limited in the amount of transaction data it can
+Each ((("transactions", "weights", id="transactions-weight")))((("weights (of transactions)", id="weights")))((("vbytes", id="vbytes")))Bitcoin block is limited in the amount of transaction data it can
 contain, so most Bitcoin software needs to be able to measure the
 transactions it creates or processes.  The modern unit of measurement
 for Bitcoin is called _weight_.  An alternative version of weight is
@@ -1252,7 +1252,7 @@ $ bitcoin-cli getrawtransaction 466200308696215bbc949d5141a49a41\
 Alice's transaction from <<alice_tx_serialized_reprint>> at the beginning of
 this chapter is shown represented in weight units in
 <<alice_tx_weight_map>>.  You can see the factor at work by comparing
-the difference in size between the various fields in the two images.
+the difference in size between the various fields in the ((("transactions", "weights", startref="transactions-weight")))((("weights (of transactions)", startref="weights")))((("vbytes", startref="vbytes")))two images.
 
 [[alice_tx_weight_map]]
 .A byte map of Alice's transaction