chore(docs-site): fix typos in node operator guides (#18586)

Co-authored-by: Roger <50648015+RogerLamTd@users.noreply.github.com>
taikoxyz · Dec 16, 2024 · b4bd23c · b4bd23c
1 parent 38bbb55
commit b4bd23c
Show file tree

Hide file tree

Showing 4 changed files with 4 additions and 4 deletions.
diff --git a/packages/docs-site/src/content/docs/guides/node-operators/node-troubleshooting.mdx b/packages/docs-site/src/content/docs/guides/node-operators/node-troubleshooting.mdx
@@ -84,7 +84,7 @@ This means that you are not able to connect to the RPC endpoint. Check if you ha
 
 ### No contract code at given address
 
-Please ensure your node is running on the correct network and is fully up to date. If the problem still persists, your underlying L1 node is still syncing. Please wait until your L1 node is fully synced before starting your L2 node.
+Please ensure your node is running on the correct network and is fully up-to-date. If the problem still persists, your underlying L1 node is still syncing. Please wait until your L1 node is fully synced before starting your L2 node.
 
 ### Database contains incompatible genesis
 

diff --git a/...src/content/docs/guides/node-operators/run-a-mainnet-taiko-node-from-source.mdx b/...src/content/docs/guides/node-operators/run-a-mainnet-taiko-node-from-source.mdx
@@ -5,7 +5,7 @@ description: This guide will help you start up a Taiko node.
 
 import { Aside, Card, Steps, Tabs, TabItem } from "@astrojs/starlight/components";
 
-This tutorial explains how to run an Taiko node for Mainnet from source code.
+This tutorial explains how to run a Taiko node for Mainnet from source code.
 
 ## Building the Source Code
 

diff --git a/...cs-site/src/content/docs/guides/node-operators/run-a-taiko-node-with-docker.mdx b/...cs-site/src/content/docs/guides/node-operators/run-a-taiko-node-with-docker.mdx
@@ -72,7 +72,7 @@ This guide will help you start up a Taiko RPC node using [simple-taiko-node](htt
 
     It's recommended to [run a local L1 node](/guides/node-operators/run-an-ethereum-testnet-node) but you browse around for other RPC Providers. Keep in mind they will **eventually rate limit your node** and it will stop syncing, so a local L1 node is recommended for a proper setup.
 
-    For Mainnet, the L1 Node will need to be an Ethereum node; for Testnet, the L1 Node will need to be a Etherem testnet (Holesky) node.
+    For Mainnet, the L1 Node will need to be an Ethereum node; for Testnet, the L1 Node will need to be an Etherem testnet (Holesky) node.
     </Aside>
 
     Next, you will set the L1 node endpoints. If you are running a local L1 node, you cannot reference the L1 endpoints as `http://127.0.0.1:8545`, `ws://127.0.0.1:8546` and `http://127.0.0.1:5052` because that is local to inside the simple-taiko-node Docker networking. Instead you can try:

diff --git a/...src/content/docs/guides/node-operators/run-a-testnet-taiko-node-from-source.mdx b/...src/content/docs/guides/node-operators/run-a-testnet-taiko-node-from-source.mdx
@@ -5,7 +5,7 @@ description: This guide will help you start up a Testnet (Hekla) Taiko node.
 
 import { Aside, Card, Steps, Tabs, TabItem } from "@astrojs/starlight/components";
 
-This tutorial explains how to run an Taiko node for our testnet Hekla from source code.
+This tutorial explains how to run a Taiko node for our testnet Hekla from source code.
 
 ## Building the Source Code