Apply suggestions from code review

Co-authored-by: Amin Sammara <[email protected]>

Author: sklppy88

docs/versioned_docs/version-v1.2.0/the_aztec_network/guides/run_nodes/how_to_run_sequencer_new.md

@@ -32,7 +32,7 @@ The sequencer node takes part in three key actions:
 2. Attest to correct execution of txs in the proposed block (if part of validator committee)
 3. Submit the successfully attested block to L1
 
-When transactions are sent to the Aztec network, sequencer nodes bundles them into blocks, checking various constraints such as gas limits, block size, and transaction validity. Before a block can be published, it must be validated by a committee of other sequencer nodes (validators in this context) who re-execute public transactions and verify private function proofs so they can attest to correct execution. These validators attest to the block's validity by signing it, and once enough attestations are collected (two-thirds of the committee plus one), the sequencer can submit the block to L1.
+When transactions are sent to the Aztec network, sequencer nodes bundles them into blocks, checking various constraints such as gas limits, block size, and transaction validity. Before a block can be published, it must be validated by a committee of other sequencer nodes (validators in this context) who re-execute public transactions and verify private function proofs so they can attest to correct execution. These validators attest to the block's validity by signing the block header, and once enough attestations are collected (two-thirds of the committee plus one), the sequencer can submit the block to L1.
 
 The archiver component complements this process by maintaining historical chain data. It continuously monitors L1 for new blocks, processes them, and maintains a synchronized view of the chain state. This includes managing contract data, transaction logs, and L1-to-L2 messages, making it essential for network synchronization and data availability.
 
@@ -94,7 +94,7 @@ The keystore defines a few important keys and addresses for sequencer operation.
 - `attester`: the private key of the sequencer, used for signing block proposals and attestations on block proposals produced by other sequencers. The corresponding Ethereum address of the private key is the identity of the sequencer.
 - `publisher`: the private key of the Ethereum EOA used for sending the block proposal to L1. This defaults to the attester private key if not set.
 - `coinbase`: the Ethereum address set in a block proposal. L1 rewards and fees are sent to this address. This falls back to the address derived by the attester private key if not set.
-- `feeRecipient`: the Aztec Address of the fee recipient address when proposing blocks. Allows receiving  funds as the block proposer in L2.
+- `feeRecipient`: the Aztec Address of the fee recipient address when proposing blocks. The unburnt portion of the tx fees in a given block are sent to this address.
 
 Please set these values with the ones you want and save `keystore.json`.
 
@@ -175,7 +175,7 @@ services:
   entrypoint: node /usr/src/yarn-project/aztec/dest/bin/index.js
   command: >-
    start
-   --network testnet-ignition
+--network alpha-testnet
    --node
    --archiver
    --sequencer