Correct a couple years of accumulated typos

This commit is contained in:
Luke Parker
2023-12-17 02:06:51 -05:00
parent 9c3329abeb
commit c2fffb9887
40 changed files with 63 additions and 63 deletions

View File

@@ -140,7 +140,7 @@ async fn potentially_cosign_block(
// If we skipped a block, we're supposed to sign it plus the COSIGN_DISTANCE if no other blocks
// trigger a cosigning protocol covering it
// This means there will be the maximum delay allowed from a block needing cosigning occuring
// This means there will be the maximum delay allowed from a block needing cosigning occurring
// and a cosign for it triggering
let maximally_latent_cosign_block =
skipped_block.map(|skipped_block| skipped_block + COSIGN_DISTANCE);

View File

@@ -42,7 +42,7 @@ pub fn dkg_confirmation_nonces(
.preprocess()
}
// If there's an error generating a key pair, return any errors which would've occured when
// If there's an error generating a key pair, return any errors which would've occurred when
// executing the DkgConfirmer in order to stay in sync with those who did.
//
// The caller must ensure only error_generating_key_pair or generated_key_pair is called for a

View File

@@ -38,7 +38,7 @@
only way to operate on distinct received messages would be if:
1) A logical flaw exists, letting new messages over write prior messages
2) A reorganization occured from chain A to chain B, and with it, different messages
2) A reorganization occurred from chain A to chain B, and with it, different messages
Reorganizations are not supported, as BFT is assumed by the presence of a BFT algorithm. While
a significant amount of processes may be byzantine, leading to BFT being broken, that still will

View File

@@ -74,7 +74,7 @@ fn invalid_block() {
assert!(blockchain.verify_block::<N>(&block, &validators, false).is_err());
}
// Mutate tranactions merkle
// Mutate transactions merkle
{
let mut block = block;
block.header.transactions = Blake2s256::digest(block.header.transactions).into();