fix: broken links (#2549)

<!--
Please read and fill out this form before submitting your PR.

Please make sure you have reviewed our contributors guide before
submitting your
first PR.

NOTE: PR titles should follow semantic commits:
https://www.conventionalcommits.org/en/v1.0.0/
-->

## Overview

Fixes some broken links

<!-- 
Please provide an explanation of the PR, including the appropriate
context,
background, goal, and rationale. If there is an issue with this
information,
please provide a tl;dr and link the issue. 

Ex: Closes #<issue number>
-->

Author: Manav-Aggarwal

docs/guides/deploy/local.md

@@ -216,7 +216,7 @@ Since our chain is running in a docker container, we want to enter the docker co
 docker exec -it gm-world sh
 ```
 
-Now that you are in the docker container, you can interact with the chain using the `gmd` command and the example you used in the [gm-world tutorial](/docs/guides/gm-world.md).
+Now that you are in the docker container, you can interact with the chain using the `gmd` command and the example you used in the [gm-world tutorial](/guides/gm-world.md).
 
 Once you are done interacting with your chain, you can exit out of your docker container with:
 

docs/guides/deploy/overview.md

@@ -6,7 +6,7 @@ description: This page provides an overview of some common ways to deploy chains
 
 One of the benefits of building chains with Evolve is the flexibility you have as a developer to choose things like the DA layer, the settlement scheme, and the execution environment.
 
-You can learn more about Evolve architecture [here](/docs/learn/specs/overview.md).
+You can learn more about Evolve architecture [here](/learn/specs/overview.md).
 
 The challenge that comes with this flexibility is that there are more services that now need to be deployed and managed while running your chain.
 

docs/guides/deploy/testnet.md

@@ -2,7 +2,7 @@
 
 This tutorial is going to show you how to deploy a Evolve testnet, focusing on the architecture choices and components that make up a complete EVM-based chain deployment.
 
-You can learn more about Evolve EVM architecture [here](/docs/learn/execution.md).
+You can learn more about Evolve EVM architecture [here](/learn/execution.md).
 
 <!-- markdownlint-disable MD033 -->
 <script setup>
@@ -90,7 +90,7 @@ graph TB
 
 ## 💻 Pre-requisites {#prerequisites}
 
-Make sure you understand the sequencing topology you want to use by reading the [Sequencing Overview](/docs/learn/sequencing/overview.md).
+Make sure you understand the sequencing topology you want to use by reading the [Sequencing Overview](/learn/sequencing/overview.md).
 
 ## 🛠️ Dependencies {#dependencies}
 
@@ -107,7 +107,7 @@ Currently, Evolve supports one sequencing implementation:
 - **Advantages**: Easy setup, fast block production, independence from DA block time
 - **Requirements**: One sequencer node, multiple optional full nodes
 
-For detailed information about sequencing topologies, see the [Sequencing Overview](/docs/learn/sequencing/overview.md) and [Single Sequencer](/docs/learn/sequencing/single.md) documentation.
+For detailed information about sequencing topologies, see the [Sequencing Overview](/learn/sequencing/overview.md) and [Single Sequencer](/learn/sequencing/single.md) documentation.
 
 ## 🏗️ Deployment Architecture {#deployment-architecture}
 
@@ -300,8 +300,8 @@ Congratulations again! You now know how to deploy Evolve EVM chains and understa
 
 For detailed setup instructions, see:
 
-- [Single Sequencer Setup Guide](/docs/guides/evm/single.md) - Step-by-step deployment instructions
-- [RETH Backup Guide](/docs/guides/evm/reth-backup.md) - Data protection and backup procedures
-- [Celestia DA Guide](/docs/guides/da/celestia-da.md) - Connecting to Celestia networks
+- [Single Sequencer Setup Guide](/guides/evm/single.md) - Step-by-step deployment instructions
+- [RETH Backup Guide](/guides/evm/reth-backup.md) - Data protection and backup procedures
+- [Celestia DA Guide](/guides/da/celestia-da.md) - Connecting to Celestia networks
 
 You can also learn more about local deployments in our [Docker Compose guide](/docs/guides/deploy/local.md).

docs/index.md

@@ -15,22 +15,22 @@ hero:
   actions:
     - theme: brand
       text: Quick start
-      link: /docs/guides/quick-start
+      link: /guides/quick-start
     - theme: alt
       text: Introduction
-      link: /docs/learn/about
+      link: /learn/about
 
 features:
   - title: Full Control Over Execution
     details: Design your network exactly how you want it. Choose your VM, customize your execution environment, and maintain complete control without middlemen or revenue share.
-    link: /docs/learn/about#why-evolve
+    link: /learn/about#why-evolve
     icon: 🚀
   - title: Speed to Traction
     details: Get to market fast with infrastructure that adapts to your app—not the other way around. Skip the complexity and start building what matters; your product.
-    link: /docs/learn/execution
+    link: /learn/execution
     icon: ⚡
   - title: No Validator Overhead
     details: Skip the complexity of running validators. Focus on building your application while Celestia handles consensus and data availability.
-    link: /docs/learn/about
+    link: /learn/about
     icon: 🛡️
 ---

docs/src/openapi-rpc.json

@@ -1,18 +1,18 @@
 {
   "openapi": "3.1.0",
   "info": {
-    "title": "Rollkit API",
+    "title": "Evolve API",
     "description": "This API provides access to Signer, Store, P2P, and Health services.\n\n## Services\n\n* **Signer Service** - Sign messages and retrieve public keys\n* **Store Service** - Access blocks, state, and metadata\n* **P2P Service** - Network and peer information\n* **Health Service** - Node health checks and simple HTTP endpoints\n\n## Protocols\n\n### gRPC-Web Protocol\n\nMost endpoints use gRPC-Web protocol over HTTP/1.1 with JSON encoding. Requests are made via POST with `Content-Type: application/json`.\n\n### Simple HTTP Endpoints\n\nSome endpoints (like `/health/live`) are simple HTTP GET requests that return plain text responses for basic monitoring and health checks.",
     "version": "1.0.0",
     "contact": {
-      "name": "Rollkit Team",
-      "url": "https://rollkit.dev"
+      "name": "Evolve Team",
+      "url": "https://ev.xyz"
     }
   },
   "servers": [
     {
       "url": "http://localhost:7331",
-      "description": "A local Rollkit instance configured to provide a remote procedure call (RPC) endpoint, actively listening for connections on TCP port 7331."
+      "description": "A local Evolve instance configured to provide a remote procedure call (RPC) endpoint, actively listening for connections on TCP port 7331."
     }
   ],
   "tags": [