chore: add missing anchors, frontmatter and cleanup duplicate copy

docs/base-chain/node-operators/node-providers.mdx

@@ -182,7 +182,7 @@ import {HeaderNoToc} from "/snippets/headerNoToc.mdx";
 
 ## Unifra
 
-[Unifra](https://www.unifra.io) is a Web3 developer platform that provides tools, APIs, and node infrastructure, and provides access to Base nodes that are nodes are reliable, scalable, and easy to use.
+[Unifra](https://www.unifra.io) is a Web3 developer platform that provides tools, APIs, and node infrastructure, and provides access to Base nodes that are reliable, scalable, and easy to use.
 
 <HeaderNoToc title="Supported Networks"/>
 

docs/base-chain/node-operators/performance-tuning.mdx

@@ -1,6 +1,7 @@
 ---
 title: Node Performance
 sidebarTitle: Performance Tuning
+description: Hardware specifications, storage requirements, client recommendations, and configuration settings for running a performant Base node.
 ---
 
 This guide provides recommendations for hardware, client software, and configuration settings to optimize the performance of your Base node.

docs/base-chain/node-operators/snapshots.mdx

@@ -1,6 +1,7 @@
 ---
 title: Node Snapshots
 sidebarTitle: Snapshots
+description: Download and restore Base node snapshots to significantly reduce initial sync time for both archive and pruned nodes.
 ---
 
 Using a snapshot significantly reduces the initial time required to sync a Base node. Snapshots are updated regularly.

docs/base-chain/node-operators/troubleshooting.mdx

@@ -1,6 +1,7 @@
 ---
-sidebarTitle: Troubleshooting
 title: Node Troubleshooting
+sidebarTitle: Troubleshooting
+description: Solutions to common issues when setting up and running a Base node, covering sync problems, networking, snapshots, and performance.
 ---
 
 This guide covers common issues encountered when setting up and running a Base node using the official [Base Node Docker setup](https://github.com/base/node) and provides steps to diagnose and resolve them.
@@ -17,7 +18,7 @@ Before diving into specific issues, here are some general steps that often help:
 
 3. **Check Resource Usage**: Monitor your server’s CPU, RAM, disk I/O, and network usage. Performance issues are often linked to insufficient resources. Tools like `htop`, `iostat`, and `iftop` can be helpful.
 
-4. **Verify RPC Endpoints**: Use `curl` to check if the L2 client’s RPC endpoint is responding (see [Running a Base Node > Verify Node is Running](/base-chain/node-operators/run-a-base-node#verify-node-is-running)). Also, verify your L1 endpoints are correct and accessible from the node server.
+4. **Verify RPC Endpoints**: Use `curl` to check if the L2 client’s RPC endpoint is responding (see [Running a Node](/base-chain/node-operators/run-a-base-node#running-a-node)). Also, verify your L1 endpoints are correct and accessible from the node server.
 
 5. **Check L1 Node**: Ensure your configured L1 node (Execution and Consensus) is fully synced, healthy, and accessible. Issues with the L1 node will prevent the L2 node from syncing correctly.
 
@@ -107,7 +108,7 @@ Refer to the [Snapshots](/base-chain/node-operators/snapshots) guide for the cor
 - **Issue**: Node has low peer count.  
     - **Check**: P2P port accessibility. Ensure `30303` (TCP/UDP) and `9222` (TCP/UDP for Reth discv5) are not blocked by a firewall on the host or network.  
     - **Check**: Node logs for P2P errors.  
-    - **Action**: If behind NAT, configure the `--nat=extip:<your-ip>` flag via `ADDITIONAL_ARGS` in the `.env` file (see [Advanced Configuration](/base-chain/node-operators/run-a-base-node#improving-peer-connectivity)).
+    - **Action**: If behind NAT, configure the `--nat=extip:<your-ip>` flag via `ADDITIONAL_ARGS` in the `.env` file (see [Networking](/base-chain/node-operators/run-a-base-node#networking)).
 
 - **Issue**: Port conflicts reported in logs or `docker compose up` fails.  
     - **Check**: Are other services running on the host using the default ports (`8545`, `8546`, `8551`, `6060`, `7545`, `30303`)? Use