diff --git a/pages/builders/chain-operators/configuration/rollup.mdx b/pages/builders/chain-operators/configuration/rollup.mdx
index 16140ad87..35c6c7bdc 100644
--- a/pages/builders/chain-operators/configuration/rollup.mdx
+++ b/pages/builders/chain-operators/configuration/rollup.mdx
@@ -1005,7 +1005,7 @@ gas on L2.
 Alt-DA Mode enables seamless integration of various Data Availability (DA) 
 Layers, regardless of their commitment type, into the OP Stack. This allows 
 any chain operator to launch an OP Stack chain using their favorite DA Layer 
-for sustainably low costs. Learn more [here](/stack/protocol/features/alt-da-mode).
+for sustainably low costs. Learn more [here](/stack/beta-features/alt-da-mode).
 
 ***
 
diff --git a/pages/builders/chain-operators/deploy/genesis.mdx b/pages/builders/chain-operators/deploy/genesis.mdx
index 3df9223dc..7004e07d8 100644
--- a/pages/builders/chain-operators/deploy/genesis.mdx
+++ b/pages/builders/chain-operators/deploy/genesis.mdx
@@ -8,6 +8,11 @@ import { Callout } from 'nextra/components'
 
 # OP Stack genesis creation
 
+<Callout type="warning">
+This page is out of date and shows the legacy method for genesis file creation.
+For the latest recommended method, use [op-deployer](/builders/chain-operators/tools/op-deployer).
+</Callout>
+
 The following guide shows you how to generate the L2 genesis file `genesis.json`. This is a JSON
 file that represents the L2 genesis. You will provide this file to the
 execution client (op-geth) to initialize your network. There is also the rollup configuration file, `rollup.json`, which will be
diff --git a/pages/builders/chain-operators/deploy/smart-contracts.mdx b/pages/builders/chain-operators/deploy/smart-contracts.mdx
index bcea8a6b4..598e8c1d0 100644
--- a/pages/builders/chain-operators/deploy/smart-contracts.mdx
+++ b/pages/builders/chain-operators/deploy/smart-contracts.mdx
@@ -8,6 +8,11 @@ import { Callout } from 'nextra/components'
 
 # OP Stack smart contract deployment
 
+<Callout type="warning">
+This page is out of date and shows the legacy method for smart contract deployment.
+For the latest recommended method, use [op-deployer](/builders/chain-operators/tools/op-deployer).
+</Callout>
+
 The following guide shows you how to deploy the OP Stack L1 smart contracts.
 The primary development branch is `develop`, however **you should only deploy
 official contract releases**. You can visit the see the [smart contract overview](/stack/smart-contracts#official-releases)