From 4785a77d21f65f128b236c556718afaf930ba10b Mon Sep 17 00:00:00 2001 From: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Date: Wed, 5 Nov 2025 20:09:44 +0000 Subject: [PATCH] Fix typos and grammatical errors in notices and reference documentation - Fix 'effects' to 'affects' in blob-fee-bug.mdx description - Fix 'we'd be overcharge' to 'we'd overcharge' in blob-fee-bug.mdx - Fix 'effect any' to 'affect any' in superchain-withdrawal-pause-test.mdx - Fix missing space after period in pectra-changes.mdx - Add missing comma after 'dugtrio' in fusaka-notice.mdx - Remove trailing dash from 'Breaking Changes' heading in upgrade-17.mdx - Add missing space before 'or' in components.mdx - Add missing space in 'Release of' in stack-contribute.mdx - Fix 'it's address' to 'its address' in glossary.mdx --- notices/archive/blob-fee-bug.mdx | 4 ++-- notices/archive/pectra-changes.mdx | 2 +- notices/archive/superchain-withdrawal-pause-test.mdx | 2 +- notices/fusaka-notice.mdx | 2 +- notices/upgrade-17.mdx | 2 +- reference/components.mdx | 2 +- reference/contribute/stack-contribute.mdx | 2 +- reference/glossary.mdx | 2 +- 8 files changed, 9 insertions(+), 9 deletions(-) diff --git a/notices/archive/blob-fee-bug.mdx b/notices/archive/blob-fee-bug.mdx index 3a1ab2dff..5299d0276 100644 --- a/notices/archive/blob-fee-bug.mdx +++ b/notices/archive/blob-fee-bug.mdx @@ -1,9 +1,9 @@ --- title: Superchain testnets' blob fee bug -description: Learn about the blob fee bug that effects OP Stack testnets on the Superchain and how to fix it. +description: Learn about the blob fee bug that affects OP Stack testnets on the Superchain and how to fix it. --- -At the time of writing, all OP Stack testnets are currently sequencing a "wrong" chain. The L1 Block's blob base fee is calculated with pre-Prague blob schedule parameters. This is not a critical security issue on any OP Sepolia (or Holesky) chain. However, when L1 blob base fees rise to 100 Mwei or higher on the L1 testnet, there is a temporary liveness risk, because we'd be overcharge L1 fees. +At the time of writing, all OP Stack testnets are currently sequencing a "wrong" chain. The L1 Block's blob base fee is calculated with pre-Prague blob schedule parameters. This is not a critical security issue on any OP Sepolia (or Holesky) chain. However, when L1 blob base fees rise to 100 Mwei or higher on the L1 testnet, there is a temporary liveness risk, because we'd overcharge L1 fees. This was fixed on the `develop` branch with this [PR](https://github.com/ethereum-optimism/optimism/pull/14500) and there will be no impact on any mainnet chains. Mainnet chains will just need to update their binaries to the latest release prior to the activation of Pectra on Ethereum, so the bug isn't triggered when Pectra activates. diff --git a/notices/archive/pectra-changes.mdx b/notices/archive/pectra-changes.mdx index 1dd8b4ff3..db7a5f52c 100644 --- a/notices/archive/pectra-changes.mdx +++ b/notices/archive/pectra-changes.mdx @@ -48,7 +48,7 @@ Pectra contains a variety of EIPs, some of which apply to the OP Stack; others d ## For node operators -Node operators will need to upgrade to the respective releases before the activation dates.These following steps are necessary for every node operator: +Node operators will need to upgrade to the respective releases before the activation dates. These following steps are necessary for every node operator: ### Update to the latest release diff --git a/notices/archive/superchain-withdrawal-pause-test.mdx b/notices/archive/superchain-withdrawal-pause-test.mdx index 9e633fb89..b1c7c09b4 100644 --- a/notices/archive/superchain-withdrawal-pause-test.mdx +++ b/notices/archive/superchain-withdrawal-pause-test.mdx @@ -18,4 +18,4 @@ The Optimism Collective will be testing improved incident response features on t To learn more about this functionality, please refer to this [documentation](/stack/security/pause). -This functionality is important for the security of the Superchain and should be understood by Chain Operators, users, and especially for centralized exchanges and third-party bridge operators. **Please note that this will not effect any L1-to-L2 deposit transactions or L2 transactions. No action is required from users or operators.** +This functionality is important for the security of the Superchain and should be understood by Chain Operators, users, and especially for centralized exchanges and third-party bridge operators. **Please note that this will not affect any L1-to-L2 deposit transactions or L2 transactions. No action is required from users or operators.** diff --git a/notices/fusaka-notice.mdx b/notices/fusaka-notice.mdx index adb246a4f..64e3f839b 100644 --- a/notices/fusaka-notice.mdx +++ b/notices/fusaka-notice.mdx @@ -78,7 +78,7 @@ Update the following: | Component | Version | Notes | | --------------- | ----------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `proxyd` | [v4.19.0](https://github.com/ethereum-optimism/infra/releases/tag/proxyd%2Fv4.19.0) or greater | You need to whitelist `eth_blobBaseFee` rpc if using proxyd for L1 load balancing. If you use `dugtrio` ensure this is also updated to the latest release. | +| `proxyd` | [v4.19.0](https://github.com/ethereum-optimism/infra/releases/tag/proxyd%2Fv4.19.0) or greater | You need to whitelist `eth_blobBaseFee` rpc if using proxyd for L1 load balancing. If you use `dugtrio`, ensure this is also updated to the latest release. | | `op-batcher` | [v1.16.0](https://github.com/ethereum-optimism/optimism/releases/tag/op-batcher%2Fv1.16.0) | `OP_BATCHER_TXMGR_ENABLE_CELL_PROOFS`: `true` or equivalent CLI flag needs to be set and the batcher restarted just after Fusaka activates on L1. | | `op-node` | [v1.14.1](https://github.com/ethereum-optimism/optimism/releases/tag/op-node%2Fv1.14.1) | L1 chain config must be supplied via a new flag (see the release notes). Not necessary for chains deriving from Ethereum Mainnet, Sepolia, Holesky or Hoodi. | | `op-geth` | [v1.101603.1](https://github.com/ethereum-optimism/op-geth/releases/tag/v1.101603.1) | | diff --git a/notices/upgrade-17.mdx b/notices/upgrade-17.mdx index 53344690e..def659e78 100644 --- a/notices/upgrade-17.mdx +++ b/notices/upgrade-17.mdx @@ -25,7 +25,7 @@ Upgrade 17 introduces the following changes: For more information on the Jovian implementation details, please review the [Jovian specifications](https://specs.optimism.io/protocol/jovian/overview.html). -## Breaking Changes - +## Breaking Changes ### Block header changes diff --git a/reference/components.mdx b/reference/components.mdx index c39957024..cd46b9445 100644 --- a/reference/components.mdx +++ b/reference/components.mdx @@ -12,7 +12,7 @@ This page sketches out the different conceptual layers of the stack as they exis This doesn't include all of the modules or layers that may exist in the future, but it gives a good overview of the major OP Stack components. - Please note that not all of the modules described on this page already exist in a production state — these are explicitly marked as either "**in development**"or "**proposed**." + Please note that not all of the modules described on this page already exist in a production state — these are explicitly marked as either "**in development**" or "**proposed**." ## Layers diff --git a/reference/contribute/stack-contribute.mdx b/reference/contribute/stack-contribute.mdx index afd6d640d..7cf7d8911 100644 --- a/reference/contribute/stack-contribute.mdx +++ b/reference/contribute/stack-contribute.mdx @@ -18,7 +18,7 @@ To start contributing components to the stack, check out some of these [useful i The OP Stack codebase is not a product (in the traditional sense) but rather a collection of software components that power the Optimism ecosystem. If you'd like to contribute to the current release of OP Stack codebase, rather than creating new components, your contribution would be greatly appreciated. -**A "Release"of the OP Stack codebase is a particular set of software components that are production-ready and which fit the stack's design principles and goals.** +**A "Release" of the OP Stack codebase is a particular set of software components that are production-ready and which fit the stack's design principles and goals.** To make your first contribution to the codebase, check out the [open issues](https://github.com/ethereum-optimism/optimism/issues) on the Optimism Monorepo. diff --git a/reference/glossary.mdx b/reference/glossary.mdx index d3ac32a64..ecf8a43f5 100644 --- a/reference/glossary.mdx +++ b/reference/glossary.mdx @@ -17,7 +17,7 @@ The glossary provides definitions of important terminology used throughout the O ### Address aliasing -When a contract submits a [deposit](#deposit) from L1 to L2, it's address (as returned by `ORIGIN` and `CALLER`) will be +When a contract submits a [deposit](#deposit) from L1 to L2, its address (as returned by `ORIGIN` and `CALLER`) will be aliased with a modified representation of the address of a contract. ### Block