feat(consensus): update README for running milestone 2 (#2190)

Author: matan-starkware

crates/sequencing/papyrus_consensus/README.md

@@ -11,15 +11,19 @@ versions. Breaking changes are expected to happen in the near future.
 2. Start by running any nodes which are validators for `consensus.start_height` which is by default 0 to avoid them missing the proposal.
    1. You can change the default topic by adding: `--consensus.topic "TOPIC"`
 
-Bootstrap Node - this must be run first:
+#### Bootstrap Node
+This must be run first:
 ```
 cargo run --package papyrus_node --bin papyrus_node -- --base_layer.node_url <ETH_NODE_URL> --network.#is_none false --consensus.#is_none false --consensus.validator_id 0x1 --storage.db_config.path_prefix <UNIQUE>
 ```
 - This will log `local_peer_id` which is used by other nodes. (Alternatively pass `network.secret_key` to have a fixed peer id).
 
-Other Nodes - the last run should use `--consensus.validator_id 0x0`.
+#### Other Nodes
+
 ```
 cargo run --package papyrus_node --bin papyrus_node -- --base_layer.node_url <ETH_NODE_URL> --network.#is_none false --consensus.#is_none false --consensus.validator_id 0x<UNIQUE> --network.tcp_port <UNIQUE> --network.bootstrap_peer_multiaddr.#is_none false --rpc.server_address 127.0.0.1:<UNIQUE> --monitoring_gateway.server_address 127.0.0.1:<UNIQUE> --storage.db_config.path_prefix <UNIQUE>  --network.bootstrap_peer_multiaddr /ip4/127.0.0.1/tcp/10000/p2p/<BOOT_NODE_PEER_ID> 
 ```
+- The validator set, (0, 1, 2, 3), is hardcoded in milestone 2.
+- Node 0 is the first proposer and should be run last.
 
 UNIQUE - a value unique among all nodes running locally.