From da85b510dd7683165f0d31c18a838ca2aea43f60 Mon Sep 17 00:00:00 2001
From: srdusr <99972264+srdusr@users.noreply.github.com>
Date: Sun, 30 Aug 2026 12:32:00 +0200
Subject: Update README

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 54c3e3a..b9fe5ea 100644
--- a/README.md
+++ b/README.md
@@ -577,7 +577,7 @@ engine, and the TUI restarting (or crashing) never interrupts capture.
 Capture fidelity is the other core design constraint: for HTTP/1.1
 traffic, request and response bytes stored in history are exactly what
 was read off the wire - captured via a `net.Conn` wrapper that records
-bytes as `net/http`'s own (memory-safe, battle-tested) parser consumes
+bytes as `net/http`'s own (memory-safe) parser consumes
 them, rather than re-serializing a parsed representation. For HTTP/2,
 which has no meaningful single "raw bytes" form, the stored
 representation is a reconstruction, and every stored entry says which
-- 
cgit v1.2.3