diff --git a/Modern Hierarchy for Deterministic Multisignature Wallets.mediawiki b/Modern Hierarchy for Deterministic Multisignature Wallets.mediawiki
index 391b88a2..6be0a65d 100644
--- a/Modern Hierarchy for Deterministic Multisignature Wallets.mediawiki	
+++ b/Modern Hierarchy for Deterministic Multisignature Wallets.mediawiki	
@@ -129,14 +129,16 @@ The multisig descriptors or descriptor template that is generated from the cosig
 For example:
 
 The following descriptor template and derivation path:
+
 <code>wsh(sortedmulti(2,[xfpForA/XY'/0'/0']XpubA/**,[xfpForB/XY'/0'/0']XpubB/**))</code>
 <code>/0/*,/1/*</code>
 
 Expands to the two concrete descriptors:
+
 <code>wsh(sortedmulti(2,[xfpForA/XY'/0'/0']XpubA/0/*,[xfpForB/XY'/0'/0']XpubB/0/*))#Checksum</code>
 <code>wsh(sortedmulti(2,[xfpForA/XY'/0'/0']XpubA/1/*,[xfpForB/XY'/0'/0']XpubB/1/*))#Checksum</code>
 
-# Scan addresses of the external chain; respect the gap limit described below
+To discover addresses, scan addresses of the external chain; respect the gap limit described below
 
 Note: This therefore necessitates that multisig wallets backup their private key information and their descriptor, in order to properly restore at a later time.  This shouldn't be a user burden, since (to much user surprise), all cosigner public keys need to be supplied in addition to <code>M</code> seeds in any <code>M</code> of <code>N</code> multisig restore operation. The descriptor provides this information in a standardized format, with key origin information and error detection.