Edited ch06_transactions.adoc with Atlas code editor

ch06_transactions.adoc

@@ -1010,7 +1010,7 @@ be received to witness programs and spent with the witness structure. The terms
 
 ==== Witness Structure Serialization
 
-Similar to the inputs and outputs fields, the witness structure contains
+Similar to((("transactions", "witnesses", "count", id="transaction-witness-count")))((("witnesses", "count", id="witness-count"))) the inputs and outputs fields, the witness structure contains
 other fields, so we'll start with a map of those bytes from
 Alice's transaction in <<alice_tx_witness_map>>.
 
@@ -1024,7 +1024,7 @@ Instead, this is implied by the inputs field--there's one witness
 stack for every input in a transaction.
 
 The witness structure for a particular input does start with a count of the
-number of elements they contain.  Those elements are called _witness
+number of elements they contain.  Those elements are ((("witness items")))called _witness
 items_.  We'll explore them in detail in
 <<c_authorization_authentication>>, but for now we need to know that
 each witness item is prefixed by a compactSize integer indicating its
@@ -1033,7 +1033,7 @@ size.
 Legacy inputs don't contain any witness items so their witness stack
 consists entirely of a count of zero (0x00).
 
-Alice's transaction contains one input and one ((("transactions", "witnesses", startref="transaction-witness")))((("witnesses", startref="witness")))witness item.
+Alice's transaction contains one input and one ((("transactions", "witnesses", startref="transaction-witness")))((("witnesses", startref="witness")))((("transactions", "witnesses", "count", startref="transaction-witness-count")))((("witnesses", "count", startref="witness-count")))witness item.
 
 [[lock_time]]
 === Lock Time