diff --git a/.wordlist.txt b/.wordlist.txt
index 7aef3a7277d2..83d2bd51aa73 100644
--- a/.wordlist.txt
+++ b/.wordlist.txt
@@ -109,7 +109,7 @@ nodemodule
 overriden
 params
 plaintext
-produceBlockV3
+produceBlockV
 prover
 req
 reqresp
diff --git a/docs/usage/beacon-management.md b/docs/usage/beacon-management.md
index 5536fbb78a5b..7da97d253f2b 100644
--- a/docs/usage/beacon-management.md
+++ b/docs/usage/beacon-management.md
@@ -101,7 +101,7 @@ A young testnet should take a few hours to sync. If you see multiple or consiste
 
 ### Checkpoint Sync
 
-If you are starting your node from a blank db, like starting from genesis, or from the last saved state in db and the network is now far ahead, your node will be susceptible to "long range attacks."  Ethereum's solution to this is via something called weak subjectivity. [Read Vitalik's illuminating post explaining weak subjectivity.](https://blog.ethereum.org/2014/11/25/proof-stake-learned-love-weak-subjectivity/).
+If you are starting your node from a blank db, like starting from genesis, or from the last saved state in db and the network is now far ahead, your node will be susceptible to "long range attacks." Ethereum's solution to this is via something called weak subjectivity. [Read Vitalik's illuminating post explaining weak subjectivity.](https://blog.ethereum.org/2014/11/25/proof-stake-learned-love-weak-subjectivity/).
 
 If you have a synced beacon node available (e.g., your friend's node or an infrastructure provider) and a trusted checkpoint you can rely on, you can start off your beacon node in under a minute! And at the same time kicking the "long range attack" in its butt!