diff --git a/Makefile b/Makefile
index 564e32843..8392d0017 100644
--- a/Makefile
+++ b/Makefile
@@ -14,7 +14,7 @@ BUILD_PATH_AARCH64 = "target/$(AARCH64_TAG)/release"
 PINNED_NIGHTLY ?= nightly
 CLIPPY_PINNED_NIGHTLY=nightly-2022-05-19
 
-# List of features to use when building natively. Can be overriden via the environment.
+# List of features to use when building natively. Can be overridden via the environment.
 # No jemalloc on Windows
 ifeq ($(OS),Windows_NT)
     FEATURES?=
diff --git a/beacon_node/src/cli.rs b/beacon_node/src/cli.rs
index 73ca5c623..002bb344a 100644
--- a/beacon_node/src/cli.rs
+++ b/beacon_node/src/cli.rs
@@ -1164,7 +1164,7 @@ pub fn cli_app<'a, 'b>() -> App<'a, 'b> {
         .arg(
             Arg::with_name("disable-deposit-contract-sync")
                 .long("disable-deposit-contract-sync")
-                .help("Explictly disables syncing of deposit logs from the execution node. \
+                .help("Explicitly disables syncing of deposit logs from the execution node. \
                       This overrides any previous option that depends on it. \
                       Useful if you intend to run a non-validating beacon node.")
                 .takes_value(false)
diff --git a/beacon_node/src/lib.rs b/beacon_node/src/lib.rs
index cf6d627c3..ee782c650 100644
--- a/beacon_node/src/lib.rs
+++ b/beacon_node/src/lib.rs
@@ -99,7 +99,7 @@ impl<E: EthSpec> ProductionBeaconNode<E> {
                 DatabaseBackendOverride::Success(old_backend) => {
                     info!(
                         log,
-                        "Slasher backend overriden";
+                        "Slasher backend overridden";
                         "reason" => "database exists",
                         "configured_backend" => %old_backend,
                         "override_backend" => %slasher_config.backend,
diff --git a/book/src/help_bn.md b/book/src/help_bn.md
index bb4d7a10c..dff2ab687 100644
--- a/book/src/help_bn.md
+++ b/book/src/help_bn.md
@@ -29,7 +29,7 @@ FLAGS:
                                                contention which degrades staking performance. Stakers should generally
                                                choose to avoid this flag since backfill sync is not required for
                                                staking.
-        --disable-deposit-contract-sync        Explictly disables syncing of deposit logs from the execution node. This
+        --disable-deposit-contract-sync        Explicitly disables syncing of deposit logs from the execution node. This
                                                overrides any previous option that depends on it. Useful if you intend to
                                                run a non-validating beacon node.
         --disable-duplicate-warn-logs          Disable warning logs for duplicate gossip messages. The WARN level log is
diff --git a/book/src/redundancy.md b/book/src/redundancy.md
index 8318aea21..11b984565 100644
--- a/book/src/redundancy.md
+++ b/book/src/redundancy.md
@@ -97,7 +97,7 @@ from this list:
   setup this is the first option we would recommend enabling.
 - `sync-committee`: Send sync committee signatures & aggregates to all beacon nodes. This can
   improve propagation of sync committee messages with similar tradeoffs to broadcasting
-  attestations, although occuring less often due to the infrequency of sync committee duties.
+  attestations, although occurring less often due to the infrequency of sync committee duties.
 - `none`: Disable all broadcasting. This option only has an effect when provided alone, otherwise
    it is ignored. Not recommended except for expert tweakers.
 
diff --git a/book/src/slasher.md b/book/src/slasher.md
index 41bc3baf7..c8506922b 100644
--- a/book/src/slasher.md
+++ b/book/src/slasher.md
@@ -71,7 +71,7 @@ If an MDBX database is already found on disk, then Lighthouse will try to use it
 in a log at start-up:
 
 ```
-INFO Slasher backend overriden    reason: database exists, configured_backend: lmdb, overriden_backend: mdbx
+INFO Slasher backend overridden    reason: database exists, configured_backend: lmdb, overridden_backend: mdbx
 ```
 
 If the running Lighthouse binary doesn't have the MDBX backend enabled but an existing database is
diff --git a/book/src/validator-manager-create.md b/book/src/validator-manager-create.md
index 0cec150da..6ba894a43 100644
--- a/book/src/validator-manager-create.md
+++ b/book/src/validator-manager-create.md
@@ -139,7 +139,7 @@ In order to import the validators, the location of the VC `api-token.txt` file
 must be known. The location of the file varies, but it is located in the
 "validator directory" of your data directory. For example:
 `~/.lighthouse/mainnet/validators/api-token.txt`. We will use `<API-TOKEN-PATH>`
-to subsitute this value. If you are unsure of the `api-token.txt` path, you can run `curl http://localhost:5062/lighthouse/auth` which will show the path.
+to substitute this value. If you are unsure of the `api-token.txt` path, you can run `curl http://localhost:5062/lighthouse/auth` which will show the path.
 
 
 Once the VC is running, use the `import` command to import the validators to the VC:
diff --git a/common/malloc_utils/src/jemalloc.rs b/common/malloc_utils/src/jemalloc.rs
index c796ea39a..92533048c 100644
--- a/common/malloc_utils/src/jemalloc.rs
+++ b/common/malloc_utils/src/jemalloc.rs
@@ -3,7 +3,7 @@
 //! Due to `jemalloc` requiring configuration at compile time or immediately upon runtime
 //! initialisation it is configured via a Cargo config file in `.cargo/config.toml`.
 //!
-//! The `jemalloc` tuning can be overriden by:
+//! The `jemalloc` tuning can be overridden by:
 //!
 //! A) `JEMALLOC_SYS_WITH_MALLOC_CONF` at compile-time.
 //! B) `_RJEM_MALLOC_CONF` at runtime.