update chainhooks copy for evaluate (#1106)

* update redirects

* update locale configurations

* update copy

* update refs to chainhook -> chainhooks

* fix link validation for locale

* update locale content

* update chainhook copy

* update locale lockfile

* fix(api-playground): fix body schema and skip empty JSON headers

* feat(api-playground): persist api key in session storage

* docs(chainhooks): add get-secret reference page and sync  metadata

* fix: lint

* copy updates + minor bug fixes

* update copy

Author: ryanwaits

content/docs/en/apis/chainhooks-api/reference/chainhooks/evaluate-chainhook.mdx

@@ -5,6 +5,10 @@ description: Queues an on-demand evaluation job for a specific block
 full: true
 ---
 
+Use this endpoint to replay a single block (historical) against an existing chainhook so you can debug delivery issues, re-run missed events, or backfill data after a filter change. Provide either a `block_height` or `index_block_hash` to pinpoint the block you evaluate.
+
+The evaluation job returns `204 No Content`; if your filters match, the webhook payload is delivered to the hook's configured action just like a live event.
+
 <APIPage
   document="./openapi/chainhook-api.json"
   operations={[{ path: '/me/{uuid}/evaluate', method: 'post' }]}

content/docs/en/apis/chainhooks-api/reference/chainhooks/get-chainhook.mdx

@@ -1,6 +1,6 @@
 ---
-title: Get a specific chainhook
-sidebarTitle: Get a specific chainhook
+title: Get a chainhook
+sidebarTitle: Get a chainhook
 description: Returns a chainhook by its UUID
 full: true
 ---

content/docs/en/apis/chainhooks-api/usage.mdx

@@ -134,7 +134,7 @@ curl https://api.testnet.hiro.so/chainhooks/v1/me/ \
   -H "x-api-key: YOUR_API_KEY"
 ```
 
-### Get a Specific Chainhook
+### Get a chainhook
 
 ```bash
 curl https://api.testnet.hiro.so/chainhooks/v1/me/{uuid} \

content/docs/en/apis/platform-api/reference/chainhooks/get.mdx

@@ -1,12 +1,12 @@
 ---
-title: Get a specific chainhook
+title: Get a chainhook
 sidebarTitle: Get
-description: Get a specific chainhook through the Hiro Platform.
+description: Get a chainhook through the Hiro Platform.
 full: true
 ---
 
 <APIPage
   document="./openapi/platform-api.json"
   operations={[{ path: '/v1/ext/{apiKey}/chainhooks/{chainhookUuid}', method: 'get' }]}
   hasHead={false}
-/>
+/>

content/docs/en/tools/chainhooks/(chainhook-sdk)/evaluate.mdx

@@ -1,9 +1,9 @@
 ---
-title: Evaluate a specific block
-description: Run your chainhooks against specific blocks for testing, debugging, and historical indexing.
+title: Replay a block
+description: Replay any block height or hash against a chainhook to debug, backfill, or re-process historical events.
 ---
 
-The evaluate endpoint replays a single block against one of your registered chainhooks so you can validate filters without waiting for live traffic.
+The evaluate endpoint replays any single block you choose—live or historical—against one of your registered chainhooks so you can validate filters without waiting for live traffic. Provide either a block height or block hash to target the exact block you care about.
 
 Use it to reproduce missed deliveries, inspect payload schemas after filter changes, or test webhook infrastructure with known blocks before enabling a hook in production.
 
@@ -56,13 +56,13 @@ Returns HTTP `204 No Content`. If filters match, webhook payload is sent to your
 
 | Use Case | Description | Example |
 |----------|-------------|---------|
-| **Debug** | Investigate missed events | Evaluate specific block that should have triggered |
-| **Backfill** | Index historical data | Process past blocks after creating chainhook |
-| **Re-process** | Fix webhook handler issues | Re-evaluate after fixing bugs |
+| **Debug** | Investigate missed events | Replay a block height that should have triggered |
+| **Backfill** | Index historical data | Process older blocks created before the hook existed |
+| **Re-process** | Fix webhook handler issues | Re-evaluate a block after patching infrastructure |
 
 ## Next steps
 
 :::next-steps
-- [Register & Enable](/tools/chainhooks/create): Create chainhooks to evaluate
 - [Filter Reference](/tools/chainhooks/reference/filters): Configure which events to match
+- [Evaluate endpoint](/apis/chainhooks-api/reference/chainhooks/evaluate-chainhook): Replay past blocks through the API
 :::

content/docs/en/tools/chainhooks/(chainhook-sdk)/introduction.mdx

@@ -124,7 +124,7 @@ The SDK provides the following methods:
 |--------|-------------|
 | `registerChainhook()` | Create a new chainhook |
 | `getChainhooks()` | List all your chainhooks (with pagination) |
-| `getChainhook()` | Get a specific chainhook by UUID |
+| `getChainhook()` | Get a chainhook by UUID |
 | `updateChainhook()` | Update an existing chainhook |
 | `deleteChainhook()` | Delete a chainhook |
 

content/docs/en/tools/chainhooks/(chainhook-sdk)/secrets.mdx

@@ -26,7 +26,7 @@ When you create a secret, our Chainhooks service attaches an `Authorization: Bea
 
 ### Create/rotate consumer secret
 
-```ts -nc server.ts
+```ts server.ts -nc
 import { ChainhooksClient, CHAINHOOKS_BASE_URL } from '@hirosystems/chainhooks-client';
 
 const client = new ChainhooksClient({
@@ -40,11 +40,7 @@ const secret = await client.rotateConsumerSecret(chainhookUuid).secret;
 
 ### Example Fastify server
 
-```ts -nc -n
-import Fastify from 'fastify';
-
-const server = Fastify();
-
+```ts server.ts -n
 server.post('/webhook', async (request, reply) => {
   if (!secret) {
     reply.code(503).send({ error: 'consumer secret unavailable' });