docs: fix typos (#5689)

* fix typos

* fix typos

* fix typo

* fix typo

Author: omahs

docs/block_flow.md

@@ -78,7 +78,7 @@ Blocks are considered trusted if they come from:
 
 A block with a valid cryptographic signature is considered SigVerified.
 This is a weaker guarantee than Trusted as the block might still be invalid according to the state transition function.
-Such a block are produced if incoming gossip blocks' signatures are batched together for batch verification **before** being passed to state transition.
+Such a block is produced if incoming gossip blocks' signatures are batched together for batch verification **before** being passed to state transition.
 
 #### TransitionVerifiedBeaconBlocks
 
@@ -149,7 +149,7 @@ There is no backpressure handling at the RequestManager and Gossip level with re
 
 There is backpressure handling at the Quarantine level:
 - Blocks in the SharedBlockQueue that are missing parents
-  are put in quarantine, only 16 can be stored and new candidate are dropped as long as the older ones are unresolved.
+  are put in quarantine, only 16 can be stored and new candidates are dropped as long as the older ones are unresolved.
 
 ##### Latency & Throughput sensitiveness
 

docs/cpu_features.md

@@ -75,7 +75,7 @@ nim c -r -d:danger --passC:"-mbmi2 -madx" --hints:off --warnings:off --verbosity
 ```
 
 **Verification** is the bottleneck as it must be done for each block and attestation or aggregate received
-and verifying a block requires verifying up to 6 signatures (block proposer, RANDAO, aggregate verifification of attestations, proposer slashings, attester slashings, voluntary exits).
+and verifying a block requires verifying up to 6 signatures (block proposer, RANDAO, aggregate verification of attestations, proposer slashings, attester slashings, voluntary exits).
 **Signing** can become a bottleneck when a node has many validators.
 
 **Without BMI2 & ADX**
@@ -104,7 +104,7 @@ Serial batch verify 6 msgs by 6 pubkeys (with blinding)  282.562 ops/s      3539
 
 ### SHA-NI
 
-The hardware SHA instructions has NOT been available in Intel consumer hardware until 2021.
+The hardware SHA instructions have NOT been available in Intel consumer hardware until 2021.
 AMD has made it available in Zen architecture since 2017.
 
 Intel:

docs/the_nimbus_book/src/faq.md

@@ -317,7 +317,7 @@ As such, it's a good idea to create your keys from mnemonics which act as anothe
 This will be the default for validators who join via this site's onboarding process.
 
 If the validator can no longer propose or attest, their balance will decrease over time as they are punished for not participating in the consensus process.
-When the validator's balance reaches 16 ETH, they will be automatically exited from the validator pool, and 16 ETH will be transfered to their withdrawal address (as long it's specified).
+When the validator's balance reaches 16 ETH, they will be automatically exited from the validator pool, and 16 ETH will be transferred to their withdrawal address (as long it's specified).
 
 !!! note
     After the Capella hard-fork, activated on 12th of April 2023, all exited validators that use `0x01` withdrawal credentials will have their funds automatically withdrawn.

installer/macos/README.md

@@ -1,7 +1,7 @@
 This directory contains a set of files used for building a PKG macOS
 installation package for the Nimbus beacon node.
 
-To build the package, you'll need XCode and and the "Packages" tool freeware
+To build the package, you'll need XCode and the "Packages" tool freeware
 developer tool from:
 http://s.sudre.free.fr/Software/Packages/about.html