From 2874a863b92da641f177090f953fba0f50a9a8e1 Mon Sep 17 00:00:00 2001
From: bigbear <155267841+aso20455@users.noreply.github.com>
Date: Thu, 20 Feb 2025 21:48:24 +0100
Subject: [PATCH 1/7] Update holocene-changes.mdx
---
pages/notices/holocene-changes.mdx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/pages/notices/holocene-changes.mdx b/pages/notices/holocene-changes.mdx
index bbcb7aa5a..600ace16e 100644
--- a/pages/notices/holocene-changes.mdx
+++ b/pages/notices/holocene-changes.mdx
@@ -72,7 +72,7 @@ These following steps are necessary for every node operator:
### Configure the Holocene activation date
- If you are operating a node for an OP Chain that have opted into the [hardfork activation inheritance behavior](https://github.com/ethereum-optimism/superchain-registry/blob/main/docs/hardfork-activation-inheritance.md), the Holocene activation date is part of the `op-node` and `op-geth` nodes. So, no action is needed for the sequencer after upgrading to the latest release. Please skip to [Step 3: Verify Your Configuration](#verify-your-configuration).
+ If you are operating a node for an OP Chain that has opted into the [hardfork activation inheritance behavior](https://github.com/ethereum-optimism/superchain-registry/blob/main/docs/hardfork-activation-inheritance.md), the Holocene activation date is part of the `op-node` and `op-geth` nodes. So, no action is needed for the sequencer after upgrading to the latest release. Please skip to [Step 3: Verify Your Configuration](#verify-your-configuration).
For Sepolia that is: `OP Sepolia`, `Base Sepolia`, `Mode Sepolia`, `Zora Sepolia`, and `Metal Sepolia`.
From 7af10efd50024092134a6836929a0f897182f08b Mon Sep 17 00:00:00 2001
From: bigbear <155267841+aso20455@users.noreply.github.com>
Date: Thu, 20 Feb 2025 21:48:58 +0100
Subject: [PATCH 2/7] Update alt-da-mode.mdx
---
pages/operators/chain-operators/features/alt-da-mode.mdx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/pages/operators/chain-operators/features/alt-da-mode.mdx b/pages/operators/chain-operators/features/alt-da-mode.mdx
index 1609f0ab4..11532ce50 100644
--- a/pages/operators/chain-operators/features/alt-da-mode.mdx
+++ b/pages/operators/chain-operators/features/alt-da-mode.mdx
@@ -91,7 +91,7 @@ You should use at least the following compatible op\* versions when running your
### Set your fee configuration
* Chain operators are not posting everything to Ethereum, just commitments, so chain operators will need to determine fee scalars values to charge users. The fee scalar values are network throughput dependent, so values will need to be adjusted by chain operators as needed.
- * Cost structure for Alt-DA Mode: The transaction data is split up into 128kb chunks and then submitted to your DA Layer. Then, 32 byte commitments are submitted (goes to batch inbox address) to L1 for each 128kb chunk. Then, figure out how much that costs relative to the amount of transactions your chain is putting through.
+ * Cost structure for Alt-DA Mode: The transaction data is split up into 128kb chunks and then submitted to your DA Layer. Then, 32 byte commitments are submitted (goes to batch inbox address) to L1 for each 128kb chunk. Then, figure out how much that costs relative to the number of transactions your chain is putting through.
* Set scalar values inside the deploy config. The example below shows some possible fee scalar values, calculated assuming negligible DA Layer costs, but will need to be adjusted up or down based on network throughput - as a reminder of how to set your scalar values, see [this section](/operators/chain-operators/management/blobs#update-your-scalar-values-for-blobs) of the docs.
```
From 45da1ac4ae829c1cbf975f8440be2c2f7cfca62e Mon Sep 17 00:00:00 2001
From: bigbear <155267841+aso20455@users.noreply.github.com>
Date: Thu, 20 Feb 2025 21:49:20 +0100
Subject: [PATCH 3/7] Update custom-gas-token.mdx
---
pages/operators/chain-operators/features/custom-gas-token.mdx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/pages/operators/chain-operators/features/custom-gas-token.mdx b/pages/operators/chain-operators/features/custom-gas-token.mdx
index 63cc02d1a..69307ba8e 100644
--- a/pages/operators/chain-operators/features/custom-gas-token.mdx
+++ b/pages/operators/chain-operators/features/custom-gas-token.mdx
@@ -38,7 +38,7 @@ An OP Stack chain that uses the custom gas token feature enables an end user to
* symbol MUST be less than or equal to 32 bytes.
* must not be yield-bearing
* cannot be rebasing or have a transfer fee
- * must be transferrable only via a call to the token address itself
+ * must be transferable only via a call to the token address itself
* must only be able to set allowance via a call to the token address itself
* must not have a callback on transfer, and more generally a user must not be able to make a transfer to themselves revert
* a user must not be able to make a transfer have unexpected side effects
From e2b0de7b5d8898dcd123f8ac735191ad1c49cbad Mon Sep 17 00:00:00 2001
From: bigbear <155267841+aso20455@users.noreply.github.com>
Date: Thu, 20 Feb 2025 21:52:53 +0100
Subject: [PATCH 4/7] Update span-batches.mdx
---
pages/operators/chain-operators/features/span-batches.mdx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/pages/operators/chain-operators/features/span-batches.mdx b/pages/operators/chain-operators/features/span-batches.mdx
index 250257df5..76317ff2f 100644
--- a/pages/operators/chain-operators/features/span-batches.mdx
+++ b/pages/operators/chain-operators/features/span-batches.mdx
@@ -8,7 +8,7 @@ import { Callout, Steps } from 'nextra/components'
# Span batches
-Span batches are an important feature that optimizes batch processing within the chain. This section provides an overview of span batches, instructions on how to enable them, and links to detailed design documents.
+Span batches are an important feature that optimize batch processing within the chain. This section provides an overview of span batches, instructions on how to enable them, and links to detailed design documents.
## Overview
From 4b6a27f2d1e9f5bef05af375a5705844ba6e9558 Mon Sep 17 00:00:00 2001
From: bigbear <155267841+aso20455@users.noreply.github.com>
Date: Thu, 20 Feb 2025 21:54:25 +0100
Subject: [PATCH 5/7] Update op-txproxy.mdx
---
pages/operators/chain-operators/tools/op-txproxy.mdx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/pages/operators/chain-operators/tools/op-txproxy.mdx b/pages/operators/chain-operators/tools/op-txproxy.mdx
index a678a2694..26ca735d6 100644
--- a/pages/operators/chain-operators/tools/op-txproxy.mdx
+++ b/pages/operators/chain-operators/tools/op-txproxy.mdx
@@ -40,7 +40,7 @@ Even though the op-geth implementation of this endpoint includes rate limits, it
* Transaction targets are only 4337 Entrypoint contracts
- The motivating factor for this endpoint is to enable permissionless 4337 mempools, hence the restricted usage of this methods to just [Entrypoint](https://github.com/eth-infinitism/account-abstraction/blob/develop/contracts/core/EntryPoint.sol) transactions.
+ The motivating factor for this endpoint is to enable permissionless 4337 mempools, hence the restricted usage of this method to just [Entrypoint](https://github.com/eth-infinitism/account-abstraction/blob/develop/contracts/core/EntryPoint.sol) transactions.
Please open up an issue if you'd like this restriction to be optional via configuration to broaden usage of this endpoint.
From 17a2f97f4dcd16c7dd486c2ca2d1c2338890d9bf Mon Sep 17 00:00:00 2001
From: bigbear <155267841+aso20455@users.noreply.github.com>
Date: Thu, 20 Feb 2025 21:57:57 +0100
Subject: [PATCH 6/7] Update adding-derivation-attributes.mdx
---
.../chain-operators/tutorials/adding-derivation-attributes.mdx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/pages/operators/chain-operators/tutorials/adding-derivation-attributes.mdx b/pages/operators/chain-operators/tutorials/adding-derivation-attributes.mdx
index 1bb3c9864..b0f10f801 100644
--- a/pages/operators/chain-operators/tutorials/adding-derivation-attributes.mdx
+++ b/pages/operators/chain-operators/tutorials/adding-derivation-attributes.mdx
@@ -20,7 +20,7 @@ In this tutorial, you'll modify the Bedrock Rollup. Although there are many ways
## Getting the idea
-Let's quickly recap what you're about to do. The `op-node` is responsible for generating the Engine API payloads that trigger `op-geth` to produce blocks and transactions. The `op-node` already generates a "system transaction"for every L1 block that relays information about the current L1 state to the L2 chain. You're going to modify the `op-node` to add a new system transaction that reports the total burn amount (the base fee multiplied by the gas used) in each block.
+Let's quickly recap what you're about to do. The `op-node` is responsible for generating the Engine API payloads that trigger `op-geth` to produce blocks and transactions. The `op-node` already generates a "system transaction" for every L1 block that relays information about the current L1 state to the L2 chain. You're going to modify the `op-node` to add a new system transaction that reports the total burn amount (the base fee multiplied by the gas used) in each block.
Although it might sound like a lot, the whole process only involves deploying a single smart contract, adding one new file to `op-node`, and modifying one existing file inside `op-node`. It'll be painless. Let's go!
From dae9781302486a872023a7357f66cb54dec5c8e2 Mon Sep 17 00:00:00 2001
From: bigbear <155267841+aso20455@users.noreply.github.com>
Date: Thu, 20 Feb 2025 21:58:20 +0100
Subject: [PATCH 7/7] Update architecture.mdx
---
pages/operators/chain-operators/architecture.mdx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/pages/operators/chain-operators/architecture.mdx b/pages/operators/chain-operators/architecture.mdx
index 5bc5b42ef..2b8e78b05 100644
--- a/pages/operators/chain-operators/architecture.mdx
+++ b/pages/operators/chain-operators/architecture.mdx
@@ -49,7 +49,7 @@ amount of data required to reproduce L2 blocks.
`op-deployer` is a tool that simplifies the process of deploying standardized OP Stack chains that comply with Superchain specifications.
It compares the state of your chain against the intent,
-and make whatever changes are necessary for them to match. In its current state,
+and makes whatever changes are necessary for them to match. In its current state,
it is intended to deploy new standard chains that utilize the Superchain wide contracts.