diff --git a/ch09_fees.adoc b/ch09_fees.adoc
index 16a53117..e3b388d8 100644
--- a/ch09_fees.adoc
+++ b/ch09_fees.adoc
@@ -412,7 +412,7 @@ which is addressed by ((("transaction fees", "fee bumping", "CPFP (child pays fo
 
 === Package Relay
 
-Early versions of Bitcoin Core didn't place any limits on the number of
+Early versions((("transaction fees", "package relay", id="transaction-fee-package-relay")))((("package relay", id="package-relay"))) of Bitcoin Core didn't place any limits on the number of
 unconfirmed transactions they stored for later relay and mining in their
 mempools (see <<mempool>>).  Of course, computers have physical limits, whether
 it's the memory (RAM) or disk space--it's not possible for a full node
@@ -445,7 +445,7 @@ making it effectively impossible to estimate an appropriate fee rate.
 If a presigned transaction pays a fee rate below the amount necessary to
 get into a node's mempool, there's no way to fee bump it with a child.
 If that prevents the transaction from confirming in time, an honest user
-might lose money.  Package relay is the solution for this critical
+might lose money.  Package relay is the solution for this ((("transaction fees", "package relay", startref="transaction-fee-package-relay")))((("package relay", startref="package-relay")))critical
 problem.
 
 [[transaction_pinning]]