Address reviewer feedback from wileyj and rafa-stacks

- Use mainnet API URL with real principal in nonce example (wileyj)
- Remove "Express.js" from routes reference (rafa-stacks)
- Update stale docs link to docs.stacks.co (rafa-stacks)

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

Author: 2 people

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

@@ -26,7 +26,7 @@ The Stacks Blockchain API implements additional endpoints that provide data unav
 - 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 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.
+- For routes, see [`/src/api/routes`](https://github.com/hirosystems/stacks-blockchain-api/tree/master/src/api/routes) in the API repo.
 
 The API creates an "event observer" http server which listens for events from a stacks-node "event emitter".
 
@@ -46,7 +46,7 @@ The API processes and stores these events as relational data in PostgreSQL. For
 All http endpoints and responses are defined in OpenAPI and JSON Schema.
 
 - See [`openapi.yaml`](https://github.com/hirosystems/stacks-blockchain-api/blob/master/openapi.yaml) in the API repo
-- These are used to auto-generate the docs at https://hirosystems.github.io/stacks-blockchain-api/
+- These are used to auto-generate the docs at https://docs.stacks.co/reference/api/stacks-blockchain-api
 - JSON Schemas are converted into TypeScript interfaces, which are used internally by the db controller module to transform SQL query results into the correct object shapes.
 - OpenAPI and JSON Schemas are also used to generate a standalone `@stacks/blockchain-api-client`.
 

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

@@ -8,14 +8,14 @@ In order to prevent "stuck" transactions, you must track the next available nonc
 Stacks Blockchain API provides an endpoint to make nonce handling simpler when using the following command:
 
 ```bash
-curl 'https://api.testnet.hiro.so/extended/v1/address/<principal>/nonces'
+curl 'https://api.hiro.so/extended/v1/address/SP3XXK8BG5X7CRH7W07RRJK3JZJXJ799WX3Y0SMCR/nonces'
 ```
 
 ```json
 {
-  "last_executed_tx_nonce": 5893,
-  "last_mempool_tx_nonce": null,
-  "possible_next_nonce": 5894,
+  "last_executed_tx_nonce": 2789412,
+  "last_mempool_tx_nonce": 2789413,
+  "possible_next_nonce": 2789414,
   "detected_missing_nonces": []
 }
 ```