Apply suggestions from code review

Co-authored-by: josh crites <[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 the block header, 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 bundle 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.
 
@@ -53,12 +53,12 @@ It also is assumed that you have installed Docker and the aztec toolchain via az
 
 Furthermore, as this guide uses Docker compose, you will need to install it. Please follow [this](https://docs.docker.com/compose/install/) guide to do so.
 
-Finally, this guide requires you to have endpoints of an L1 node stack of an execution and consensus client. If you do not have one set up, you see a good guide on how to do that here at (Eth Docker)[https://ethdocker.com/Usage/QuickStart].
+Finally, this guide requires you to have endpoints of an L1 node stack of an execution and consensus client. If you do not have one set up, you can see a good guide on how to do that [here at Eth Docker](https://ethdocker.com/Usage/QuickStart).
 
 
 ## Configure the sequencer
 
-There are a few important things to note when setting up a sequencer. This guide will guide you in up and running a sequencer with a standard setup using Docker compose with a .env file.
+There are a few important things to note when setting up a sequencer. This guide will guide you in setting up and running a sequencer with a standard setup using Docker compose with a .env file.
 
 The setup of the sequencer has four important steps.
 
@@ -67,11 +67,11 @@ The setup of the sequencer has four important steps.
 3. Ensure auto-update / auto-restart is enabled
 4. Apply your Docker compose file
 
-Let's start by creating a new directory called `aztec-sequencer`, with two subdirectories, `keys`, and `data. This is where all the information used by the sequencer will be stored. Please also create an empty `.env` file in `aztec-sequencer` to define your settings before moving on to the next step.
+Let's start by creating a new directory called `aztec-sequencer`, with two subdirectories, `keys`, and `data`. This is where all the information used by the sequencer will be stored. Please also create an empty `.env` file in `aztec-sequencer` to define your settings before moving on to the next step.
 
-### Define private keys / accounts used for sequencer duties
+### Define private keys / accounts
 
-Due to the duties performed by the sequencer, it must hold and use private keys identifying it as a valid proposer or attester. The way this is done is by defining a keystore file.
+A sequencer must hold and use private keys identifying it as a valid proposer or attester. This is done is by defining a keystore file.
 
 An example keystore file is below. Copy this file and save it as `keystore.json` into your `aztec-sequencer/keys` folder.
 
@@ -98,15 +98,15 @@ The keystore defines a few important keys and addresses for sequencer operation.
 
 Please set these values with the ones you want and save `keystore.json`.
 
-### Set required node configuration
+### Node configuration
 
 Next you will need to define some environment variables that set important configuration for your node.
 
 These include:
 
 - `DATA_DIRECTORY`: the folder where the data of the sequencer is stored
 - `KEY_STORE_DIRECTORY`: can be a path to the file or directory where keystores are located. In our case it is the path to the folder containing the `keystore.json` file created above
-- `LOG_LEVEL`: the desired level of logging for the sequencer. It defaults to info.
+- `LOG_LEVEL`: the desired level of logging for the sequencer. It defaults to `INFO`.
 - `ETHEREUM_HOSTS`: The execution RPC endpoints
 - `L1_CONSENSUS_HOST_URLS`: The consensus RPC endpoints
 - `P2P_IP`: The IP address of this sequencer
@@ -129,16 +129,16 @@ AZTEC_PORT=8080
 :::tip
 You MUST forward your ports. Your router must send UDP and TCP traffic on the port specified by `AZTEC_NODE_P2P_PORT` to your IP address on your local network.
 
-If you are unable to determine your public ip. Running the command `curl ipv4.icanhazip.com` can retrieve it for you.
+Running the command `curl ipv4.icanhazip.com` can retrieve your public IP address for you.
 :::
 
-### Ensure auto-update / auto-restart is enabled
+### Enable auto-update / auto-restart
 
 It is imperative that the built in auto-updating functionality of the sequencer is not disabled. The update-checker is a background module in the Aztec node that enables global coordination of updates. It allows the protocol team to:
 
 - Push configuration changes to all nodes
 - Trigger shutdowns so that nodes can pull the latest image version
-- Apply hotfixes quickly
+- Apply hot-fixes quickly
 - Coordinate node resets after a governance upgrade, especially when a new canonical rollup is published to the Registry
 
 This module ensures that upgrades and fixes propagate smoothly without requiring manual intervention from every node operator.
@@ -199,7 +199,7 @@ networks:
 
 Please note that we are setting only the necessary configuration for running this sequencer. The full list of settings and flags can be explored here at the [cli reference](../../reference/cli_reference.md). A lot of these options are preset to defaults by the `--network` flag above. This downloads defaults for the specified network and applies them to the node.
 
-Now, you can run `docker compose up` inside your `aztec-sequencer` folder to start the sequencer !
+Now, you can run `docker compose up` inside your `aztec-sequencer` folder to start the sequencer!
 
 To check if it is currently synced, which may take a few minutes, run this command and compare its output to any of the Aztec block explorers.
 
@@ -211,7 +211,7 @@ http://localhost:8080 | jq -r ".result.proven.number"
 
 ## Add yourself to the testnet sequencer set
 
-After setting up your node, to be included in testnet duties, you must explicitly request to be added to the sequencer set.
+After setting up your node you must explicitly request to be added to the sequencer set.
 
 To complete this final step you have two options: