fix(website): fix port number on node-runner-manual.mdx and run-a-tai…

…ko-node.mdx (#14306) Co-authored-by: Kenk <[email protected]> Co-authored-by: David <[email protected]>
taikoxyz · Jul 28, 2023 · 759ae0c · 759ae0c
1 parent 50ad6f5
commit 759ae0c
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/packages/website/pages/docs/guides/run-a-node/run-a-taiko-node.mdx b/packages/website/pages/docs/guides/run-a-node/run-a-taiko-node.mdx
@@ -163,7 +163,7 @@ docker compose -f ./docker-compose.l3.yml --env-file .env.l3 up -d
 
 ### Verify node is running
 
-A node dashboard will be running on `localhost` on the `GRAFANA_PORT` you set in your `.env` or `.env.l3` file. For a Grimsvotn L2 node that would default to: [http://localhost:3000/d/L2ExecutionEngine/l2-execution-engine-overview](http://localhost:3000/d/L2ExecutionEngine/l2-execution-engine-overview).
+A node dashboard will be running on `localhost` on the `GRAFANA_PORT` you set in your `.env` or `.env.l3` file. For a Grimsvotn L2 node that would default to: [http://localhost:3001/d/L2ExecutionEngine/l2-execution-engine-overview](http://localhost:3001/d/L2ExecutionEngine/l2-execution-engine-overview).
 
 You can verify that your node is syncing by checking the **chain head** on the dashboard and seeing that it is increasing. Once the chain head matches what's on the block explorer, you are fully synced.
 

diff --git a/packages/website/pages/docs/manuals/node-runner-manual.mdx b/packages/website/pages/docs/manuals/node-runner-manual.mdx
@@ -75,13 +75,13 @@ docker compose -f ./docker-compose.l3.yml --env-file .env.l3 down -v
 **Grimsvotn L2:**
 
 ```sh
-open http://localhost:3000/d/L2ExecutionEngine/l2-execution-engine-overview
+open http://localhost:3001/d/L2ExecutionEngine/l2-execution-engine-overview
 ```
 
 **Eldfell L3:**
 
 ```sh
-open http://localhost:3001/d/L2ExecutionEngine/l2-execution-engine-overview
+open http://localhost:3002/d/L2ExecutionEngine/l2-execution-engine-overview
 ```
 
 ## View all logs