Fix batch prover dev docs (#1487)

chainwayxyz · Nov 19, 2024 · 712d0b9 · 712d0b9
1 parent 00306cd
commit 712d0b9
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/docs/run-dev.md b/docs/run-dev.md
@@ -102,10 +102,10 @@ Full node RPC is accessible at `127.0.0.1:12346`
 _Optional_: Run batch prover:
 
 ```sh
-./target/debug/citrea --da-layer bitcoin --rollup-config-path resources/configs/bitcoin-regtest/prover_rollup_config.toml --batch-prover resources/configs/bitcoin-regtest/prover_config.toml --genesis-paths resources/genesis/bitcoin-regtest
+./target/debug/citrea --da-layer bitcoin --rollup-config-path resources/configs/bitcoin-regtest/batch_prover_rollup_config.toml --batch-prover resources/configs/bitcoin-regtest/batch_prover_config.toml --genesis-paths resources/genesis/bitcoin-regtest
 ```
 
-If you want to test proofs, make sure to set `proof_sampling_number` in `resources/configs/bitcion-regtest/batch_prover_config.toml` to 0, and you can lower the `min_soft_confirmations_per_commitment` to a number between 5-50, as higher numbers than that takes too long even if you run the prover in execute mode.
+If you want to test proofs, make sure to set `proof_sampling_number` in `resources/configs/bitcoin-regtest/batch_prover_config.toml` to 0, and you can lower the `min_soft_confirmations_per_commitment` to a number between 5-50, as higher numbers than that takes too long even if you run the prover in execute mode.
 
 To publish blocks on Bitcoin Regtest, run the sequencer with `test_mode` in sequencer config set to false and blocks will be published every two seconds.