diff --git a/README.md b/README.md
index a997cc8..7e518b6 100644
--- a/README.md
+++ b/README.md
@@ -191,12 +191,14 @@ The plugin records method, URL, status, headers, textual bodies (capped at 64 KB
 
 ```kotlin
 install(SharinganKtor) {
-    captureBodies = true            // default
+    captureBodies = true            // default — request/response bodies are recorded
     maxBodyBytes = 64 * 1024        // default
     redactedHeaders = setOf("Authorization", "X-Api-Key")
 }
 ```
 
+**Body capture is ON by default.** To capture only metadata (method, URL, status, headers, timing) and never store body text, set `captureBodies = false`. To **start paused** and capture nothing at all until you flip it on — e.g. so a QA build records only the flow you ask for — call `Sharingan.setRecording(false)` at startup, then `Sharingan.setRecording(true)` (or tap Pause/Resume on the Android capture notification) when you're ready. Pausing applies to every protocol, not just HTTP.
+
 Using OkHttp/NSURLSession directly? Log manually with `Sharingan.http.log(...)`.
 
 ### MQTT & BLE — one line per client callback
@@ -246,7 +248,7 @@ More adapters (KMQTT/HiveMQ/Paho callbacks, full Kable wiring, shake-to-open) li
 
 The capture notification shows per-protocol counters, a three-event ticker when expanded, and a Pause/Resume action. It is silent and updated in place. Two things to know:
 
-- **Android 13+:** the notification needs the `POST_NOTIFICATIONS` runtime permission — Sharingan declares it, your app requests it. Without the grant, capture still works; open the browser with `Sharingan.show(context)`.
+- **Android 13+:** the notification needs the `POST_NOTIFICATIONS` runtime permission. Sharingan's `AndroidManifest.xml` declares `<uses-permission android:name="android.permission.POST_NOTIFICATIONS" />`, so manifest merger surfaces it in **your app's merged manifest** (visible in *Merged Manifest* in Android Studio and in the APK). The library **never requests it at runtime** — there is no `requestPermissions` call anywhere in Sharingan, so it can't trigger a permission prompt or change your app's runtime behavior; your app decides whether to ask the user. Without the grant, capture still works silently; open the browser with `Sharingan.show(context)`. Since the debug logger ships only in debug/QA builds, the permission does not reach your release manifest (the `sharingan-noop` release artifact declares nothing).
 - **Do Not Disturb:** because the notification is silent, DND hides it on most devices — `Sharingan.show(context)` always works (wire it to a debug-drawer button or shake gesture).
 
 ### iOS
diff --git a/sharingan/src/commonMain/kotlin/dev/sharingan/HttpEvent.kt b/sharingan/src/commonMain/kotlin/dev/sharingan/HttpEvent.kt
index 7f0d7d9..6fe08fc 100644
--- a/sharingan/src/commonMain/kotlin/dev/sharingan/HttpEvent.kt
+++ b/sharingan/src/commonMain/kotlin/dev/sharingan/HttpEvent.kt
@@ -1,9 +1,22 @@
 package dev.sharingan
 
 /**
- * One phase of an HTTP request's timing waterfall (e.g. `DNS`, `Connect`,
- * `TLS`, `TTFB`, `Download`). Rendered as a proportional bar in the detail
- * screen.
+ * One phase of an HTTP request's timing waterfall, rendered as a proportional
+ * bar in the detail screen.
+ *
+ * [label] is a free-form [String], so any text renders — but stick to the
+ * conventional waterfall vocabulary so phases read consistently across events
+ * and exports. Listed in the order they occur:
+ *
+ * - `DNS` — hostname resolution.
+ * - `Connect` — TCP connection establishment.
+ * - `TLS` — TLS/SSL handshake.
+ * - `TTFB` — time to first byte (request sent → first response byte).
+ * - `Download` — response body transfer.
+ *
+ * The `SharinganKtor` plugin emits the `TTFB`/`Download` split automatically;
+ * supply the earlier phases yourself via `Sharingan.http.log(...)` when your
+ * HTTP stack exposes them.
  */
 public data class TimingPhase(
     public val label: String,