Edited ch07_authorization-authentication.adoc with Atlas code editor

ch07_authorization-authentication.adoc

@@ -1349,7 +1349,7 @@ P2WPKH should be constructed by the receiver by converting a compressed
 public key to a P2WPKH hash. Neither the spender nor anyone else should
 ever transform a P2PKH script, Bitcoin address, or uncompressed public
 key to a P2WPKH witness script.  In general, a spender should only send
-to the receiver in the manner that the receiver ((("scripts", "segregated witness", "P2WPKH", startref="script-segwit-p2wpkh")))((("segregated witness (segwit)", "scripts and", "P2WPKH", startref="segwit-script-p2wpkh")))((("P2WPKH (pay to witness public key hash)", startref="p2wpkh")))((("output scripts", "P2WPKH (pay to witness public key hash)", startref="output-script-p2wpkh")))indicated.
+to the receiver in the manner that the receiver indicated.
 ====
 
 [[p2wsh]]
@@ -1431,7 +1431,7 @@ the legacy input script field:
 
 ===== Differentiating between P2WPKH and P2WSH
 
-In the((("scripts", "segregated witness", "P2WPKH")))((("segregated witness (segwit)", "scripts and", "P2WPKH")))((("P2WPKH (pay to witness public key hash)")))((("output scripts", "P2WPKH (pay to witness public key hash)"))) previous two sections, we demonstrated two types of witness
+In the((("scripts", "segregated witness", "P2WPKH", startref="script-segwit-p2wpkh")))((("segregated witness (segwit)", "scripts and", "P2WPKH", startref="segwit-script-p2wpkh")))((("P2WPKH (pay to witness public key hash)", startref="p2wpkh")))((("output scripts", "P2WPKH (pay to witness public key hash)", startref="output-script-p2wpkh"))) previous two sections, we demonstrated two types of witness
 programs: <<p2wpkh>> and <<p2wsh>>. Both types of witness programs
 consist of the same version number followed by a data push. They
 look very similar, but are interpreted very differently: one is