diff --git a/pages/app-developers/tutorials/bridging/standard-bridge-standard-token.mdx b/pages/app-developers/tutorials/bridging/standard-bridge-standard-token.mdx
index 21b517400..59e00c16d 100644
--- a/pages/app-developers/tutorials/bridging/standard-bridge-standard-token.mdx
+++ b/pages/app-developers/tutorials/bridging/standard-bridge-standard-token.mdx
@@ -83,7 +83,7 @@ Set your L1 ERC-20 token address as an environment variable with the `export` co
 
 {<h3>Deploy your L2 ERC-20 token</h3>}
 
-You can now deploy our L2 ERC-20 token using the [`OptimismMintableERC20Factory`](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/universal/OptimismMintableERC20Factory.sol).
+You can now deploy your L2 ERC-20 token using the [`OptimismMintableERC20Factory`](https://github.com/ethereum-optimism/optimism/blob/develop/packages/contracts-bedrock/src/universal/OptimismMintableERC20Factory.sol).
 Use the `cast` command to trigger the deployment function on the factory contract.
 This example command creates a token with the name "My Standard Demo Token" and the symbol "L2TKN".
 The resulting L2 ERC-20 token address is printed to the console.
diff --git a/pages/connect/contribute/stack-contribute.mdx b/pages/connect/contribute/stack-contribute.mdx
index 4488cc36d..b1ae51210 100644
--- a/pages/connect/contribute/stack-contribute.mdx
+++ b/pages/connect/contribute/stack-contribute.mdx
@@ -29,7 +29,7 @@ To make your first contribution to the codebase, check out the [open issues](htt
 
 <Callout type="warning">
   Only the software components included within the current release of the OP Stack codebase are considered in the scope of the OP Stack.
-  Any usage of the OP Stack outside of the official, intended capabilities of the current release are considered [OP Stack Hacks](https://github.com/ethereum-optimism/developers/tree/main/hacks) — unofficial modifications that are useful for experimentation but could have unforeseen results, such as security vulnerabilities, and are likely to cause your chain to no longer be interoperable with the [Optimism Superchain](https://app.optimism.io/superchain/).
+  Any usage of the OP Stack outside of the official, intended capabilities of the current release is considered [OP Stack Hacks](https://github.com/ethereum-optimism/developers/tree/main/hacks) — unofficial modifications that are useful for experimentation but could have unforeseen results, such as security vulnerabilities, and are likely to cause your chain to no longer be interoperable with the [Optimism Superchain](https://app.optimism.io/superchain/).
   Developer support for OP Stack Hacks is limited — when in doubt, stick to the capabilities of the current release!
 </Callout>
 
diff --git a/pages/notices/holocene-changes.mdx b/pages/notices/holocene-changes.mdx
index b72312c75..6684ed924 100644
--- a/pages/notices/holocene-changes.mdx
+++ b/pages/notices/holocene-changes.mdx
@@ -23,7 +23,6 @@ If you experience difficulty at any stage of this process, please reach out to [
   The Holocene upgrade for the Mainnet Superchain is scheduled for **Thu 9 Jan 2025 18:00:01 UTC**, [governance approval](https://vote.optimism.io/proposals/20127877429053636874064552098716749508236019236440427814457915785398876262515).
 
   The Holocene upgrade for the Soneium Mainnet will be activated at **Mon Feb 03 at 09:00:00 UTC** (`1738573200`).
-  The Holocene upgrade for the Mainnet Superchain is scheduled for **Thu 9 Jan 2025 18:00:01 UTC**, [governance approval](https://vote.optimism.io/proposals/20127877429053636874064552098716749508236019236440427814457915785398876262515).
 </Callout>
 
 ## What's included in Holocene