docs: fix broken links, stale --rollkit.* flag prefixes, and escaped backticks

- Fix forced-inclusion.md: based.md → based-sequencing.md (2 links)
- Fix block-lifecycle.md: da.md → data-availability.md (2 links)
- Fix reference/specs/overview.md: p2p.md → learn/specs/p2p.md
- Fix running-nodes/full-node.md: relative paths to guides/
- Fix what-is-evolve.md: remove escaped backticks around ev-node
- Replace all --rollkit.* flags with --evnode.* in ev-node-config.md
- Fix visualizer.md: --rollkit.rpc → --evnode.rpc

Author: alpe

docs/concepts/block-lifecycle.md

@@ -428,7 +428,7 @@ The retrieval system uses persistent caches for both headers and data:
 - Enables efficient sync from P2P and DA sources
 - Maintains namespace migration state for optimized retrieval
 
-For more details on DA integration, see the [Data Availability specification](./da.md).
+For more details on DA integration, see the [Data Availability specification](./data-availability.md).
 
 #### Out-of-Order Chain Blocks on DA
 
@@ -725,7 +725,7 @@ See [tutorial] for running a multi-node network with both aggregator and non-agg
 
 [7] [Evolve Minimal Header](../../adr/adr-015-rollkit-minimal-header.md)
 
-[8] [Data Availability](./da.md)
+[8] [Data Availability](./data-availability.md)
 
 [9] [Lazy Aggregation with DA Layer Consistency ADR](../../adr/adr-021-lazy-aggregation.md)
 

docs/guides/advanced/forced-inclusion.md

@@ -72,7 +72,7 @@ Epoch [100, 109] (epoch size = 10):
   - Sequencer includes forced tx in blocks before height 110
 ```
 
-See [Based Sequencing](./based.md) for a fully decentralized alternative that relies entirely on forced inclusion.
+See [Based Sequencing](./based-sequencing.md) for a fully decentralized alternative that relies entirely on forced inclusion.
 
 ## Detecting Malicious Sequencer Behavior
 
@@ -113,7 +113,7 @@ Nodes may require a coordinated restart into based sequencing mode, depending on
 - Users submit transactions directly to the DA layer going forward
 - Returning to single sequencer mode requires explicit governance and operational coordination
 
-See [Based Sequencing documentation](./based.md) for details on operating in this mode.
+See [Based Sequencing documentation](./based-sequencing.md) for details on operating in this mode.
 
 ## Advantages
 

docs/guides/running-nodes/full-node.md

@@ -4,11 +4,11 @@
 
 This guide covers how to set up a full node to run alongside a sequencer node in a Evolve-based blockchain network. A full node maintains a complete copy of the blockchain and helps validate transactions, improving the network's decentralization and security.
 
-> **Note: The guide on how to run an Evolve EVM full node can be found [in the evm section](./evm/single.md#setting-up-a-full-node).**
+> **Note: The guide on how to run an Evolve EVM full node can be found [in the evm section](../../guides/evm/single.md#setting-up-a-full-node).**
 
 ## Prerequisites
 
-Before proceeding, ensure that you have completed the [build a chain](./gm-world.md) tutorial, which covers setting-up, building and running your chain.
+Before proceeding, ensure that you have completed the [build a chain](../../guides/gm-world.md) tutorial, which covers setting-up, building and running your chain.
 
 Ensure that you have:
 

docs/guides/tools/visualizer.md

@@ -22,7 +22,7 @@ The DA Visualizer is disabled by default. To enable it, use the following config
 ### Via Command-line Flag
 
 ```bash
-testapp start --rollkit.rpc.enable_da_visualization
+testapp start --evnode.rpc.enable_da_visualization
 ```
 
 ### Via Configuration File

docs/overview/what-is-evolve.md

@@ -14,7 +14,7 @@ Evolve is a launch stack for L1s. It gives you full control over execution — w
 
 Evolve is [open-source](https://github.com/evstack/ev-node), production-ready, and fully composable.
 
-At its core is \`ev-node\`, a modular node that exposes an [Execution interface](https://github.com/evstack/ev-node/blob/main/core/execution/execution.go), — letting you bring any VM or execution logic, including Cosmos SDK or custom-built runtimes.
+At its core is `ev-node`, a modular node that exposes an [Execution interface](https://github.com/evstack/ev-node/blob/main/core/execution/execution.go) — letting you bring any VM or execution logic, including Cosmos SDK or custom-built runtimes.
 
 Evolving from Cosmos SDK?