diff --git a/ch12_mining.adoc b/ch12_mining.adoc
index 905a526f..72c119da 100644
--- a/ch12_mining.adoc
+++ b/ch12_mining.adoc
@@ -1505,7 +1505,7 @@ needed to force a very deep fork is immense, making old blocks
 very hard to change. Hashrate attacks also do not affect the security
 of the private keys and signing algorithms.
 
-One attack scenario against the consensus mechanism is ((("majority attacks", id="majority-attack")))((("51% attacks", id="attack-51")))((("double-spend attacks", id="double-spend")))called the _majority
+One attack scenario against the consensus mechanism is ((("majority attacks", id="majority-attack")))((("51% attacks", primary-sortas="fifty-one percent attacks", id="attack-51")))((("double-spend attacks", id="double-spend")))called the _majority
 attack_ or _51% attack._ In this scenario a group of miners, controlling a majority
 of the total network's hashing power (such as 51%), collude to attack Bitcoin.
 With the ability to mine the majority of the blocks, the attacking
@@ -1590,7 +1590,7 @@ majority of the mining power.
 //TODO: update to not use 51% attack name (see other TODO in this
 //chapter)
 
-Despite its ((("majority attacks", startref="majority-attack")))((("51% attacks", startref="attack-51")))((("double-spend attacks", startref="double-spend")))name, the 51% attack scenario doesn't actually require 51%
+Despite its ((("majority attacks", startref="majority-attack")))((("51% attacks", primary-sortas="fifty-one percent attacks", startref="attack-51")))((("double-spend attacks", startref="double-spend")))name, the 51% attack scenario doesn't actually require 51%
 of the hashing power. In fact, such an attack can be attempted with a
 smaller percentage of the hashing power. The 51% threshold is simply the
 level at which such an attack is almost guaranteed to succeed. A