chore(blockifier_reexecution): small description fixes (starkware-lib…

…s#3273)

crates/blockifier_reexecution/README.md

@@ -24,9 +24,9 @@ cargo run --bin blockifier_reexecution write-to-file -n <node_url> -d <directory
 ```
 
 - **Offline Reexecution:**
-Reexecution test where the data required for reexecuting the block, as well as the expected resulting state diff, are read from local JSON files. Offline reexecution should be run in release mode, as otherwise these tests can be very long. To run offline reexecution on blocks in the GC bucket, download the files as explained below.
+Reexecution test where the data required for reexecuting the block, as well as the expected resulting state diff, are read from local JSON files. Offline reexecution should be run in release mode, as otherwise these tests can be very long. To run offline reexecution on blocks in the GC bucket, first download the files as explained below. Then run
 ```
-cargo run --release --bin blockifier_reexecution reexecute -n <node_url> -d <directory_path> -b <optional_block_number_1> ... <optional_block_number_n>
+cargo run --release --bin blockifier_reexecution reexecute -d <directory_path> -b <optional_block_number_1> ... <optional_block_number_n>
 ```
 
 ### Downloading Offline Reexecution Files from the GC Bucket

crates/blockifier_reexecution/src/state_reader/reexecution_test.rs

@@ -19,6 +19,7 @@ use crate::state_reader::utils::{get_block_numbers_for_reexecution, reexecute_bl
 #[case::example_l1_handler(868429)]
 #[ignore = "Requires downloading JSON files prior to running; Long test, run with --release flag."]
 fn test_block_reexecution(#[case] block_number: u64) {
+    // Assert that the block number exists in the json file.
     assert!(
         get_block_numbers_for_reexecution(Some("../../".to_owned()))
             .contains(&BlockNumber(block_number))