diff --git a/Modern Hierarchy for Deterministic Multisignature Wallets.mediawiki b/Modern Hierarchy for Deterministic Multisignature Wallets.mediawiki
index 2783cea5..b6079336 100644
--- a/Modern Hierarchy for Deterministic Multisignature Wallets.mediawiki	
+++ b/Modern Hierarchy for Deterministic Multisignature Wallets.mediawiki	
@@ -140,13 +140,13 @@ Expands to the two concrete descriptors:
 
 <code>wsh(sortedmulti(2,[xfpForA/XY'/0'/0']XpubA/1/*,[xfpForB/XY'/0'/0']XpubB/1/*))#Checksum</code>
 
-To discover addresses, scan addresses of the external chain; respect the gap limit described below
+To discover addresses, import both the receiving and change descriptors; 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.
 
 ===Address Gap Limit===
 
-Address gap limit is currently set to 20. If the software hits 20 unused addresses in a row, it expects there are no used addresses beyond this point and stops searching the address chain. We scan just the external chains, because internal chains receive only coins that come from the associated external chains.
+Address gap limit is currently set to 20. If the software hits 20 unused addresses in a row, it expects there are no used addresses beyond this point and stops searching the address chain.
 
 Wallet software should warn when the user is trying to exceed the gap limit on an external chain by generating a new address.