diff --git a/ch03_bitcoin-core.adoc b/ch03_bitcoin-core.adoc
index b351b36e..cb053349 100644
--- a/ch03_bitcoin-core.adoc
+++ b/ch03_bitcoin-core.adoc
@@ -888,7 +888,7 @@ transmitted from one owner to the((("Bitcoin Core", "command-line interface", "e
 ==== Exploring Blocks
 
 Exploring
-blocks is similar to exploring transactions. However, blocks can be
+blocks is((("Bitcoin Core", "command-line interface", "exploring blocks", id="bitcoin-core-command-blocks")))((("command-line interface (Bitcoin Core)", "exploring blocks", id="command-blocks")))((("blocks", "exploring", id="blocks-explore")))((("exploring", "blocks", id="explore-blocks"))) similar to exploring transactions. However, blocks can be
 referenced either by the block _height_ or by the block _hash_. First,
 let's find a block by its height.
 We use the +getblockhash+ command, which takes the block height as the
@@ -962,7 +962,7 @@ miners to manipulate), and the size of the block in three different
 measurements (its legacy stripped size, its full size, and its size in
 weight units).  We also see some fields used for security and
 proof of work (merkle root, nonce, bits, difficulty, and chainwork);
-we'll examine those in detail in <<mining>>.
+we'll examine those ((("Bitcoin Core", "command-line interface", "exploring blocks", startref="bitcoin-core-command-blocks")))((("command-line interface (Bitcoin Core)", "exploring blocks", startref="command-blocks")))((("blocks", "exploring", startref="blocks-explore")))((("exploring", "blocks", startref="explore-blocks")))in detail in <<mining>>.
 
 ==== Using Bitcoin Core's Programmatic Interface