diff --git a/ch07_authorization-authentication.adoc b/ch07_authorization-authentication.adoc
index ccb576af..9814e296 100644
--- a/ch07_authorization-authentication.adoc
+++ b/ch07_authorization-authentication.adoc
@@ -1956,7 +1956,7 @@ in November 2021.
 
 //FIXME:mention "control block" (maybe in MAST section)
 
-Taproot ((("scripts", "MAST", "tapscript", id="script-mast-tapscript")))((("MAST (merklized alternative script trees)", "tapscript", id="mast-tapscript")))((("merkle trees", "MAST", "tapscript", id="merkle-tree-mast-tapscript")))((("tapscript", id="tapscript")))((("mutual satisfaction contracts", "tapscript", id="mutual-satisfaction-tapscript")))enables MAST but only with a slightly different version of the
+Taproot ((("tapscript", id="tapscript")))((("mutual satisfaction contracts", "tapscript", id="mutual-satisfaction-tapscript")))enables MAST but only with a slightly different version of the
 Bitcoin Script language than previously used, the new version being
 called _tapscript_.  The major differences include:
 
@@ -1995,7 +1995,7 @@ Additionally, any signature-checking operation that is not expected
 
 Although we've looked at authorization and authentication in depth in
 this chapter, we've skipped over one very important part of how Bitcoin
-authenticates spenders: its signatures.  We'll look at that((("scripts", "MAST", "tapscript", startref="script-mast-tapscript")))((("MAST (merklized alternative script trees)", "tapscript", startref="mast-tapscript")))((("merkle trees", "MAST", "tapscript", startref="merkle-tree-mast-tapscript")))((("tapscript", startref="tapscript")))((("mutual satisfaction contracts", "tapscript", startref="mutual-satisfaction-tapscript"))) next in
+authenticates spenders: its signatures.  We'll look at that((("tapscript", startref="tapscript")))((("mutual satisfaction contracts", "tapscript", startref="mutual-satisfaction-tapscript"))) next in
 <<c_signatures>>.
 
 //FIXME:text "I think more information should be added concerning: tapscript in general. I think the MAST section would better serve to be condensed and integrated in the section on taproot. It should also mention how the taproot merle tree is unique (sorting the leaves, tagged hashes, etc, etc)."