Fix llms descriptions (#2632)

* feat: add script to generate and include llms.txt in build

* chore: minor changes

* chore: make sure docs start with description

* chore: fix descriptions

* feat: add description to docs

* Apply suggestions from code review

---------

Co-authored-by: Matias Benary <matiasbenary@gmail.com>
Co-authored-by: Guillermo Alejandro Gallardo Diez <gagdiez@MacBookPro.home>

Author: 3 people

docs/ai/shade-agents/examples.md

@@ -4,8 +4,6 @@ title: What can you Build?
 sidebar_label: What can you Build?
 ---
 
-# What can you build with Shade Agents?
-
 With their extensive list of features, Shade Agents unlock a wide range of new use cases, enable many previously centralized apps to become decentralized, and change how blockchain applications are designed. 
 
 ## Shade Agent Features

docs/ai/shade-agents/production/deploying.md

@@ -6,8 +6,6 @@ sidebar_label: Deploying an Agent
 
 import { SigsSupport } from '@site/src/components/sigsSupport';
 
-# Deploying an Agent
-
 In this section we'll walk through deploying your first Shade Agent. The template we're using is a simple Shade Agent built with NextJS that acts as a verifiable ETH price oracle. It takes prices from two different APIs, takes the average and then pushes the price to an Ethereum contract.  
 
 We'll cover two deployment scenarios:

docs/chain-abstraction/meta-tx.md

@@ -4,11 +4,7 @@ title: Meta Transactions
 sidebar_label: NEP-366
 ---
 
-[NEP-366](https://github.com/near/NEPs/pull/366) introduced the concept of meta
-transactions to Near Protocol. This feature allows users to execute transactions
-on NEAR without owning any gas or tokens. In order to enable this, users
-construct and sign transactions off-chain. A third party (the relayer) is used
-to cover the fees of submitting and executing the transaction.
+[NEP-366](https://github.com/near/NEPs/pull/366) introduced the concept of meta transactions to Near Protocol. This feature allows users to execute transactions on NEAR without owning any gas or tokens. In order to enable this, users construct and sign transactions off-chain. A third party (the relayer) is used to cover the fees of submitting and executing the transaction.
 
 ---
 

docs/chain-abstraction/omnibridge/how-it-works.md

@@ -4,8 +4,6 @@ sidebar_label: How It Works
 title: How Omni Bridge Works
 ---
 
-## Background
-
 The journey toward truly trustless cross-chain communication took a significant leap forward when the NEAR team [created the first trustless bridge with Ethereum](https://near.org/blog/the-rainbow-bridge-is-live) (Rainbow Bridge). This pioneering achievement demonstrated that completely trustless cross-chain communication was possible, marking a crucial step toward the vision of chain abstraction. However, this approach relied on implementing a NEAR light client directly on Ethereum - essentially requiring Ethereum to understand and verify NEAR's complex blockchain rules.
 
 Omni Bridge introduces a more elegant solution using Chain Signatures. Instead of running light clients on each destination chain, it leverages Chain Signature's MPC Service to enable secure cross-chain message verification without the overhead of light client verification. This new approach reduces verification times from hours to minutes while significantly reducing gas costs across all supported chains.

docs/chain-abstraction/wallet.md

@@ -3,8 +3,6 @@ id: wallet
 title: Wallet Chain Key Rules 
 ---
 
-## Overview
-
 In this article you'll find details on how to parse and present multichain transactions to the user so they can take an informed decision about their wallet's assets, while minimizing the number of times the user has to consent.
 You'll also learn how to ensure that a signature on one chain is not used to take a meaningful action on another chain.
 

docs/chain-abstraction/what-is.md

@@ -6,8 +6,6 @@ import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
 import {CodeTabs, Language, Github} from "@site/src/components/codetabs";
 
-# What is Chain Abstraction?
-
 Blockchain development today faces a critical challenge: users need to understand complex blockchain concepts, manage multiple wallets, and deal with different networks just to use basic applications. Chain abstraction solves this by making blockchain technology invisible to end users while preserving all of the underlying benefits.
 
 ![img](/docs/assets/welcome-pages/2.chain-abstraction.png)

docs/data-infrastructure/big-query.md

@@ -4,6 +4,10 @@ title: BigQuery Public Dataset
 sidebar_label: BigQuery
 ---
 
+This document provides an overview of the  BigQuery public dataset that allows users to query historical on-chain data from the NEAR Protocol. It includes setup instructions, example queries, and information about the available data structures.
+
+# NEAR Public Lakehouse
+
 Blockchain data indexing in NEAR Public Lakehouse is for anyone wanting to understand blockchain data. This includes:
 
 - **Users**: create queries to track NEAR assets, monitor transactions, or analyze on-chain events at a massive scale.

docs/data-infrastructure/indexers.md

@@ -2,8 +2,6 @@
 sidebar_label: "Intro to Indexers"
 ---
 
-# Introduction to Indexers
-
 Here you will find everything you need to know in order to familiarize yourself with the concept of indexers and even build your own one.
 
 :::info Disclaimer

docs/data-infrastructure/lake-framework/building-indexers/js-lake-indexer.md

@@ -3,20 +3,20 @@ id: js-lake-indexer
 title: JS basic tutorial
 sidebar_label: JS basic tutorial
 ---
+This tutorial will guide you through creating a simple indexer using the JavaScript version of the NEAR Lake Framework. The indexer will print block height and number of shards to the console.
 
-# NEAR Lake indexer basic tutorial
+# NEAR Lake Framework JavaScript Indexer Tutorial
 
+Recently we have [published a JavaScript version of the NEAR Lake Framework](https://www.npmjs.com/package/near-lake-framework) on npmjs.org
+
+We want to empower you with a basic tutorial on how to use the JavaScript Library. Let's get started!
 
 :::info Source code for the tutorial
 
 [`near-examples/near-lake-raw-printer-js`](https://github.com/near-examples/near-lake-raw-printer-js): source code for the tutorial on how to create an indexer that prints block height and number of shards
 
 :::
 
-Recently we have [published a JavaScript version of the NEAR Lake Framework](https://www.npmjs.com/package/near-lake-framework) on npmjs.org
-
-We want to empower you with a basic tutorial on how to use the JavaScript Library. Let's get started!
-
 
 ## Requirements
 

docs/data-infrastructure/lake-framework/building-indexers/nft-indexer.md

@@ -2,24 +2,22 @@
 sidebar_label: NFT Indexer
 ---
 
-# Building an NFT indexer
+This tutorial will guide you through building a simple NFT indexer using the JavaScript version of the [NEAR Lake Framework JS](/data-infrastructure/lake-framework/near-lake-framework). The indexer will listen for `nft_mint` events and print relevant data about newly minted NFTs.
 
+The indexer is watching for `nft_mint` [Events](https://nomicon.io/Standards/EventsFormat) and prints some relevant data:
+- `receiptId` of the [Receipt](/data-infrastructure/lake-data-structures/receipt) where the mint has happened
+- Marketplace
+- NFT owner account name
+- Links to the NFTs on the marketplaces
+
+The final source code is available on the GitHub [`near-examples/near-lake-nft-indexer`](https://github.com/near-examples/near-lake-nft-indexer)
 
 :::note Source code for the tutorial
 
 [`near-examples/near-lake-nft-indexer`](https://github.com/near-examples/near-lake-nft-indexer): source code for this tutorial
 
 :::
 
-## The End
-
-This tutorial ends with a working NFT indexer built on top [NEAR Lake Framework JS](/data-infrastructure/lake-framework/near-lake-framework). The indexer is watching for `nft_mint` [Events](https://nomicon.io/Standards/EventsFormat) and prints some relevant data:
-- `receiptId` of the [Receipt](/data-infrastructure/lake-data-structures/receipt) where the mint has happened
-- Marketplace
-- NFT owner account name
-- Links to the NFTs on the marketplaces
-
-The final source code is available on the GitHub [`near-examples/near-lake-nft-indexer`](https://github.com/near-examples/near-lake-nft-indexer)
 
 ## Motivation