resolve comments

Author: krofax

pages/operators/chain-operators/deploy/genesis.mdx

@@ -75,16 +75,6 @@ Once you have `genesis.json` and `rollup.json`:
 2.  Configure op-node with rollup.json.
 3.  Set up additional off-chain infrastructure as needed (block explorer, indexers, etc.). For more on architecture, see [Architecture overview](/operators/chain-operators/architecture).
 
-### Step 4: Get data
-
-Now that you have your `genesis.json` and `rollup.json` you can spin up a node on your network.
-You can also use the following inspect subcommands to get additional data:
-
-```bash
-./bin/op-deployer inspect l1 --workdir .deployer <l2-chain-id> # outputs all L1 contract addresses for an L2 chain
-./bin/op-deployer inspect deploy-config --workdir .deployer <l2-chain-id> # outputs the deploy config for an L2 chain
-```
-
 ## Legacy method: using foundry script
 
 The following guide shows you how to generate the L2 genesis file `genesis.json`. This is a JSON

pages/operators/chain-operators/deploy/smart-contracts.mdx

@@ -19,11 +19,6 @@ official contract releases**. You can visit the [smart contract overview](/stack
 for the official release versions. Changes to the smart contracts are
 generally not considered backwards compatible.
 
-<Callout type="warning">
-  The following deployment information outlines the legacy method for deploying the OP Stack L1 contracts.
-  This method is not recommended and is provided only for historical context.
-</Callout>
-
 ## Deployment configuration
 
 Deploying your OP Stack contracts requires creating a deployment configuration
@@ -34,8 +29,19 @@ can see the [rollup deployment configuration page](/operators/chain-operators/co
 
 For a detailed explanation of the configuration options and their meanings, refer to the [rollup deployment configuration page](/operators/chain-operators/configuration/rollup).
 
+## Using `op-deployer`
+
+The recommended way to deploy the L1 smart contracts is with the `op-deployer` tool.
+Follow the steps in this [section](/operators/chain-operators/tutorials/create-l2-rollup#using-op-deployer) to learn how it works.
+
+
 ## Deployment script (Legacy method)
 
+<Callout type="warning">
+  The following deployment information outlines the legacy method for deploying the OP Stack L1 contracts.
+  This method is not recommended and is provided only for historical context.
+</Callout>
+
 The legacy method for deploying smart contracts uses [foundry](https://github.com/foundry-rs) and the deployment script located in the monorepo at
 [packages/contracts-bedrock/scripts/deploy/Deploy.s.sol](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/scripts/deploy/Deploy.s.sol).
 
@@ -84,11 +90,6 @@ All functions for deploying a single contract are public, meaning that
 the `--sig` argument to forge script can be used to target the deployment of a
 single contract.
 
-## Using `op-deployer`
-
-The recommended way to deploy the L1 smart contracts is with the `op-deployer` tool.
-Follow the steps in this [section](/operators/chain-operators/tutorials/create-l2-rollup#using-op-deployer) to learn how it works.
-
 ## Best practices
 
 Production users should deploy their L1 contracts from a contracts release.

pages/operators/chain-operators/tools/op-deployer.mdx

@@ -128,7 +128,7 @@ Inspect the `state.json` file by navigating to your working directory. With the
 ./bin/op-deployer inspect rollup --workdir .deployer <l2-chain-id> > .deployer/rollup.json
 ```
 
-Now that you have your `genesis.json` and `rollup.json` you can spin up a node on your network. You can also use the following inspect subcommands to get additional data:
+Now that you have your `genesis.json` and `rollup.json` you can spin up a node on your network. You can also use the following inspect subcommands to get additional chain artifacts:
 
 ```bash
 ./bin/op-deployer inspect l1 --workdir .deployer <l2-chain-id> # outputs all L1 contract addresses for an L2 chain

pages/operators/chain-operators/tutorials/create-l2-rollup.mdx

@@ -433,8 +433,6 @@ Using op-deployer for chain initialization is a requirement for all chains inten
 This ensures standardization and compatibility across the OP Stack ecosystem.
 </Callout>
 
-## Recommended method: using op-deployer
-
 ### Prerequisites
 
 1.  You have installed the `op-deployer` binary following the instructions in [deployer docs](/operators/chain-operators/tools/op-deployer#installation).
@@ -489,16 +487,6 @@ Once you have `genesis.json` and `rollup.json`:
 2.  Configure op-node with rollup.json.
 3.  Set up additional off-chain infrastructure as needed (block explorer, indexers, etc.). For more on architecture, see [Architecture overview](/operators/chain-operators/architecture).
 
-### Step 4: Get data
-
-Now that you have your `genesis.json` and `rollup.json` you can spin up a node on your network.
-You can also use the following inspect subcommands to get additional data:
-
-```bash
-./bin/op-deployer inspect l1 --workdir .deployer <l2-chain-id> # outputs all L1 contract addresses for an L2 chain
-./bin/op-deployer inspect deploy-config --workdir .deployer <l2-chain-id> # outputs the deploy config for an L2 chain
-```
-
 ## Initialize `op-geth`
 
 You're almost ready to run your chain!