Edited ch09_fees.adoc with Atlas code editor

ch09_fees.adoc

@@ -359,7 +359,7 @@ There are additional problems ((("transaction fees", "fee bumping", "RBF (replac
 [[cpfp]]
 === Child Pays for Parent (CPFP) Fee Bumping
 
-Anyone ((("transaction fees", "fee bumping", "CPFP (child pays for parent)", id="transaction-fees-bump-cpfp")))((("fee bumping", "CPFP (child pays for parent)", id="fee-bump-cpfp")))((("CPFP (child pays for parent) fee bumping", id="cpfp")))who receives the output of an unconfirmed transaction can
+Anyone ((("transaction fees", "fee bumping", "CPFP (child pays for parent)", id="transaction-fees-bump-cpfp")))((("fee bumping", "CPFP (child pays for parent)", id="fee-bump-cpfp")))((("CPFP (child pays for parent) fee bumping", id="cpfp-ch9")))who receives the output of an unconfirmed transaction can
 incentivize miners to confirm that transaction by spending that output.
 The transaction you want to get confirmed is called the _parent
 transaction_.  A transaction that spends an output of the parent
@@ -408,7 +408,7 @@ fees beyond the cost of the fee bump.
 There are several challenges with CPFP, some of which we'll explore in
 <<transaction_pinning>>.  One other problem that we
 specifically need to mention is the minimum relay fee rate problem,
-which is addressed by ((("transaction fees", "fee bumping", "CPFP (child pays for parent)", startref="transaction-fees-bump-cpfp")))((("fee bumping", "CPFP (child pays for parent)", startref="fee-bump-cpfp")))((("CPFP (child pays for parent) fee bumping", startref="cpfp")))package relay.
+which is addressed by ((("transaction fees", "fee bumping", "CPFP (child pays for parent)", startref="transaction-fees-bump-cpfp")))((("fee bumping", "CPFP (child pays for parent)", startref="fee-bump-cpfp")))((("CPFP (child pays for parent) fee bumping", startref="cpfp-ch9")))package relay.
 
 === Package Relay