Edited ch07_authorization-authentication.adoc with Atlas code editor

ch07_authorization-authentication.adoc

@@ -468,7 +468,7 @@ workaround to an oddity in the ((("scripts", "multisignature", startref="script-
 [[p2sh]]
 === Pay to Script Hash
 
-Pay to script hash (P2SH) was((("scripts", "P2SH (pay to script hash)", id="script-p2sh")))((("P2SH (pay to script hash)", id="p2sh-ch7")))
+Pay to script hash (P2SH) was((("scripts", "P2SH (pay to script hash)", id="script-p2sh")))((("addresses", "P2SH (pay to script hash)", id="address-p2sh-ch7")))((("P2SH (pay to script hash)", id="p2sh-ch7")))
 introduced in 2012 as a powerful new type of operation that greatly
 simplifies the use of complex scripts. To explain the need
 for P2SH, let's look at a practical example.
@@ -618,7 +618,7 @@ If the redeem script hash matches, the redeem script is executed:
 ==== P2SH Addresses
 
 Another
-important ((("addresses", "P2SH (pay to script hash)")))part of the P2SH feature is the ability to encode a script
+important part of the P2SH feature is the ability to encode a script
 hash as an address, as defined in BIP13. P2SH addresses are base58check
 encodings of the 20-byte hash of a script, just like Bitcoin addresses
 are base58check encodings of the 20-byte hash of a public key. P2SH
@@ -680,7 +680,7 @@ P2SH output scripts
 contain the hash of a redeem script, which gives no clues as to
 the content of the redeem script. The P2SH output will be
 considered valid and accepted even if the redeem script is invalid. You
-might accidentally receive bitcoin in such a way that it cannot later((("scripts", "P2SH (pay to script hash)", startref="script-p2sh")))((("P2SH (pay to script hash)", startref="p2sh-ch7"))) be
+might accidentally receive bitcoin in such a way that it cannot later((("scripts", "P2SH (pay to script hash)", startref="script-p2sh")))((("P2SH (pay to script hash)", startref="p2sh-ch7")))((("addresses", "P2SH (pay to script hash)", startref="address-p2sh-ch7"))) be
 spent.
 ====