fix(capy/README): the 2026-10-15 waves were not gstack's first fix waves

docs/designs/ already holds fix-wave plans from October 3, 6 and 12;
on October 15 Garry approved two more (fix-wave-2026-10-15 and
fix-wave-2-2026-10-15).

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>

capy/README.md

@@ -14,7 +14,7 @@ reference is [docs/captain.md](../docs/captain.md).
 
 ## The numbers
 
-The 14 days from the first fix waves (2026-10-15, with the Captain taking over
+The 14 days from the 2026-10-15 fix waves (the Captain took over
 the next day) against the 14 days before, measured from git and GitHub[^1]:
 
 - **197 PRs merged to gstack's main, up from 65 (3.0x).** That is 98.5 a week.
@@ -37,7 +37,7 @@ went up, from a median of 1.1 hours to 5.6, because trains batch merges.
 ## What we did
 
 Capy threads started writing gstack PRs on 2026-09-15. On 2026-10-15 Garry
-approved the first fix waves, and the next day he handed gstack's development
+approved two fix waves, and the next day he handed gstack's development
 to a Capy Captain, GStack Minder. Its standing job is to keep
 `garrytan/gstack` moving and main green. Within two weeks there were seven Captains (gstack, gbrain,
 alphaclaw, two eval projects, a game, and a magazine), each directing its own