diff --git a/ch10_network.adoc b/ch10_network.adoc
index 69255dd3..86a69276 100644
--- a/ch10_network.adoc
+++ b/ch10_network.adoc
@@ -83,7 +83,7 @@ merchant payment processing) to be built on top.
 
 === Compact Block Relay
 
-When a ((("Bitcoin network", "blocks", "compact block relay", id="bitcoin-network-block-compact-relay")))((("blocks", "compact block relay", id="block-compact-relay")))((("compact block relay", id="compact-block-relay")))((("mining", "blocks", "compact block relay", id="mining-block-compact-relay")))miner finds a new block, they announce it to the Bitcoin network
+When a ((("Bitcoin network", "nodes", "compact block relay", id="bitcoin-network-node-compact-relay")))((("nodes", "compact block relay", id="node-compact-relay")))((("blocks", "compact block relay", id="block-compact-relay")))((("compact block relay", id="compact-block-relay")))((("mining", "blocks", "compact block relay", id="mining-block-compact-relay")))miner finds a new block, they announce it to the Bitcoin network
 (which includes other miners).  The miner who found that block can start
 building on top of it immediately; all other miners who haven't learned
 about the block yet will continue building on top of the previous block
@@ -148,7 +148,7 @@ There are two modes that Bitcoin Core currently implements for sending
 compact blocks, illustrated in <<bip152_illustration>>:
 
 Low-bandwidth mode::
-  When your node requests that a peer use low-bandwidth mode (the default),
+  When your((("low-bandwidth mode (compact block relay)"))) node requests that a peer use low-bandwidth mode (the default),
   that peer will tell your node the 32-byte identifier (header hash) of a
   new block but will not send your node any details about it.  If your
   node acquires that block first from another source, this avoids
@@ -157,7 +157,7 @@ Low-bandwidth mode::
   block.
 
 High-bandwidth mode::
-  When your node requests that a peer use high-bandwidth mode, that peer
+  When your node ((("high-bandwidth mode (compact block relay)")))requests that a peer use high-bandwidth mode, that peer
   will send your node a compact block for a new block even before it has
   fully verified that the block is valid.  The only validation the peer
   will perform is ensuring that the block's header contains the correct
@@ -182,7 +182,7 @@ The names of the two methods (which are taken from BIP152) can be a bit
 confusing.  Low-bandwidth mode saves bandwidth by not sending blocks in
 most cases.  High-bandwidth mode uses more bandwidth than low-bandwidth
 mode but, in most cases, much less bandwidth than was used for block
-relay before compact blocks were ((("Bitcoin network", "blocks", "compact block relay", startref="bitcoin-network-block-compact-relay")))((("blocks", "compact block relay", startref="block-compact-relay")))((("compact block relay", startref="compact-block-relay")))((("mining", "blocks", "compact block relay", startref="mining-block-compact-relay")))implemented.
+relay before compact blocks were ((("Bitcoin network", "nodes", "compact block relay", startref="bitcoin-network-node-compact-relay")))((("nodes", "compact block relay", startref="node-compact-relay")))((("blocks", "compact block relay", startref="block-compact-relay")))((("compact block relay", startref="compact-block-relay")))((("mining", "blocks", "compact block relay", startref="mining-block-compact-relay")))implemented.
 
 === Private Block Relay Networks