From 7bf23584f87eb19085da8d315a3502e564fb19bc Mon Sep 17 00:00:00 2001 From: broccoin <58350903+broccoin-jp@users.noreply.github.com> Date: Wed, 27 Sep 2023 23:08:05 +0900 Subject: [PATCH] fix(website): Correcting broken link Incorrect: https://taiko.xyz/docs/manual/node-runner-manual Correct: https://taiko.xyz/docs/manuals/node-runner-manual --- .../website/pages/docs/reference/node-troubleshooting.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/packages/website/pages/docs/reference/node-troubleshooting.mdx b/packages/website/pages/docs/reference/node-troubleshooting.mdx index acf91c5443..78accb5d21 100644 --- a/packages/website/pages/docs/reference/node-troubleshooting.mdx +++ b/packages/website/pages/docs/reference/node-troubleshooting.mdx @@ -169,7 +169,7 @@ This means that you are not able to connect to the RPC endpoint. Check if you ha #### `WARNING: Found orphan containers` -You should not have orphan containers as the L2 and L3 image container names are different in each docker compose file. Check the [node runner manual](/docs/manual/node-runner-manual) for a command to remove orphan containers. +You should not have orphan containers as the L2 and L3 image container names are different in each docker compose file. Check the [node runner manual](/docs/manuals/node-runner-manual) for a command to remove orphan containers. #### `WARN Snapshot extension registration failed err="peer connected on snap without compatible eth support"` @@ -185,4 +185,4 @@ Copy the default .env file, then reset your RPC node and proposer with the updat Scenario when the mempool is small and proposers are trying to propose the same transactions within an L1 block. The first proposer included on chain will successfully propose these transactions. However, all others proposer included transactions will end up with status `propose empty blocks`, -since the proposed transactions will be filtered by nodes. \ No newline at end of file +since the proposed transactions will be filtered by nodes.