Edited ch07_authorization-authentication.adoc with Atlas code editor

ch07_authorization-authentication.adoc

@@ -887,7 +887,7 @@ https://oreil.ly/YmJGD[BIP65
 [[op_csv]]
 ==== Relative Timelocks
 
-Lock time and +OP_CLTV+ are both
+Lock time((("transactions", "timelocks", "relative", id="transaction-timelock-relative")))((("timelocks", "relative", id="timelock-relative")))((("lock time", "relative", id="locktime-relative")))((("scripts", "timelocks", "relative", id="script-timelock-relative")))((("relative timelocks", id="relative-timelock2"))) and +OP_CLTV+ are both
 _absolute timelocks_ in that they specify an absolute point in time. The
 next two timelock features we will examine are _relative timelocks_ in
 that they specify, as a condition of spending an output, an elapsed time
@@ -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 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"))) in detail in
 https://oreil.ly/z_Obw[BIP112,
 CHECKSEQUENCEVERIFY].