TODO.md

@@ -116,10 +116,10 @@ Run `make frontend-viewport-test` in CI as its own step; it is not part of
   failed writes are written in the order they arrived. Two writes that failed at
   the same time put their reports back in the wrong order when the older failed
   first. One write runs at a time. Each takes the waiting reports only when it
-  starts, after a failed write has put its own back. The write `Append` starts
-  when 10 MiB are waiting waits for any write under way, and `Append` starts no
-  other while it waits. Files written since the start are deleted to make room
-  in the order they were written, after those found at start.
+  starts, after a failed write has put its own back. The write that `Append`
+  starts at 10 MiB waits for any write under way, and `Append` starts no other
+  while it waits. Files written since the start are deleted to make room in the
+  order they were written, after those found at start.
 - 2026-10-19: `DEBUG` unset or empty leaves debug logging off, and any other
   value, `false` and `0` included, turns it on, as the code style guide says
   ([#159](https://git.eeqj.de/sneak/netwatch/issues/159)). No value of it stops
@@ -202,11 +202,11 @@ Run `make frontend-viewport-test` in CI as its own step; it is not part of
   entry, which the client writes itself behind a proxy that appends to the
   header. So a client could choose the address the rate limit counts and the
   request log records. An entry written as an address with a port is read as
-  that address. With only trusted addresses in the header, or an entry that is
-  not an address at all (such as `unknown`) met on the way, the direct peer is
-  used. `X-Real-IP` is read only without `X-Forwarded-For`, and every
-  `X-Forwarded-For` header line is read, not only the first. The image's nginx,
-  and the `TRUSTED_PROXIES=127.0.0.1/32` it starts the backend with, are
+  that address. The direct peer is used when the header holds only trusted
+  addresses, or when the search meets an entry that is not an address at all,
+  such as `unknown`. `X-Real-IP` is read only without `X-Forwarded-For`, and
+  every `X-Forwarded-For` header line is read, not only the first. The image's
+  nginx, and the `TRUSTED_PROXIES=127.0.0.1/32` it starts the backend with, are
   unchanged.
 - 2026-10-18: after an interval change, the summary's Reachable slot reads
   `--/--` in white, as at page load, until the second round since the change
@@ -485,7 +485,7 @@ Run `make frontend-viewport-test` in CI as its own step; it is not part of
 - 2026-10-03: the Go tests run with the race detector and coverage
   ([#88](https://git.eeqj.de/sneak/netwatch/issues/88)):
   `go test -timeout 30s -race -cover ./...` and, if that fails, the same again
-  with `-v`, and then a failure. Go's `-timeout` bounds the tests, not their
+  with `-v`, then a failing exit. Go's `-timeout` bounds the tests, not their
   compile. The race detector needs a C compiler; the binary is still built with
   `CGO_ENABLED=0`. New tests cover the health check's answer, a valid report's
   answer, a report file's exact contents, and the flush when the buffer reaches