Fix some typos (#3376)

## Proposed Changes

This PR fixes various minor typos in the project.

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
 

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:

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

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

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:
 

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

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.
 

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.