From 47847fe874764a0ffc9addbcfc692e5199a7339d Mon Sep 17 00:00:00 2001
From: Hugo Nguyen <hugh.hn@gmail.com>
Date: Tue, 11 May 2021 03:36:32 -0700
Subject: minor edit

---
 bip-hugonguyen-bsms.mediawiki | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

(limited to 'bip-hugonguyen-bsms.mediawiki')

diff --git a/bip-hugonguyen-bsms.mediawiki b/bip-hugonguyen-bsms.mediawiki
index 5d9ef85..d34a42f 100644
--- a/bip-hugonguyen-bsms.mediawiki
+++ b/bip-hugonguyen-bsms.mediawiki
@@ -187,13 +187,11 @@ Also refer to [https://github.com/BlockchainCommons/Research/blob/master/papers/
 ==Compatibility==
 This specification is not backwards compatible with existing multisig implementations.
 
-BSMS is opt-in, meaning existing multisig implementations can continue working as-is, with the caveat that they are full of pitfalls. Some of the problems have been described in the [[#Motivation]] section.
+BSMS is opt-in, meaning existing multisig implementations can continue working as-is, with the caveat that they are likely to have various pitfalls. Some of the problems with existing solutions have been described in the [[#Motivation]] section.
 
 To comply with this standard, a Signer must be able to persist the descriptor record in its storage.
 
-Once a Signer has implemented BSMS, the user can create new multisig wallets using BSMS or migrate existing ones to BSMS.
-
-Existing multisig wallets should delay upgrading to BSMS until all participating Signers have implemented BSMS.
+To use BSMS for a multisig wallet, the user should wait until all participating Signers in the multisig have implemented BSMS.
 
 ==Security==
 
-- 
cgit v1.2.3

