tutorial: minor fix wrt test node config path

Closes: aptos-labs#453
OlPanche · Apr 8, 2022 · f96546e · f96546e
1 parent 7af7ffe
commit f96546e
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/aptos-node/src/lib.rs b/aptos-node/src/lib.rs
@@ -202,7 +202,7 @@ pub fn load_test_environment<R>(
 
     println!("Completed generating configuration:");
     println!("\tLog file: {:?}", log_file);
-    println!("\tConfig path: {:?}", validator_config_path);
+    println!("\tConfig path: {:?}", config_path);
     println!("\tAptos root key path: {:?}", aptos_root_key_path);
     println!("\tWaypoint: {}", config.base.waypoint.genesis_waypoint());
     println!("\tChainId: {}", ChainId::test());

diff --git a/developer-docs-site/docs/tutorials/run-a-local-testnet.md b/developer-docs-site/docs/tutorials/run-a-local-testnet.md
@@ -31,7 +31,7 @@ We describe each method below.
     ./scripts/dev_setup.sh
     source ~/.cargo/env
     ```
-2. Run the command: `cargo run -p aptos-node -- --test`. After starting up, the process should print its config path (e.g., `/private/var/folders/36/w0v54r116ls44q29wh8db0mh0000gn/T/f62a72f87940e3892a860c21b55b529b/0/node.yaml`) and other metadata.
+2. Run the command: `cargo run -p aptos-node -- --test`. After starting up, the process should print its config path (e.g., `/private/var/folders/36/w0v54r116ls44q29wh8db0mh0000gn/T/f62a72f87940e3892a860c21b55b529b`) and other metadata.
 
 Note: this command runs `aptos-node` from a genesis-only ledger state. If you want to reuse the ledger state produced by a previous run of `aptos-node`, use `cargo run -p aptos-node -- --test --config <config-path>`.