Edited ch08_signatures.adoc with Atlas code editor

ch08_signatures.adoc

@@ -48,7 +48,7 @@ public key.
 
 In Bitcoin's((("digital signatures", "creating"))) use of digital signature algorithms, the "message" being
 signed is the transaction, or more accurately a hash of a specific
-subset of the data in the transaction, called the _commitment hash_ (see
+subset of the data in the transaction, ((("commitment hash")))called the _commitment hash_ (see
 <<sighash_types>>). The
 signing key is the user's private key. The result is the signature:
 
@@ -78,7 +78,7 @@ simpler serialization format is used.
 
 ==== Verifying the Signature
 
-The signature verification algorithm takes the message (a hash of parts of the transaction and related data), the signer's public key and the signature, and returns ++TRUE++ if the signature is valid for this message and public key.
+The((("digital signatures", "verifying")))((("verifying", "digital signatures"))) signature verification algorithm takes the message (a hash of parts of the transaction and related data), the signer's public key and the signature, and returns ++TRUE++ if the signature is valid for this message and public key.
 
 To verify the signature, one must have the signature, the serialized
 transaction, some data about the output being spent, and the public key