diff --git a/pages/builders/node-operators/_meta.json b/pages/builders/node-operators/_meta.json
index a9d6fbb46..07df62fb7 100644
--- a/pages/builders/node-operators/_meta.json
+++ b/pages/builders/node-operators/_meta.json
@@ -1,6 +1,6 @@
 {
-  "rollup-node": "Run a Node in the Superchain",
   "architecture": "Architecture",
+  "rollup-node": "Run a Node in the Superchain",
   "tutorials": "Tutorials",
   "configuration": "Configuration",
   "management": "Node Management",
diff --git a/pages/builders/node-operators/rollup-node.mdx b/pages/builders/node-operators/rollup-node.mdx
index 41091e6a9..38125c94c 100644
--- a/pages/builders/node-operators/rollup-node.mdx
+++ b/pages/builders/node-operators/rollup-node.mdx
@@ -51,7 +51,7 @@ OP Stack rollup nodes can be configured for individual needs. The following step
   This is an **optional** feature but highly recommended for node providers.
 
   <Callout type="info">
-    Additional configuration options exist for [`op-geth`](/builders/node-operators/configuration/geth-config) and [`op-node`](/builders/node-operators/configuration/node-config), respectively.
+    Additional configuration options exist for [`op-geth`](/builders/node-operators/configuration/execution-config) and [`op-node`](/builders/node-operators/configuration/consensus-config), respectively.
   </Callout>
 </Steps>