Merge of #837

ZcashFoundation · Jan 15, 2025 · acace26 · acace26
2 parents 8ab55dd + f26d4fe
commit acace26
Show file tree

Hide file tree

Showing 4 changed files with 6 additions and 6 deletions.
diff --git a/book/src/frost.md b/book/src/frost.md
@@ -128,7 +128,7 @@ and Mallory is eventually excluded from the group and replaced with Bob, it is
 not enough to trust 2 out of 3 between Alice, Bob and Eve. **You also need to
 trust that Mallory won't collude with, say, Eve which could have kept her
 original pre-refresh share and they could both together recompute the original
-key and compromise the group.** If that's a unnaceptable risk to your use case,
+key and compromise the group.** If that's an unacceptable risk to your use case,
 you will need to migrate to a new group if that makes sense to your application.
 ```
 

diff --git a/book/src/tutorial/refreshing-shares.md b/book/src/tutorial/refreshing-shares.md
@@ -35,6 +35,6 @@ successfully generating a signature with all of those participants.
 
 ```admonish danger
 Refreshing Shares may be not enough to address security concerns
-after a share has been compromised. Refer to to the [Understanding
+after a share has been compromised. Refer to the [Understanding
 FROST](../frost.md#refreshing-shares) section.
 ```
diff --git a/book/src/tutorial/trusted-dealer.md b/book/src/tutorial/trusted-dealer.md
@@ -40,8 +40,8 @@ You can specify which identifiers to use by using [`IdentifierList::Custom`](htt
 Which [**authenticated** and **confidential** channel](https://frost.zfnd.org/terminology.html#peer-to-peer-channel)
 to use is up to the application. Some examples:
 
-- Manually require the dealer to sent the `SecretShare`s to the
-  partipants using some secure messenger such as Signal;
+- Manually require the dealer to send the `SecretShare`s to the
+  participants using some secure messenger such as Signal;
 - Use a TLS connection, authenticating the server with a certificate
   and the client with some user/password or another suitable authentication
   mechanism;

diff --git a/book/src/zcash/ywallet-demo.md b/book/src/zcash/ywallet-demo.md
@@ -6,7 +6,7 @@ This tutorial explaining how to run the FROST demo using Ywallet that was
 Ywallet supports [offline
 signing](https://ywallet.app/advanced/offline_signature/), which allows having a
 view-only account that can generate a transaction plan, which can be signed by
-a offline wallet also running Ywallet. The demo uses this mechanism but signs
+an offline wallet also running Ywallet. The demo uses this mechanism but signs
 the transaction plan with a command line tool, using FROST.
 
 This tutorial assumes familiarity with the command line.
@@ -88,7 +88,7 @@ another account (or try [ZecFaucet](https://zecfaucet.com/)).
 ```admonish warning
 The address being show by Ywallet is a unified address that includes both an
 Orchard and Sapling address. For the demo to work, you need to receive funds in
-you Orchard address. Whether that will happen depends on multiple factors so
+your Orchard address. Whether that will happen depends on multiple factors so
 it's probably easier to use just the Orchard-only address printed by the signer.
 **If you send it to the Sapling address, the funds will be unspendable and lost!**
 ```