Edited ch12_mining.adoc with Atlas code editor

ch12_mining.adoc

@@ -1816,7 +1816,7 @@ consensus modifications.
 
 ==== Soft Forks
 
-Not all consensus rule changes cause a hard fork. Only
+Not all((("consensus rules", "soft forks", "explained", id="consensus-soft-explain")))((("forks", "soft forks", "explained", id="fork-soft-explain")))((("soft forks", "explained", id="soft-fork-explain"))) consensus rule changes cause a hard fork. Only
 consensus changes that are forward-incompatible cause a fork. If the
 change is implemented in such a way that an unmodified client still sees
 the transaction or block as valid under the previous rules, the change
@@ -1854,7 +1854,7 @@ the NOP2 opcode. Clients implementing BIP65 interpret NOP2 as
 on UTXOs that contain this opcode in their locking scripts. This change
 is a soft fork because a transaction that is valid under BIP65 is also
 valid on any client that is not implementing (ignorant of) BIP65. To
-the old clients, the script contains an NOP code, which is ignored.
+the old clients, the script contains an NOP code, which is((("consensus rules", "soft forks", "explained", startref="consensus-soft-explain")))((("forks", "soft forks", "explained", startref="fork-soft-explain")))((("soft forks", "explained", startref="soft-fork-explain"))) ignored.
 
 ==== Criticisms of Soft Forks