@@ -15,7 +15,7 @@ common --lockfile_mode=error
 
 # We build nothing for Android, but rules_jvm_external (the //jni Maven jar)
 # depends on rules_android, whose android_sdk_repository extension probes
-# $ANDROID_HOME while analysing *any* target. When ANDROID_HOME is exported but
+# $ANDROID_HOME while analyzing *any* target. When ANDROID_HOME is exported but
 # the SDK has no platform APIs installed — as on GitHub's ubuntu runners after
 # the free-disk-space step removes the SDK — that extension hard-fails and takes
 # down unrelated builds (e.g. //wasm, //web). Pinning the var to empty makes the
 
@@ -125,7 +125,7 @@ auto load_recording(const std::string& path, Recording& out, std::string& error)
   -> bool;
 
 // Resolve a Bazel runfile (e.g. "_main/benchmarks/testdata/x.jsonl") to a real
-// path, or "" if it cannot be found. Windows does not materialise the runfiles
+// path, or "" if it cannot be found. Windows does not materialize the runfiles
 // tree -- that would need symlinks -- so the manifest has to be consulted there.
 // `bazel test` exports the manifest location in the environment; `bazel run`
 // does not, so pass argv[0] and the manifest beside the binary will be used.
 
@@ -277,7 +277,7 @@ Batched form of `analyse_play_pbn` (wraps `AnalyseAllPlaysPBN`).
 Legacy thread-resource hook (wraps the **deprecated** `SetMaxThreads` C API).
 
 This does **not** control DDS's batch parallelism and is kept only for backward
-compatibility. `solve_all_boards_*` already parallelise across the machine's
+compatibility. `solve_all_boards_*` already parallelize across the machine's
 hardware threads automatically (via `solve_boards_n`) — the value passed here does
 not size that pool. `analyse_all_plays_pbn` currently runs sequentially.
 `user_threads` must be `>= 0` (`0` = auto); raises `ValueError` for negative values.
 
@@ -623,7 +623,7 @@ auto register_analysis_bindings(py::module_& module) -> void
 {
     // initialize_static_memory: allocate the solver's static memory pools and
     // perform one-time lookup-table initialization. This does NOT control the
-    // worker-thread count; use solve_all_boards_* (which parallelise across the
+    // worker-thread count; use solve_all_boards_* (which parallelize across the
     // machine's hardware threads automatically) or one SolverContext per worker
     // thread for per-board concurrency.
     module.def(
@@ -635,7 +635,7 @@ auto register_analysis_bindings(py::module_& module) -> void
         "Initialize the solver's static memory.\n\n"
         "Allocates the transposition-table memory pools and performs one-time\n"
         "lookup-table initialization. This does NOT control the number of worker\n"
-        "threads: solve_all_boards_* parallelise across the machine's hardware\n"
+        "threads: solve_all_boards_* parallelize across the machine's hardware\n"
         "threads automatically, and for per-board concurrency from Python you\n"
         "create one SolverContext per worker thread and pass it to solve_board /\n"
         "solve_board_pbn.");