From c44ed8e185fd3709dc3bc1bb58b52880b0ffb6a8 Mon Sep 17 00:00:00 2001
From: ImStaked <82274336+ImStaked@users.noreply.github.com>
Date: Thu, 2 Jan 2025 02:15:43 -0600
Subject: [PATCH] Update runtime override operate path (#115)

Because the current directory is /run-evm-tracing-node/darwinia-release the correct relative path is ../overridden-runtimes.
---
 docs/node-operators/run-evm-tracing-node.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/node-operators/run-evm-tracing-node.md b/docs/node-operators/run-evm-tracing-node.md
index 9e30b41..8176888 100644
--- a/docs/node-operators/run-evm-tracing-node.md
+++ b/docs/node-operators/run-evm-tracing-node.md
@@ -43,7 +43,7 @@ As you may be aware, Darwinia chains are EVM compatible, which means that the RP
     # Check out the corresponding network branch
     git checkout origin/darwinia
     # Copy the wasm runtime files to the temporary workaround override runtime location 
-    cp wasm/evm-tracing/* ../run-evm-tracing-node/overridden-runtimes/
+    cp wasm/evm-tracing/* ../overridden-runtimes/
     ```
     
     The `wasm-runtime-overrides` repository has five branches, each corresponding to one of the four Darwinia chains. You will need to switch to the branch that corresponds to your desired network and copy the `wasm` directory to your temporary workaround location. In this tutorial, we will use the `darwinia` branch.
@@ -144,4 +144,4 @@ As you may be aware, Darwinia chains are EVM compatible, which means that the RP
     2024-09-27 06:58:28 [Parachain] discovered: 12D3KooWDajBn6V4j8Hq5j2yG2H3q16ztZ7wZ9Qg6NoitGr6XYBz /ip4/172.20.0.2/tcp/30334/ws
     2024-09-27 06:58:28 [Relaychain] discovered: 12D3KooWRyXoStSmNnVZjCoQsitLwruKcc6e7mu5dQAnA4CXVMhk /ip4/172.20.0.2/tcp/30333/ws
     2024-09-27 06:58:28 [Relaychain] Sending fatal alert BadCertificate
-    ```
\ No newline at end of file
+    ```