Edited ch09_fees.adoc with Atlas code editor

ch09_fees.adoc

@@ -458,15 +458,18 @@ problem.
 [[transaction_pinning]]
 === Transaction Pinning
 
-Although((("transaction fees", "fee bumping", "transaction pinning", id="transaction-fee-bump-pin")))((("fee bumping", "transaction pinning", id="fee-bump-pin")))((("transaction pinning", id="transaction-pin")))((("RBF (replace by fee) fee bumping", "transaction pinning", id="rbf-pin")))((("CPFP (child pays for parent) fee bumping", "transaction pinning", id="cpfp-pin"))) both RBF and CPFP fee bumping work in the basic cases we
+++++
+<p class="fix_tracking">
+Although both RBF and CPFP fee bumping work in the basic cases we
 described, there are rules related to both
 methods that are designed to prevent denial-of-service attacks on miners
 and relaying full nodes.  An unfortunate side effect of those rules
 is that they can sometimes prevent someone from being able to use fee
 bumping.  Making it impossible or difficult to fee bump a transaction is
-called _transaction pinning_.
+called <em>transaction pinning</em>.</p>
+++++
 
-One of the major denial of service concerns revolves around the effect of
+One((("transaction fees", "fee bumping", "transaction pinning", id="transaction-fee-bump-pin")))((("fee bumping", "transaction pinning", id="fee-bump-pin")))((("transaction pinning", id="transaction-pin")))((("RBF (replace by fee) fee bumping", "transaction pinning", id="rbf-pin")))((("CPFP (child pays for parent) fee bumping", "transaction pinning", id="cpfp-pin"))) of the major denial of service concerns revolves around the effect of
 transaction relationships.  Whenever the output of a transaction is
 spent, that transaction's identifier (txid) is referenced by the child
 transaction.  However, when a transaction is replaced, the replacement