diff --git a/ch06_transactions.adoc b/ch06_transactions.adoc
index c1b203fb..2c1c8d04 100644
--- a/ch06_transactions.adoc
+++ b/ch06_transactions.adoc
@@ -531,7 +531,7 @@ and sequence signals, which we'll see in <<rbf>>.
 [[relative_timelocks]]
 ===== Sequence as a consensus-enforced relative timelock
 
-In <<version>>, we learned that the BIP68 soft fork added
+In <<version>>, we learned ((("relative timelocks", id="relative-timelock")))that the BIP68 soft fork added
 a new constraint to transactions with version numbers 2 or higher.  That
 constraint applies to the sequence field.
 
@@ -574,7 +574,7 @@ as defined by BIP68.
 image::images/mbc3_0603.png["BIP68 definition of sequence encoding"]
 
 Note that any transaction which sets a relative timelock using sequence
-also sends the signal for opt-in replace by fee ((("transactions", "inputs", startref="transaction-input")))((("inputs", startref="input-transaction")))((("transactions", "inputs", "sequence field", startref="transaction-input-sequence")))((("inputs", "sequence field", startref="input-transaction-sequence")))((("sequence field (transaction inputs)", startref="sequence-field")))as described in
+also sends the signal for opt-in replace by fee ((("transactions", "inputs", startref="transaction-input")))((("inputs", startref="input-transaction")))((("transactions", "inputs", "sequence field", startref="transaction-input-sequence")))((("inputs", "sequence field", startref="input-transaction-sequence")))((("sequence field (transaction inputs)", startref="sequence-field")))((("relative timelocks", startref="relative-timelock")))as described in
 <<sequence-bip125>>.
 
 === Outputs