Edited ch09_fees.adoc with Atlas code editor

ch09_fees.adoc

@@ -193,7 +193,7 @@ bumping in Bitcoin, replace by fee (RBF) and child pays for parent
 [[rbf]]
 === Replace By Fee (RBF) Fee Bumping
 
-To((("transaction fees", "fee bumping", "RBF (replace by fee)", id="transaction-fees-bump-rbf")))((("fee bumping", "RBF (replace by fee)", id="fee-bump-rbf")))((("RBF (replace by fee) fee bumping", id="rbf"))) increase the fee of a transaction using RBF fee bumping, you create
+To((("transaction fees", "fee bumping", "RBF (replace by fee)", id="transaction-fees-bump-rbf")))((("fee bumping", "RBF (replace by fee)", id="fee-bump-rbf")))((("RBF (replace by fee) fee bumping", id="rbf-ch9"))) increase the fee of a transaction using RBF fee bumping, you create
 a conflicting version of the transaction that pays a higher fee.  Two
 or more transactions are considered((("conflicting transactions")))((("transactions", "conflicts in"))) to be _conflicting transactions_ if
 only one of them can be included in a valid blockchain, forcing a miner
@@ -354,7 +354,7 @@ general, if you're the receiver of an unconfirmed transaction and you
 want to make it confirm faster (or at all), you can't use an RBF fee
 bump; you need some other method.
 
-There are additional problems ((("transaction fees", "fee bumping", "RBF (replace by fee)", startref="transaction-fees-bump-rbf")))((("fee bumping", "RBF (replace by fee)", startref="fee-bump-rbf")))((("RBF (replace by fee) fee bumping", startref="rbf")))with RBF that we'll explore in <<transaction_pinning>>.
+There are additional problems ((("transaction fees", "fee bumping", "RBF (replace by fee)", startref="transaction-fees-bump-rbf")))((("fee bumping", "RBF (replace by fee)", startref="fee-bump-rbf")))((("RBF (replace by fee) fee bumping", startref="rbf-ch9")))with RBF that we'll explore in <<transaction_pinning>>.
 
 [[cpfp]]
 === Child Pays for Parent (CPFP) Fee Bumping