diff --git a/ch06_transactions.adoc b/ch06_transactions.adoc
index 4b1e1943..eb87fcd2 100644
--- a/ch06_transactions.adoc
+++ b/ch06_transactions.adoc
@@ -148,7 +148,7 @@ Service (DoS) attacks that we'll discuss((("transactions", "version of", startre
 
 === Extended Marker and Flag
 
-The next two fields((("transactions", "extended serialization format")))((("extended serialization format"))) of the example serialized transaction were added as
+The next two fields((("transactions", "extended serialization format")))((("extended serialization format")))((("BIP144 extended serialization format"))) of the example serialized transaction were added as
 part of the segregated witness (segwit) soft fork change to Bitcoin's
 consensus rules.  The rules were changed according to BIPs 141 and 143,
 but the _extended serialization format_ is defined in BIP144.
@@ -163,7 +163,7 @@ be present.  This is compatible with the original version of Bitcoin's
 transaction serialization format, now called _legacy serialization_.
 For details, see <<legacy_serialization>>.
 
-In legacy serialization, the marker byte would have been interpreted as
+In ((("transactions", "legacy serialization")))((("legacy serialization")))legacy serialization, the marker byte would have been interpreted as
 the number of inputs (zero).  A transaction can't have zero inputs, so
 the marker signals to modern programs that extended serialization is
 being used.  The flag field provides a similar signal and also