diff --git a/ch07_authorization-authentication.adoc b/ch07_authorization-authentication.adoc
index de9bc8b9..0e6b8e0a 100644
--- a/ch07_authorization-authentication.adoc
+++ b/ch07_authorization-authentication.adoc
@@ -920,7 +920,7 @@ the consensus rules.
 
 ==== Relative Timelocks with OP_CSV
 
-Just like +OP_CLTV+
+Just ((("OP_CSV script opcode", id="op-csv")))like +OP_CLTV+
 and lock time, there is a script opcode for relative timelocks that
 leverages the sequence value in scripts. That opcode is
 +OP_CHECKSEQUENCEVERIFY+, commonly referred to as +OP_CSV+ for short.
@@ -952,7 +952,7 @@ is, they're kept off the blockchain (_offchain_). A child transaction cannot be
 parent transaction has been propagated, mined, and aged by the time
 specified in the relative timelock. One application of this use case is shown in <<state_channels>> and <<lightning_network>>.
 
-+OP_CSV+ is defined((("transactions", "timelocks", "relative", startref="transaction-timelock-relative")))((("timelocks", "relative", startref="timelock-relative")))((("lock time", "relative", startref="locktime-relative")))((("scripts", "timelocks", "relative", startref="script-timelock-relative")))((("relative timelocks", startref="relative-timelock2"))) in detail in
++OP_CSV+ is defined((("transactions", "timelocks", "relative", startref="transaction-timelock-relative")))((("timelocks", "relative", startref="timelock-relative")))((("lock time", "relative", startref="locktime-relative")))((("scripts", "timelocks", "relative", startref="script-timelock-relative")))((("relative timelocks", startref="relative-timelock2")))((("OP_CSV script opcode", startref="op-csv"))) in detail in
 https://oreil.ly/z_Obw[BIP112,
 CHECKSEQUENCEVERIFY].