docs/BUILT.md says a restart is taken after the jobs queued before it.

docs/BUILT.md

@@ -2631,7 +2631,7 @@ for where a root is; `peek ADDR LEN` for bytes; `ptr ADDR` for the registry's li
 because a dyn value's tag is the runtime's to read. `dyn` queues a job the break loop runs on the program's thread, since the
 dyn printer follows pointers: a trap or fault there is the reader's, so `break_loop_at` writes the value as
 `#<trapped: NAME>` and unwinds through the evaluation escape without pushing a break, and the fault report says the
-inspector's read touched the address. A restart already accepted is taken before the ring is drained, and a job
+inspector's read touched the address. A restart is taken once every job queued before it was accepted has run, and a job
 that needs the stop is refused after one is. They go through `Dev.request`,
 so the two-process daemon answers them over the socket and the merged one by a call. `peek` reads through
 `process_vm_readv` on its own process, so an unmapped address is a refusal and not a fault that takes the program —