Accuracy and readability pass across all six prose pages

- README: rewrite intro to explain what the API is, how it extends
  Node RPC, who maintains it, and how it relates to other Stacks APIs
- usage: normalize "Stacks API" → "Stacks Blockchain API" for
  consistency across the section; fix "api-key" → "API key"
- architecture: correct inaccurate claim that the API implements
  Rosetta/Mesh (it was removed; replaced by standalone Mesh API);
  add repo link to Development Setup for context
- pagination: remove misleading empty object {} from sample JSON
- nonce-handling: fix grammar "For all transactions go through" →
  "For all transactions to go through"
- requesting-proofs: fix wording "endpoints will request the proof" →
  "endpoints return the proof"

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: 2 people

docs/reference/api/stacks-blockchain-api/README.md

@@ -4,22 +4,20 @@
 For the complete OpenAPI spec, navigate [here](https://raw.githubusercontent.com/hirosystems/stacks-blockchain-api/master/openapi.yaml).
 {% endhint %}
 
-The Stacks API provides comprehensive access to Stacks blockchain data through a high-performance REST interface. Built on cached responses and optimized indexing, it delivers transaction data, smart contract information, account balances, and block details with minimal latency.
+The Stacks Blockchain API is a REST API developed and hosted by [Hiro](https://www.hiro.so/) that extends the [Stacks Node RPC API](../stacks-node-rpc/) with additional indexed endpoints. While every Stacks node exposes a minimal set of RPC endpoints (account balances, contract calls, transaction broadcasting), the Blockchain API continuously ingests and indexes on-chain activity into a PostgreSQL database, making it possible to query transaction history, token transfers, smart contract events, and paginated lists of blocks — data that is not directly available from a Stacks node alone.
+
+The public base URL is `https://api.hiro.so`. No infrastructure setup is required, so you can start querying immediately.
 
 <details>
 
 <summary>Who is this API for?</summary>
 
-The Stacks Blockchain API is a hosted, indexed REST API that caches and indexes on-chain data so you can query it efficiently. It is distinct from the [Stacks Node RPC API](../stacks-node-rpc/), which exposes only the minimal set of endpoints built into every Stacks node.
+The Stacks Blockchain API is the recommended API for wallets, dApps, explorers, and general developers who need rich query capabilities without running their own node. It proxies all standard [Stacks Node RPC](../stacks-node-rpc/) endpoints and adds the `/extended/` family of indexed endpoints on top.
 
-If you need rich query capabilities (transaction history, token transfers, smart contract events, paginated lists, etc.) without running your own infrastructure, the Stacks Blockchain API is the right choice.
+If you need a more decentralized setup or want direct access to the raw node RPC without a third-party service, see the [Stacks Node RPC API](../stacks-node-rpc/). For exchange or institutional integrations using the Coinbase Mesh standard, see the [Stacks Mesh API](../stacks-mesh-api/).
 
 </details>
 
-{% hint style="info" %}
-This API is developed and hosted by [Hiro](https://www.hiro.so/). The public base URL is `https://api.hiro.so`.
-{% endhint %}
-
 ### Key features
 
 - **Real-time data ingestion** -- Continuously indexes blockchain activity as it happens

docs/reference/api/stacks-blockchain-api/architecture.md

@@ -24,7 +24,7 @@ The `stacks-node` has its own minimal set of http endpoints referred to as `RPC
 The Stacks Blockchain API implements additional endpoints that provide data unavailable directly from Stacks nodes due to various constraints.
 
 - The `stacks-node` may not persist certain data or may not serve it efficiently to many clients. For instance, while it can return the current STX balance of an account, it cannot provide a history of account transactions.
-- The API implements the [Mesh](https://github.com/coinbase/mesh-specifications) specification (formerly Rosetta) by Coinbase, an open standard designed to simplify blockchain deployment and interaction.
+- The API previously included an embedded Rosetta implementation, but this was removed in favor of the standalone [Stacks Mesh API](../stacks-mesh-api/).
 - The API includes support for the Blockchain Naming System (BNS) endpoints.
 - For Express.js routes, see [`/src/api/routes`](https://github.com/hirosystems/stacks-blockchain-api/tree/master/src/api/routes) in the API repo.
 
@@ -52,6 +52,6 @@ All http endpoints and responses are defined in OpenAPI and JSON Schema.
 
 ## Development Setup
 
-The easiest/quickest way to develop in this repo is using the VS Code debugger. It uses docker-compose to set up a stacks-node and Postgres instance.
+To contribute to the [Stacks Blockchain API codebase](https://github.com/hirosystems/stacks-blockchain-api), the easiest way to get started is using the VS Code debugger. It uses docker-compose to set up a stacks-node and Postgres instance.
 
 Alternatively, you can run `npm run dev:integrated` which does the same thing but without a debugger.

docs/reference/api/stacks-blockchain-api/nonce-handling.md

@@ -24,4 +24,4 @@ The `possible_next_nonce` property is the nonce suggested for a given principal'
 
 The `detected_missing_nonces` property finds any non-contiguous nonces after inspecting transactions from blocks and the mempool. For example, for a given principal, if the latest transaction included in a block has a nonce of 5, and there's only one transaction in the mempool with nonce 7, then it indicates that something likely went wrong with transaction with nonce 6 (either it was not created or broadcasted correctly by a client, or it was dropped for whatever reason). This is a strong indication that the mempool transaction with nonce 7 will never be mined since the previous nonce is missing.
 
-Clients that continue to broadcast transactions with the `possible_next_nonce` property of 8, then 9, then 10, will likely result in all of their pending/mempool transactions never going through. For all transactions go through, clients should first use any missing nonces before using the suggested `possible_next_nonce`.
+Clients that continue to broadcast transactions with the `possible_next_nonce` property of 8, then 9, then 10, will likely result in all of their pending/mempool transactions never going through. For all transactions to go through, clients should first use any missing nonces before using the suggested `possible_next_nonce`.

docs/reference/api/stacks-blockchain-api/pagination.md

@@ -44,8 +44,7 @@ Here is a sample response:
       "events": [],
       "tx_type": "coinbase",
       "coinbase_payload": {}
-    },
-    {}
+    }
   ]
 }
 ```

docs/reference/api/stacks-blockchain-api/requesting-proofs.md

@@ -4,7 +4,7 @@ description: Understand proof requests from API endpoints.
 
 # Requesting proofs
 
-Several endpoints will request the [MARF Merkle Proof](https://github.com/stacksgov/sips/blob/main/sips/sip-004/sip-004-materialized-view.md#marf-merkle-proofs) by default.
+Several endpoints return the [MARF Merkle Proof](https://github.com/stacksgov/sips/blob/main/sips/sip-004/sip-004-materialized-view.md#marf-merkle-proofs) by default.
 
 Provided with the proof, a client can verify the value, cumulative energy spent, and the number of confirmations for the response value provided by the API.
 

docs/reference/api/stacks-blockchain-api/usage.md

@@ -4,7 +4,7 @@ description: Learn the basics of using the Stacks Blockchain API.
 
 # Basic usage
 
-The Stacks API is built on REST principles, enforcing HTTPS for all requests to ensure data security, integrity, and privacy.
+The Stacks Blockchain API is built on REST principles, enforcing HTTPS for all requests to ensure data security, integrity, and privacy.
 
 ## Base URL
 
@@ -23,7 +23,7 @@ curl -L 'https://api.hiro.so/extended' \
 
 ## Authentication
 
-If you are using an api-key, replace `$HIRO_API_KEY` with your secret API key.
+If you are using an API key, replace `$HIRO_API_KEY` with your secret API key.
 
 ```bash
 curl -L 'https://api.hiro.so/extended' \
@@ -33,7 +33,7 @@ curl -L 'https://api.hiro.so/extended' \
 
 ## Response codes
 
-The Stacks API uses standard HTTP response codes to indicate request success or failure.
+The Stacks Blockchain API uses standard HTTP response codes to indicate request success or failure.
 
 | Code | Description |
 |------|-------------|