[docs] docs: fix British spellings in frontmatter-full.md - #53574
[docs] docs: fix British spellings in frontmatter-full.md#53574github-actions[bot] wants to merge 4 commits into
Conversation
Corrects behaviour/customise/parameterise to their American English equivalents (behavior/customize/parameterize) flagged by the daily docs spellcheck.
|
@copilot Please review this PR, refresh the branch if needed, then run the
|
Co-authored-by: gh-aw-bot <259018956+gh-aw-bot@users.noreply.github.com>
Co-authored-by: gh-aw-bot <259018956+gh-aw-bot@users.noreply.github.com>
Co-authored-by: gh-aw-bot <259018956+gh-aw-bot@users.noreply.github.com>
Completed in |
Summary
The daily spellcheck flagged 1,885 potential findings across 208 docs files. Nearly all of them are false positives from cspell's dictionary — product/tool names (
toolsets,agentics,GHES,zizmor,poutine, etc.), usernames (pelikhan,dsyme,mnkiefer), code identifiers, and intentional typo examples used to illustrate the CLI's fuzzy-matching / "did you mean" features (e.g.audti-workflows,permisions,mondey).After manually triaging the findings, the only genuine spelling issues were British-English spellings inconsistent with the project's American English convention, all confined to
docs/src/content/docs/reference/frontmatter-full.md:behaviour→behavior(2 occurrences)customise→customize(2 occurrences)parameterise→parameterize(4 occurrences)View Details
Note:
frontmatter-full.mdis auto-generated from the JSON Schema comments (pkg/parser/schemas/main_workflow_schema.json). This PR only updates the generated doc per the spellcheck workflow's scope (docs/src/content/); the schema source itself is outside that scope and wasn't touched, so a future regeneration could reintroduce these spellings unless the schema comments are also corrected separately.Test plan
git diffreviewed — only the 8 targeted word substitutions changed, no other content touched