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
index 05e15816e3e..b3ac3676aa4 100644
--- 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
@@ -205,7 +205,9 @@ If you find an error, check the [Node troubleshooting](/docs/reference/node-trou
 
 #### Check with the node dashboard
 
-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).
+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).
+- For a Eldfell L3 node that would default to: [http://localhost:3002/d/L2ExecutionEngine/l2-execution-engine-overview](http://localhost:3002/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.