diff options
| author | Alexander Cyon <alex.cyon@gmail.com> | 2024-05-28 19:25:46 +0200 |
|---|---|---|
| committer | Alexander Cyon <alex.cyon@gmail.com> | 2024-05-28 19:25:46 +0200 |
| commit | 1eefea0456d661b4c51f3a40b7262d6a99161edd (patch) | |
| tree | 4f84740d22e4220a8c0488e1932d6ee8b3841547 /bip-0088.mediawiki | |
| parent | e2f7481a132e1c5863f5ffcbff009964d7c2af20 (diff) | |
Fix typos on 17 files.
Diffstat (limited to 'bip-0088.mediawiki')
| -rw-r--r-- | bip-0088.mediawiki | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/bip-0088.mediawiki b/bip-0088.mediawiki index 49be7db..db21835 100644 --- a/bip-0088.mediawiki +++ b/bip-0088.mediawiki @@ -41,7 +41,7 @@ addresses differently than the one they used before. The problem is common enough to warrant the creation of a dedicated website ([https://walletsrecovery.org/ walletsrecovery.org]) that tracks paths used by different wallets. -At the time of writing, this website has used their own format to succintly describe multiple +At the time of writing, this website has used their own format to succinctly describe multiple derivation paths. As far as author knows, it was the only publicitly used format to describe path templates before introduction of this BIP. The format was not specified anywhere beside the main page of the website. It used <code>|</code> to denote alternative derivation indexes @@ -52,7 +52,7 @@ an ad-hoc format only intended for illustration. In contrast to this ad-hoc form described in this BIP is intended for unambigouos parsing by software, and to be easily read by humans at the same time. Humans can visually detect the 'templated' parts of the path more easily than the use of <code>|</code> in the template could allow. Wider range of paths can be defined in a single template more -succintly and unambiguously. +succinctly and unambiguously. ===Intended use and advantages=== @@ -71,7 +71,7 @@ into using well-known paths, or convince other vendors to support their custom p scales poorly. A flexible approach proposed in this document is to define a standard notation for "BIP32 path templates" -that succintly describes the constraints to impose on the derivation path. +that succinctly describes the constraints to impose on the derivation path. Wide support for these path templates will increase interoperability and flexibility of solutions, and will allow vendors and individual developers to easily define their own custom restrictions. @@ -89,7 +89,7 @@ installation of malicious or incorrect profiles, though. ==Specification== -The format for the template was chosen to make it easy to read, convenient and visually unambigous. +The format for the template was chosen to make it easy to read, convenient and visually unambiguous. Template starts with optional prefix <code>m/</code>, and then one or more sections delimited by the slash character (<code>/</code>). |