Edited ch14_applications.adoc with Atlas code editor

ch14_applications.adoc

@@ -194,7 +194,7 @@ coins are to be spent.  That brings us to _pay to contract (P2C)_.
 [[p2c_for_colored_coins]]
 ==== Pay to Contract (P2C)
 
-We previously learned about P2C in <<pay_to_contract>>, where it became
+We ((("colored coins application", "P2C (pay to contract)", id="color-coin-p2c")))((("P2C (pay to contract)", id="p2c-color-coin")))previously learned about P2C in <<pay_to_contract>>, where it became
 part of the basis for the taproot upgrade to Bitcoin's consensus rules.
 As a short reminder, P2C allows a spender (Bob) and receiver (Alice) to
 agree on some data, such as a contract, and then tweak Alice's public
@@ -226,7 +226,7 @@ spends and Alice has tweaked her public key by the contract terms.
 
 Because full nodes don't (and can't) validate that the contract is
 followed correctly, we need to figure out who is responsible for
-validation.  That brings us to _client-side validation._
+validation.  That brings ((("colored coins application", "P2C (pay to contract)", startref="color-coin-p2c")))((("P2C (pay to contract)", startref="p2c-color-coin")))us to _client-side validation._
 
 ==== Client-Side Validation