docs: normalize British English to American English in spec files (#31291)

Author: github-actions[bot]

docs/src/content/docs/reference/effective-tokens-specification.md

@@ -490,7 +490,7 @@ This file is embedded at compile time into the `gh-aw` binary using a Go `//go:e
 
 **R-REG-004**: Implementations MUST embed or bundle the registry at build time. Runtime fetching of multiplier values from an external source requires disclosure in reported output.
 
-**R-REG-005**: When a model name is not present in the registry, implementations MUST treat the multiplier as `1.0` and SHOULD emit a warning noting that the model is unrecognised.
+**R-REG-005**: When a model name is not present in the registry, implementations MUST treat the multiplier as `1.0` and SHOULD emit a warning noting that the model is unrecognized.
 
 **R-REG-006**: Custom multipliers supplied by the caller (e.g., via API or configuration) MUST be merged with registry multipliers. Custom values take precedence and MUST be disclosed in any report that uses them.
 

docs/src/content/docs/reference/experiments-specification.md

@@ -997,7 +997,7 @@ experiments:
 ```
 
 The weight values are **relative proportions**, not absolute percentages. The implementation
-normalises them to compute probabilities:
+normalizes them to compute probabilities:
 
 ```
 total_weight = 20 + 50 + 30 = 100

docs/src/content/docs/reference/fuzzy-schedule-specification.md

@@ -344,13 +344,13 @@ every 2 days
 ### 3.7 Error Norms for Invalid Schedule Expressions
 
 The following table specifies normative behavior (MUST/SHALL requirements) for malformed or
-unrecognisable fuzzy schedule expressions encountered during compilation. These norms apply
+unrecognizable fuzzy schedule expressions encountered during compilation. These norms apply
 at parse time (when the compiler processes the workflow frontmatter) and at test time (when
 the compliance test suite exercises the parser with invalid inputs).
 
 | # | Error Condition | Input Example | MUST/SHALL Behavior | Error Code |
 |---|----------------|---------------|---------------------|------------|
-| E-01 | Unknown schedule keyword (not one of `daily`, `weekly`, `hourly`, `bi-weekly`, `tri-weekly`, `every`) | `monthly` | Implementation MUST reject with a descriptive error naming the unrecognised keyword and listing valid keywords | `UNKNOWN_KEYWORD` |
+| E-01 | Unknown schedule keyword (not one of `daily`, `weekly`, `hourly`, `bi-weekly`, `tri-weekly`, `every`) | `monthly` | Implementation MUST reject with a descriptive error naming the unrecognized keyword and listing valid keywords | `UNKNOWN_KEYWORD` |
 | E-02 | Out-of-range hour in 24-hour format | `daily around 25:00` | Implementation MUST reject; the error message MUST state the valid hour range (0–23) and the offending value | `HOUR_OUT_OF_RANGE` |
 | E-03 | Out-of-range minute | `daily around 14:65` | Implementation MUST reject; the error message MUST state the valid minute range (0–59) and the offending value | `MINUTE_OUT_OF_RANGE` |
 | E-04 | `around` keyword with no time specification | `daily around` | Implementation MUST reject; the error message MUST include an example of correct `around` usage | `MISSING_TIME_SPEC` |