Fix typos

book/src/tutorial/refreshing-shares.md

@@ -30,7 +30,7 @@ The refreshed `KeyPackage` contents must be stored securely and the original
 Applications should first ensure that all participants who refreshed their
 `KeyPackages` were actually able to do so successfully, before deleting their old
 `KeyPackages`. How this is done is up to the application; it might require
-sucessfully generating a signature with all of those participants.
+successfully generating a signature with all of those participants.
 ```
 
 ```admonish danger

book/src/zcash/ywallet-demo.md

@@ -37,9 +37,9 @@ cargo run --bin trusted-dealer -- -C redpallas
 
 This will by default generate a 2-of-3 key shares. The public key package
 will be written to `public-key-package.json`, while key packages will be
-written to `key-package-1.json` through `-3`. You can change the threhsold,
+written to `key-package-1.json` through `-3`. You can change the threshold,
 number of shares and file names using the command line; append `-- -h`
-to the commend above for the command line help.
+to the command above for the command line help.
 
 ```admonish info
 If you want to use DKG instead of Trusted Dealer, instead of the command above,
@@ -198,7 +198,7 @@ cargo run --bin participant -- -C redpallas --http --key-package key-package-1.j
 ```
 
 (We are using "alice" again. There's nothing stopping a Coordinator from being a
-Partcipant too!)
+Participant too!)
 
 ### Participant 2 (bob)
 
@@ -212,7 +212,7 @@ cargo run --bin participant -- -C redpallas --http --key-package key-package-2.j
 ### Coordinator
 
 Go back to the Coordinator CLI. The protocol should run and complete
-succesfully. It will print the final FROST-generated signature. Hurrah! Copy it
+successfully. It will print the final FROST-generated signature. Hurrah! Copy it
 (just the hex value).
 
 Go back to the signer and paste the signature. It will write the raw signed

frost-core/src/keys.rs

@@ -319,7 +319,7 @@ where
         Self(coefficients)
     }
 
-    /// Returns serialized coefficent commitments
+    /// Returns serialized coefficient commitments
     pub fn serialize(&self) -> Result<Vec<Vec<u8>>, Error<C>> {
         self.0
             .iter()

frost-core/src/lib.rs

@@ -419,7 +419,7 @@ where
     ) -> Result<Vec<(Identifier<C>, Vec<u8>)>, Error<C>> {
         let mut binding_factor_input_prefix = Vec::new();
 
-        // The length of a serialized verifying key of the same cipersuite does
+        // The length of a serialized verifying key of the same ciphersuite does
         // not change between runs of the protocol, so we don't need to hash to
         // get a fixed length.
         binding_factor_input_prefix.extend_from_slice(verifying_key.serialize()?.as_ref());

frost-core/src/scalar_mul.rs

@@ -1,4 +1,4 @@
-//! Non-adjacent form (NAF) implementations for fast batch scalar multiplcation
+//! Non-adjacent form (NAF) implementations for fast batch scalar multiplication
 
 // We expect slicings in this module to never panic due to algorithmic
 // constraints.

frost-core/src/tests/refresh.rs

@@ -396,7 +396,7 @@ where
         received_round2_packages.clone(),
     );
 
-    // For each participant, this is where they refresh thair shares
+    // For each participant, this is where they refresh their shares
     // In practice, each participant will perform this on their own environments.
     for participant_identifier in remaining_ids.clone() {
         let (key_package, pubkey_package_for_participant) =

frost-core/src/traits.rs

@@ -225,7 +225,7 @@ pub trait Ciphersuite: Copy + Clone + PartialEq + Debug + 'static {
     // protocol if required.
 
     /// Optional. Do regular (non-FROST) signing with a [`SigningKey`]. Called
-    /// by [`SigningKey::sign()`]. This is not used by FROST. Can be overriden
+    /// by [`SigningKey::sign()`]. This is not used by FROST. Can be overridden
     /// if required which is useful if FROST signing has been changed by the
     /// other Ciphersuite trait methods and regular signing should be changed
     /// accordingly to match.