diff --git a/beacon_node/beacon_chain/src/early_attester_cache.rs b/beacon_node/beacon_chain/src/early_attester_cache.rs index 62b584968..1ddbe1324 100644 --- a/beacon_node/beacon_chain/src/early_attester_cache.rs +++ b/beacon_node/beacon_chain/src/early_attester_cache.rs @@ -86,7 +86,7 @@ impl EarlyAttesterCache { /// /// - There is a cache `item` present. /// - If `request_slot` is in the same epoch as `item.epoch`. - /// - If `request_index` does not exceed `item.comittee_count`. + /// - If `request_index` does not exceed `item.committee_count`. pub fn try_attest( &self, request_slot: Slot, diff --git a/beacon_node/lighthouse_network/src/behaviour/gossip_cache.rs b/beacon_node/lighthouse_network/src/behaviour/gossip_cache.rs index 93687e555..4842605f7 100644 --- a/beacon_node/lighthouse_network/src/behaviour/gossip_cache.rs +++ b/beacon_node/lighthouse_network/src/behaviour/gossip_cache.rs @@ -30,9 +30,9 @@ pub struct GossipCache { proposer_slashing: Option, /// Timeout for attester slashings. attester_slashing: Option, - /// Timeout for aggregated sync commitee signatures. + /// Timeout for aggregated sync committee signatures. signed_contribution_and_proof: Option, - /// Timeout for sync commitee messages. + /// Timeout for sync committee messages. sync_committee_message: Option, } @@ -51,9 +51,9 @@ pub struct GossipCacheBuilder { proposer_slashing: Option, /// Timeout for attester slashings. attester_slashing: Option, - /// Timeout for aggregated sync commitee signatures. + /// Timeout for aggregated sync committee signatures. signed_contribution_and_proof: Option, - /// Timeout for sync commitee messages. + /// Timeout for sync committee messages. sync_committee_message: Option, } @@ -101,13 +101,13 @@ impl GossipCacheBuilder { self } - /// Timeout for aggregated sync commitee signatures. + /// Timeout for aggregated sync committee signatures. pub fn signed_contribution_and_proof_timeout(mut self, timeout: Duration) -> Self { self.signed_contribution_and_proof = Some(timeout); self } - /// Timeout for sync commitee messages. + /// Timeout for sync committee messages. pub fn sync_committee_message_timeout(mut self, timeout: Duration) -> Self { self.sync_committee_message = Some(timeout); self diff --git a/beacon_node/network/src/service.rs b/beacon_node/network/src/service.rs index c21183608..9e3302af2 100644 --- a/beacon_node/network/src/service.rs +++ b/beacon_node/network/src/service.rs @@ -362,7 +362,7 @@ impl NetworkService { Some(msg) = self.attestation_service.next() => self.on_attestation_service_msg(msg), // process any sync committee service events - Some(msg) = self.sync_committee_service.next() => self.on_sync_commitee_service_message(msg), + Some(msg) = self.sync_committee_service.next() => self.on_sync_committee_service_message(msg), event = self.libp2p.next_event() => self.on_libp2p_event(event, &mut shutdown_sender).await, @@ -774,7 +774,7 @@ impl NetworkService { } } - fn on_sync_commitee_service_message(&mut self, msg: SubnetServiceMessage) { + fn on_sync_committee_service_message(&mut self, msg: SubnetServiceMessage) { match msg { SubnetServiceMessage::Subscribe(subnet) => { for fork_digest in self.required_gossip_fork_digests() { diff --git a/book/src/contributing.md b/book/src/contributing.md index 9204ff846..4b21d1ecf 100644 --- a/book/src/contributing.md +++ b/book/src/contributing.md @@ -33,7 +33,7 @@ Lighthouse maintains two permanent branches: - [`stable`][stable]: Always points to the latest stable release. - This is ideal for most users. - [`unstable`][unstable]: Used for development, contains the latest PRs. - - Developers should base thier PRs on this branch. + - Developers should base their PRs on this branch. ## Ethereum consensus client diff --git a/book/src/docker.md b/book/src/docker.md index 9a0378f09..f22b8a200 100644 --- a/book/src/docker.md +++ b/book/src/docker.md @@ -73,7 +73,7 @@ The `stability` is: The `arch` is: * `-amd64` for x86_64, e.g. Intel, AMD -* `-arm64` for aarch64, e.g. Rasperry Pi 4 +* `-arm64` for aarch64, e.g. Raspberry Pi 4 * empty for a multi-arch image (works on either `amd64` or `arm64` platforms) The `modernity` is: diff --git a/book/src/installation.md b/book/src/installation.md index 38fbe6b78..e222c401a 100644 --- a/book/src/installation.md +++ b/book/src/installation.md @@ -14,7 +14,7 @@ The community maintains additional installation methods (currently only one). Additionally, there are two extra guides for specific uses: -- [Rapsberry Pi 4 guide](./pi.md). +- [Raspberry Pi 4 guide](./pi.md). - [Cross-compiling guide for developers](./cross-compiling.md). ## Minimum System Requirements diff --git a/book/src/mainnet-validator.md b/book/src/mainnet-validator.md index 0f91b8e27..41735f85b 100644 --- a/book/src/mainnet-validator.md +++ b/book/src/mainnet-validator.md @@ -34,7 +34,7 @@ Remember, if you get stuck you can always reach out on our [Discord][discord]. > > **Please note**: the Lighthouse team does not take any responsibility for losses or damages -> occured through the use of Lighthouse. We have an experienced internal security team and have +> occurred through the use of Lighthouse. We have an experienced internal security team and have > undergone multiple third-party security-reviews, however the possibility of bugs or malicious > interference remains a real and constant threat. Validators should be prepared to lose some rewards > due to the actions of other actors on the consensus layer or software bugs. See the diff --git a/book/src/setup.md b/book/src/setup.md index dfff9290e..e8c56623b 100644 --- a/book/src/setup.md +++ b/book/src/setup.md @@ -19,7 +19,7 @@ The additional requirements for developers are: ## Using `make` -Commands to run the test suite are avaiable via the `Makefile` in the +Commands to run the test suite are available via the `Makefile` in the project root for the benefit of CI/CD. We list some of these commands below so you can run them locally and avoid CI failures: diff --git a/book/src/slasher.md b/book/src/slasher.md index 05107238c..889f9c6cb 100644 --- a/book/src/slasher.md +++ b/book/src/slasher.md @@ -1,6 +1,6 @@ # Running a Slasher -Lighthouse includes a slasher for identifying slashable offences comitted by other validators and +Lighthouse includes a slasher for identifying slashable offences committed by other validators and including proof of those offences in blocks. Running a slasher is a good way to contribute to the health of the network, and doing so can earn @@ -69,7 +69,7 @@ The slasher uses MDBX as its backing store, which places a hard limit on the siz file. You can use the `--slasher-max-db-size` flag to set this limit. It can be adjusted after initialization if the limit is reached. -By default the limit is set to accomodate the default history length and around 300K validators but +By default the limit is set to accommodate the default history length and around 300K validators but you can set it lower if running with a reduced history length. The space required scales approximately linearly in validator count and history length, i.e. if you halve either you can halve the space required. @@ -134,7 +134,7 @@ the slot duration. ### Chunk Size and Validator Chunk Size * Flags: `--slasher-chunk-size EPOCHS`, `--slasher-validator-chunk-size NUM_VALIDATORS` -* Arguments: number of ecochs, number of validators +* Arguments: number of epochs, number of validators * Defaults: 16, 256 Adjusting these parameter should only be done in conjunction with reading in detail diff --git a/book/src/slashing-protection.md b/book/src/slashing-protection.md index 9ae6c102e..a60c8e36d 100644 --- a/book/src/slashing-protection.md +++ b/book/src/slashing-protection.md @@ -54,7 +54,7 @@ Examples where it is **ineffective** are: clients (e.g. Lighthouse and Prysm) running on the same machine, two Lighthouse instances using different datadirs, or two clients on completely different machines (e.g. one on a cloud server and one running locally). You are responsible for ensuring that your validator keys are never - running simultanously – the slashing protection DB **cannot protect you in this case**. + running simultaneously – the slashing protection DB **cannot protect you in this case**. * Importing keys from another client without also importing voting history. * If you use `--init-slashing-protection` to recreate a missing slashing protection database. diff --git a/book/src/validator-import-launchpad.md b/book/src/validator-import-launchpad.md index aee9ac7b9..9849b91b7 100644 --- a/book/src/validator-import-launchpad.md +++ b/book/src/validator-import-launchpad.md @@ -1,6 +1,6 @@ # Importing from the Ethereum Staking Launch pad -The [Staking Lauchpad](https://github.com/ethereum/eth2.0-deposit) is a website +The [Staking Launchpad](https://github.com/ethereum/eth2.0-deposit) is a website from the Ethereum Foundation which guides users how to use the [`eth2.0-deposit-cli`](https://github.com/ethereum/eth2.0-deposit-cli) command-line program to generate consensus validator keys. diff --git a/common/eth2_network_config/built_in_network_configs/kiln/config.yaml b/common/eth2_network_config/built_in_network_configs/kiln/config.yaml index 797c0672c..5631c8a0b 100644 --- a/common/eth2_network_config/built_in_network_configs/kiln/config.yaml +++ b/common/eth2_network_config/built_in_network_configs/kiln/config.yaml @@ -6,7 +6,7 @@ PRESET_BASE: 'mainnet' MIN_GENESIS_ACTIVE_VALIDATOR_COUNT: 95000 # Mar 11th, 2022, 14:00 UTC MIN_GENESIS_TIME: 1647007200 -# Gensis fork +# Genesis fork GENESIS_FORK_VERSION: 0x70000069 # 300 seconds (5 min) GENESIS_DELAY: 300 diff --git a/consensus/state_processing/src/per_block_processing/tests.rs b/consensus/state_processing/src/per_block_processing/tests.rs index 2daefdaca..2a84d1d2d 100644 --- a/consensus/state_processing/src/per_block_processing/tests.rs +++ b/consensus/state_processing/src/per_block_processing/tests.rs @@ -394,7 +394,7 @@ async fn invalid_attestation_no_committee_for_index() { &spec, ); - // Expecting NoCommitee because we manually set the attestation's index to be invalid + // Expecting NoCommittee because we manually set the attestation's index to be invalid assert_eq!( result, Err(BlockProcessingError::AttestationInvalid { @@ -471,7 +471,7 @@ async fn invalid_attestation_bad_aggregation_bitfield_len() { &spec, ); - // Expecting InvalidBitfield because the size of the aggregation_bitfield is bigger than the commitee size. + // Expecting InvalidBitfield because the size of the aggregation_bitfield is bigger than the committee size. assert_eq!( result, Err(BlockProcessingError::BeaconStateError( diff --git a/scripts/local_testnet/vars.env b/scripts/local_testnet/vars.env index efb104645..b6ea89794 100644 --- a/scripts/local_testnet/vars.env +++ b/scripts/local_testnet/vars.env @@ -18,7 +18,7 @@ GENESIS_VALIDATOR_COUNT=80 # Number of beacon_node instances that you intend to run BN_COUNT=4 -# Number of valicator clients +# Number of validator clients VC_COUNT=$BN_COUNT # Number of seconds to delay to start genesis block. diff --git a/scripts/tests/vars.env b/scripts/tests/vars.env index d51fe2aef..376fe3d8c 100644 --- a/scripts/tests/vars.env +++ b/scripts/tests/vars.env @@ -18,7 +18,7 @@ GENESIS_VALIDATOR_COUNT=80 # Number of beacon_node instances that you intend to run BN_COUNT=4 -# Number of valicator clients +# Number of validator clients VC_COUNT=$BN_COUNT # Number of seconds to delay to start genesis block. diff --git a/validator_client/src/lib.rs b/validator_client/src/lib.rs index 1baa9f6bb..f10142d61 100644 --- a/validator_client/src/lib.rs +++ b/validator_client/src/lib.rs @@ -440,7 +440,7 @@ impl ProductionValidatorClient { context.service_context("sync_committee".into()), ); - // Wait until genesis has occured. + // Wait until genesis has occurred. // // It seems most sensible to move this into the `start_service` function, but I'm caution // of making too many changes this close to genesis (<1 week).