From 5d32b363da45e366193759ea5993fbc4bfee7a00 Mon Sep 17 00:00:00 2001
From: Jordan Ritter <jpr5@darkridge.com>
Date: Thu, 5 Mar 2026 09:21:05 -0800
Subject: [PATCH] docs: rewrite Why llmock section to lead with the problem

Tests hitting real LLM APIs cost money, time out, and are flaky.
The old copy focused on multi-process architecture; the new copy
leads with what users actually care about.
---
 docs/index.html | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/docs/index.html b/docs/index.html
index 8609ec4..7a2765d 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -946,10 +946,11 @@ <h1>Deterministic <span class="highlight">mock LLM</span> server for testing</h1
     <section id="features" class="reveal">
       <div class="container">
         <span class="section-label">Why llmock</span>
-        <h2 class="section-title">Everything you need to test AI integrations</h2>
+        <h2 class="section-title">Stop paying for flaky tests</h2>
         <p class="section-desc">
-          Built for E2E test suites where multiple processes — your app, agent workers, framework
-          runtimes — all need to hit the same mock endpoint.
+          Tests that hit real LLM APIs — OpenAI, Gemini, Anthropic — cost money, time out, and
+          produce non-deterministic results. llmock replaces those calls with immediate,
+          deterministic responses from a real HTTP server any process on the machine can reach.
         </p>
 
         <div class="features-grid">