From 923cd134ba8e5be3d60a1ddee9a14c8068afd973 Mon Sep 17 00:00:00 2001 From: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Date: Wed, 5 Nov 2025 18:52:31 +0000 Subject: [PATCH] Fix typos and grammatical errors in chain-operators/reference documentation - Fix missing preposition in architecture.mdx: 'taking disk snapshots' -> 'for taking disk snapshots' - Fix incorrect verb form in opcm.mdx: 'deploys of' -> 'deploys' - Fix subject-verb agreement in preinstalls.mdx: 'what it brings' -> 'what they bring' - Fix typo in alt-da-mode.mdx: '--atlda.da-server' -> '--altda.da-server' - Fix incorrect relative pronoun in superchain-registry.mdx: 'who have utilize' -> 'that utilize' - Fix incorrect apostrophe in superchain-upgrades.mdx: 'see's' -> 'sees' --- chain-operators/reference/architecture.mdx | 2 +- chain-operators/reference/features/alt-da-mode.mdx | 2 +- chain-operators/reference/features/preinstalls.mdx | 2 +- chain-operators/reference/opcm.mdx | 2 +- chain-operators/reference/superchain-registry.mdx | 2 +- chain-operators/reference/superchain-upgrades.mdx | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/chain-operators/reference/architecture.mdx b/chain-operators/reference/architecture.mdx index 2f302680e..f8fc0a893 100644 --- a/chain-operators/reference/architecture.mdx +++ b/chain-operators/reference/architecture.mdx @@ -125,7 +125,7 @@ GETH_DB_ENGINE: "pebble" GETH_STATE_SCHEME: "hash" ``` -* You can also use these nodes taking disk snapshots for disaster recovery. +* You can also use these nodes for taking disk snapshots for disaster recovery. ### Full Snapsync Nodes diff --git a/chain-operators/reference/features/alt-da-mode.mdx b/chain-operators/reference/features/alt-da-mode.mdx index 9c53d9ac4..d035e3b49 100644 --- a/chain-operators/reference/features/alt-da-mode.mdx +++ b/chain-operators/reference/features/alt-da-mode.mdx @@ -59,7 +59,7 @@ You should use at least the following compatible op\* versions when running your * Set `--altda.enabled=true` and `--altda.da-service=true`. - * Provide the URL for `--atlda.da-server=$DA_SERVER_HTTP_URL`. + * Provide the URL for `--altda.da-server=$DA_SERVER_HTTP_URL`. ``` --altda.da-server value ($OP_BATCHER_ALTDA_DA_SERVER) diff --git a/chain-operators/reference/features/preinstalls.mdx b/chain-operators/reference/features/preinstalls.mdx index ae280cc52..33280e542 100644 --- a/chain-operators/reference/features/preinstalls.mdx +++ b/chain-operators/reference/features/preinstalls.mdx @@ -3,7 +3,7 @@ title: OP Stack preinstalls description: Learn how to use preinstalls on your chain. --- -This guide explains OP Stack preinstalls and what it brings to developers. +This guide explains OP Stack preinstalls and what they bring to developers. To go to production on a new chain, developers need their core contracts: Gnosis Safes, the 4337 entrypoint, create2deployer, etc. On a blank EVM, these contracts can take weeks to be deployed. Now, core contracts come *preinstalled* on the OP Stack -- no third party deployment necessary. Whether hacking alone or starting the next big rollup, developers can start using their favorite contracts as soon as they spin up their chain. diff --git a/chain-operators/reference/opcm.mdx b/chain-operators/reference/opcm.mdx index 7fa8a18b1..a300fd6db 100644 --- a/chain-operators/reference/opcm.mdx +++ b/chain-operators/reference/opcm.mdx @@ -1,6 +1,6 @@ --- title: OP Contracts Manager -description: Learn how OP Contracts Manager deploys of the OP Stack with one transaction. +description: Learn how OP Contracts Manager deploys the OP Stack with one transaction. --- The OP Contracts Manager is a contract that deploys the L1 contracts for an OP Stack chain in a single transaction. It provides a minimal set of user-configurable parameters to ensure that the resulting chain meets the standard configuration requirements. Additionally, as of [Upgrade 13](https://gov.optimism.io/t/upgrade-proposal-13-opcm-and-incident-response-improvements/9739), instances of OPCM can upgrade existing OP Stack chains. diff --git a/chain-operators/reference/superchain-registry.mdx b/chain-operators/reference/superchain-registry.mdx index c8896a3e7..2df0261c6 100644 --- a/chain-operators/reference/superchain-registry.mdx +++ b/chain-operators/reference/superchain-registry.mdx @@ -30,4 +30,4 @@ All Superchain Ecosystem members are welcome to join the Superchain Registry, re After being included into the Superchain Registry, subsequent releases of the `op-node` and `op-geth` will contain the chain's genesis and rollup configurations baked in. You can use then use the `--network` (`op-node`) and `--op-network` (`op-geth`) flags to start up your node with this information. Using these flags means that the node will automatically inherit the hard fork activation times from the Superchain Registry, so you don't need to manually set them in your node configuration. Additionally, chains can opt into the hard fork activation inheritance behavior by specifying the `superchain_time` in the chain's TOML file to start inheriting Superchain wide activation timestamps. -Networks who have utilize this mechanism will activate network hard forks specified in the `superchain.toml` files: [Sepolia superchain.toml](https://github.com/ethereum-optimism/superchain-registry/blob/main/superchain/configs/sepolia/superchain.toml) and [Mainnet superchain.toml](https://github.com/ethereum-optimism/superchain-registry/blob/main/superchain/configs/mainnet/superchain.toml). +Networks that utilize this mechanism will activate network hard forks specified in the `superchain.toml` files: [Sepolia superchain.toml](https://github.com/ethereum-optimism/superchain-registry/blob/main/superchain/configs/sepolia/superchain.toml) and [Mainnet superchain.toml](https://github.com/ethereum-optimism/superchain-registry/blob/main/superchain/configs/mainnet/superchain.toml). diff --git a/chain-operators/reference/superchain-upgrades.mdx b/chain-operators/reference/superchain-upgrades.mdx index 7148e0414..0f74c6565 100644 --- a/chain-operators/reference/superchain-upgrades.mdx +++ b/chain-operators/reference/superchain-upgrades.mdx @@ -22,7 +22,7 @@ This contract is instrumental in managing and tracking the progression of protoc **[Superchain version signaling](https://specs.optimism.io/protocol/superchain-upgrades.html?utm_source=op-docs&utm_medium=docs#superchain-version-signaling)** is a mechanism that allows nodes and clients to be aware of and prepare for upcoming protocol changes. This signaling is achieved through the **ProtocolVersion smart contract**, allowing chains to indicate their readiness for upcoming upgrades and ensuring that all participating chains are synchronized. -If the node see's a versioning signal onchain before the node software has been updated for a hardfork, the node will [halt](/superchain/superchain-upgrades#rolluphalt-flags-on-node-binaries) to prevent chain divergence +If the node sees a versioning signal onchain before the node software has been updated for a hardfork, the node will [halt](/superchain/superchain-upgrades#rolluphalt-flags-on-node-binaries) to prevent chain divergence Through this signaling: * Nodes can anticipate and implement necessary adjustments ahead of time. * Clients are informed about the protocol version they should be compatible with, ensuring seamless interactions across the Superchain.