docs(course): fix review findings in modules 06–11

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

course/10-extensions.md

@@ -139,6 +139,8 @@ Notice what you did *not* have to do: touch the rules of the game, or let `updat
 
 ## Exercises
 
+> **About test names.** The test titles quoted under "Proved by" are the JavaScript ones. The Scala and F# suites test the same things one-to-one, but their titles use each track's vocabulary: "events" instead of "inputs", `None` instead of `null`, `()` instead of `undefined`, `bind`/`choose` instead of `flatMap`/`filterMap`, `IO.map throwingF io` instead of `map(io, throwingF)`, and so on. Failing tests are reported by name when you run the module's tests; to read all titles, open `scala/test/M10Extensions.test.scala` or `fsharp/tests/M10Extensions.fs`. Fixture-based tests have the same case names in every track.
+
 ### Exercise 10.1 — `movesEvery`
 
 **JavaScript** (`js/src/game.js`)
@@ -286,7 +288,7 @@ def update(state: GameState, action: Action): GameState = action match
 let update (state: GameState) (action: Action) : GameState =
     match action with
     | Tick -> Spawn.tick state
-    | Turn d -> Rules.turn d state   (* use the argument order of your Rules.turn *)
+    | Turn d -> Rules.turn state d
     | TogglePause -> (* ? *)
     | Restart -> (* ? *)
     | Frame -> (* ? *)