docs(ha): rename worked examples sections to example configurations

documentation/high-availability/client-failover/concepts.md

@@ -22,7 +22,7 @@ single hard-coded address must be reconfigured and restarted. A failover-aware
 client instead carries the full list of peers and walks that list automatically
 when the current connection breaks.
 
-This page explains the model. The user-facing knobs and worked examples live in
+This page explains the model. The user-facing knobs and examples live in
 the [Configuration](/docs/high-availability/client-failover/configuration/)
 page.
 
@@ -266,6 +266,6 @@ the failover model — split the workload into one connect string per credential
 ## Next steps
 
 - [Configuration](/docs/high-availability/client-failover/configuration/) —
-  the connect-string keys and worked examples for each context.
+  the connect-string keys and examples for each context.
 - [Store-and-forward concepts](/docs/high-availability/store-and-forward/concepts/) —
   how the ingress failover loop interacts with the disk-backed substrate.

documentation/high-availability/client-failover/configuration.md

@@ -79,7 +79,7 @@ the user-visible knobs are:
 | `failover_backoff_initial_ms` | int (ms) | `50` | Starting backoff sleep. Doubles up to the cap. |
 | `failover_backoff_max_ms` | int (ms) | `1000` | Cap on the exponential backoff. With full-jitter, the actual sleep lands in `[0, max)`. |
 
-## Worked examples
+## Example configurations
 
 ### Three-node Enterprise cluster, default failover
 

documentation/high-availability/store-and-forward/configuration.md

@@ -113,7 +113,7 @@ The parser rejects:
 - `sender_id` containing path separators or empty.
 - `request_durable_ack=on` on non-WebSocket transports.
 
-## Worked examples
+## Example configurations
 
 ### Single-node memory-mode producer