Edited ch09_fees.adoc with Atlas code editor

ch09_fees.adoc

@@ -530,7 +530,7 @@ this writing—https://oreil.ly/300dv[ephemeral anchors].
 [[cpfp_carve_out]]
 === CPFP Carve Out and Anchor Outputs
 
-In 2018, developers working on Lightning Network (LN) had a problem.
+In 2018, ((("transaction fees", "fee bumping", "CPFP carve outs", id="transaction-fee-bump-carveout")))((("fee bumping", "CPFP carve outs", id="fee-bump-carveout")))((("carve outs (CPFP)", id="carveout")))((("CPFP (child pay for parent) fee bumping", "carve outs", id="cpfp-carveout")))developers working on Lightning Network (LN) had a problem.
 Their protocol uses transactions that require signatures from two
 different parties.  Neither party wants to trust the other, so they sign
 transactions at a point in the protocol when trust isn't needed,
@@ -576,7 +576,7 @@ for that and developers are focused on building more generic solutions
 to transaction pinning attacks.
 
 As of this writing, most popular LN implementations use a transaction
-template called _anchor outputs_, which is designed to be used with CPFP
+template called _anchor outputs_, which is designed to be used ((("transaction fees", "fee bumping", "CPFP carve outs", startref="transaction-fee-bump-carveout")))((("fee bumping", "CPFP carve outs", startref="fee-bump-carveout")))((("carve outs (CPFP)", startref="carveout")))((("CPFP (child pay for parent) fee bumping", "carve outs", startref="cpfp-carveout")))with CPFP
 carve out.
 
 === Adding Fees to Transactions