diff --git a/ch06_transactions.adoc b/ch06_transactions.adoc
index cbfa2977..34d88bd4 100644
--- a/ch06_transactions.adoc
+++ b/ch06_transactions.adoc
@@ -877,7 +877,7 @@ certainly talking about the unwanted variant of((("transactions", "witnesses", "
 
 ==== Second-Party Transaction Malleability
 
-When the legacy transaction format was the only transaction format,
+When the ((("transactions", "witnesses", "second-party transaction malleability", id="transaction-witness-second-party")))((("witnesses", "second-party transaction malleability", id="witness-circular-second-party")))((("second-party transaction malleability", id="second-party")))legacy transaction format was the only transaction format,
 developers worked on proposals to minimize third-party malleability,
 such as BIP62.  However, even if they were able to entirely eliminate
 third-party malleability, users of contract protocols faced another problem:
@@ -915,7 +915,7 @@ Tx~0~ (which contains Bob's signature), Bob can generate an alternative
 signature to create a conflicting transaction with a different txid.  If
 Bob's alternative version of Tx~0~ gets confirmed, then Alice can't use
 the presigned version of Tx~1~ to claim her refund.  This type of
-mutation is called _unwanted second-party transaction malleability_.
+mutation ((("transactions", "witnesses", "second-party transaction malleability", startref="transaction-witness-second-party")))((("witnesses", "second-party transaction malleability", startref="witness-circular-second-party")))((("second-party transaction malleability", startref="second-party")))is called _unwanted second-party transaction malleability_.
 
 [[segwit]]
 ==== Segregated Witness