Update broken links inside the documentation

README.md

@@ -1,7 +1,7 @@
 <img src=".github/readme-banner.png" alt="Welcome to the Superchain Registry"><br/>
 
 > [!WARNING]
-> Starting on March 1st, 2025, all standard chains who wish to be added to the Superchain registry **MUST** be deployed using [OP Deployer](https://docs.optimism.io/builders/chain-operators/tools/op-deployer).
+> Starting on March 1st, 2025, all standard chains who wish to be added to the Superchain registry **MUST** be deployed using [OP Deployer](https://docs.optimism.io/chain-operators/tools/op-deployer).
 
 The Superchain Registry is an index of chains which serves as the source of truth for who’s in the Superchain Ecosystem and what modifications they’ve made to their chains.
 
@@ -24,7 +24,7 @@ A glossary, with key terms and more information about Superchain levels and requ
 
 ### Downstream packages
 
-The Superchain configs are stored in a minimal form and embedded in downstream OP-Stack software ([`op-node`](https://github.com/ethereum-optimism/optimism) and [`op-geth`](https://github.com/ethereum-optimism/op-geth)). This means that after a chain has been added to the registry and the dependency on the registry updates in the downstream software, it is possible to start an `op-node` instance [using the `--network` flag](https://docs.optimism.io/builders/node-operators/configuration/consensus-config#network) (and also an `op-geth` instance [using the `--op-network` tag](https://docs.optimism.io/builders/node-operators/configuration/execution-config#op-network-betaop-network)) which will successfully sync with other nodes on that network.
+The Superchain configs are stored in a minimal form and embedded in downstream OP-Stack software ([`op-node`](https://github.com/ethereum-optimism/optimism) and [`op-geth`](https://github.com/ethereum-optimism/op-geth)). This means that after a chain has been added to the registry and the dependency on the registry updates in the downstream software, it is possible to start an `op-node` instance [using the `--network` flag](https://docs.optimism.io/node-operators/guides/consensus-config#network) (and also an `op-geth` instance [using the `--op-network` tag](https://docs.optimism.io/node-operators/guides/execution-config#op-network%2C-beta-op-network )) which will successfully sync with other nodes on that network.
 
 ### Hardfork activations
 If you would like your chain to automatically receive superchain-wide coordinated hardfork activations, you can enable this by:

docs/hardfork-activation-inheritance.md

@@ -12,8 +12,8 @@ For a chain to "receive" a particular default (superchain-wide) hardfork activat
 To "receive" a hardfork activation time for a given chain means that the downstream OP Stack components will apply that activation time when starting up using a network flag specifying the chain in question.
 
 At the time of writing, this is implemented for
-* [op-geth](https://docs.optimism.io/builders/node-operators/configuration/base-config#initialization-via-network-flags)
-* [op-node](https://docs.optimism.io/builders/node-operators/configuration/base-config#configuring-op-node)
+* [op-geth](https://docs.optimism.io/node-operators/guides/base-config#initialization-via-network-flags)
+* [op-node](https://docs.optimism.io/node-operators/guides/base-config#configuring-op-node)
 
 > [!NOTE]
 > Since [version 2.0](https://github.com/ethereum-optimism/superchain-registry/pull/816) of the superchain registry, the inherited hardfork activation times are applied directly to each chain's individual chain config TOML file. What you see is what you get (unlike in previous iterations of the registry, where the inheritance was applied "magically" by Go bindings).

docs/ops.md

@@ -13,7 +13,7 @@ The following are the steps you need to take to add a chain to the registry:
 ### 0. Standard Chains: Deploy your chain with `op-deployer`
 
 If you are deploying a standard chain, it _must_ be deployed with `op-deployer` to be considered standard in the Superchain Registry. Check out
-the [docs](https://docs.optimism.io/builders/chain-operators/tools/op-deployer) for more information on how to use it.
+the [docs](https://docs.optimism.io/chain-operators/tools/op-deployer) for more information on how to use it.
 
 > [!TIP]
 > We recommend that most chains use `op-deployer`. `op-deployer` can be configured to support L3s, alt-DA and custom gas token chains.