← Commit history

README: drop filler intensifiers

John Lauer ·7703abfb91 ·1mo ago ·parent d256226
1 file changed +4−4
README.md+4−4
@@ -4,7 +4,7 @@ the edge-tts wrapper with Adom pronunciation overrides and a source-hash cache. Your AI speaks through it; you listen instead of read. -## The three ways people actually use it+## The three ways people use it  ### 1. While you're driving (hands-free) @@ -13,11 +13,11 @@ You're in the car and can't read the screen. Just say: > "Read me your last answer, I'm driving."  Claude composes the reply, speaks it through the shared player, and (this is the-important part) **verifies you actually heard it**. Clips buffer through dead zones+important part) **verifies you heard it**. Clips buffer through dead zones and hotspot drops, retry if they never reached your ears, and land in a replayable History if two updates arrive back-to-back. The full hands-free contract lives in the [adom-tts skill](skills/adom-tts/SKILL.md) (also on this page's **Skills** tab); it-triggers on the words you'd actually say: "read it to me", "read that back", "I'm in+triggers on the words you'd say: "read it to me", "read that back", "I'm in the car", "narrate the answer", and many more.  ### 2. At your laptop, when you'd rather listen than read@@ -119,7 +119,7 @@ This package has **zero registry dependencies**: it installs and runs standalone - **One shared player, many AI threads**: a single persistent server owns one webview;   clips from every thread play sequentially, never overlapping, each labeled with its   thread and description.-- **Verified playback**: `--confirm` blocks until the human actually heard the clip;+- **Verified playback**: `--confirm` blocks until the human heard the clip;   `check` answers "did mine play?"; every command returns hints teaching the AI the   next correct step. - **Never lose a clip**: buffering while your device is offline (up to 10 min),