diff --git a/bip-0372.mediawiki b/bip-0372.mediawiki index ee40dd0d..aa37dddf 100644 --- a/bip-0372.mediawiki +++ b/bip-0372.mediawiki @@ -121,7 +121,7 @@ P2C tweaks commit to external data, some of which may represent certain value (like in some sidechains, single-use-seal applications like RGB etc). Creation of such outputs much allow hardware devices to understand the structure of such extra-transaction data, which may be in different formats and constantly -involve. Thus, this should be addresses with a separate standards (or be a +evolve. Thus, this should be addressed with a separate standards (or be a vendor-based). The current proposal only touches the question of spending an output which contained previously created P2C commitment, which does not creates a new commitment and does not provides that kind of risk of extra-blockchain @@ -181,7 +181,7 @@ TBD Timestamping with Bitcoin. [4] Adam Back, Matt Corallo, Luke Dashjr, et al. Enabling Blockchain - Innovations with Pegged Sidechains (commit5620e43). Appenxix A. + Innovations with Pegged Sidechains (commit5620e43). Appendix A. ;. [5] Maxim Orlovsky, Rene Pickhardt, Federico Tenga, et al. Key tweaking: collision- resistant elliptic curve-based commitments. diff --git a/bip-0381.mediawiki b/bip-0381.mediawiki index 8d12c7a4..f2bb8aa7 100644 --- a/bip-0381.mediawiki +++ b/bip-0381.mediawiki @@ -111,7 +111,7 @@ Invalid descriptors * pk() only accepts key expressions: pk(pk(03a34b99f22c790c4e36b2b3c2c35a36db06226e41c692fc82b8b56ac1c540c5bd)) * pkh() only accepts key expressions: pkh(pk(03a34b99f22c790c4e36b2b3c2c35a36db06226e41c692fc82b8b56ac1c540c5bd)) -* sh() only acceps script expressions: sh(03a34b99f22c790c4e36b2b3c2c35a36db06226e41c692fc82b8b56ac1c540c5bd) +* sh() only accepts script expressions: sh(03a34b99f22c790c4e36b2b3c2c35a36db06226e41c692fc82b8b56ac1c540c5bd) * sh() is top level only: sh(sh(pkh(03a34b99f22c790c4e36b2b3c2c35a36db06226e41c692fc82b8b56ac1c540c5bd))) ==Backwards Compatibility==