Forbid the British spellings fixed in recent PRs (mdn#45358)

* Forbid the British spellings fixed in recent PRs

Adds the 29 British spellings corrected in mdn#44920, mdn#45333, mdn#45334,
mdn#45340, mdn#45341, mdn#45346 and mdn#45355 to the forbidden-spelling dictionary,
so `npm run lint:typos` fails on them instead of letting them back in.
Both spellings are valid dictionary words, so nothing could catch a
regression until now.

Enforcing the list surfaced 32 occurrences that earlier passes missed:
seven of "labelled" in prose in the WCAG and ARIA guides, and
twenty-five in code comments and log strings that earlier passes had
left alone as code. The comments and strings are prose and read the
same either way, so they are corrected rather than exempted.

Ten files keep a British spelling and carry a per-file `cSpell:ignore`
comment, because changing the text would change its meaning:

- Code identifiers: `const cancelled` on the DOM events page and
  `const maths` in the MathML tutorial.
- The verbatim Firefox error strings on "functions cannot be labelled".
- The `menu-labelled-open` example extension name, and the `colour`
  keys in the WebExtensions storage and i18n examples, which mirror the
  `favourite-colour` example repository and the en_GB message that
  example returns.
- The note on the listbox role page stating that "labelled", with two
  L's, is the correct spelling per accessibility API conventions.
- The "Million tonne punch" sample data, which is shared with the
  learning-area repository.
- The screen reader transcript on the <math> element page.

`grey` is deliberately left out. It is a valid CSS named color and
appears legitimately 167 times, in `<named-color>`, the
`tabGroups.color` enum, and SVG and CSS samples, so forbidding it would
need an ignore comment on roughly fifty files that use the keyword
correctly.

* Add more

* Add a comment

* Minor fix

---------

Co-authored-by: Joshua Chen <sidachen2003@gmail.com>

Author: husamemadH

.vscode/cspell.json

@@ -146,6 +146,9 @@
       "addWords": false,
       "noSuggest": true
     },
+    // TODO: cSpell seems to match forbidden entries case-sensitively.
+    // For now we just report all-lowercase instances.
+    // https://github.com/streetsidesoftware/cspell/issues/9085
     {
       "name": "forbidden-spelling",
       "path": "./dictionaries/forbidden-spelling.txt",

.vscode/dictionaries/code-entities.txt

@@ -169,6 +169,7 @@ ctrz
 Cubehelix
 currententrychange
 currentscreenchange
+customelementregistry
 cwrap
 daala
 dangi

.vscode/dictionaries/forbidden-spelling.txt

@@ -1 +1,44 @@
+!amongst
 !anticlockwise
+!bevelled
+!bevelling
+!burnt
+!cancelled
+!cancelling
+!centre
+!centred
+!centres
+!centring
+!colour
+!coloured
+!fibre
+!fulfil
+!fulfils
+!greyed
+!greying
+!greyish
+!honour
+!honoured
+!honouring
+!honours
+!judgement
+!labelled
+!labelling
+!learnt
+!levelled
+!leveller
+!levelling
+!localising
+!maths
+!misspelt
+!modelled
+!modelling
+!programme
+!programmes
+!signalled
+!signalling
+!spelt
+!tonne
+!totalled
+!totalling
+!whilst

.vscode/dictionaries/terms-abbreviations.txt

@@ -61,7 +61,8 @@ barcodes
 barebones
 bfcache
 BGRA
-Bignums
+bignum
+bignums
 bikeshedding
 bilevel
 bioinformatics
@@ -594,6 +595,7 @@ redisplaying
 refbox
 regionless
 reimplementation
+relatedly
 remarketing
 remotable
 renderable

files/en-us/learn_web_development/core/accessibility/wai-aria_basics/index.md

@@ -838,7 +838,7 @@ Always include a {{HTMLelement('label')}} for every input. While some screen rea
 > [!NOTE]
 > You can see the finished example live at [`form-validation-updated.html`](https://mdn.github.io/learning-area/accessibility/aria/form-validation-updated.html).
 
-WAI-ARIA also enables some advanced form labelling techniques, beyond the classic {{htmlelement("label")}} element. We already talked about using the [`aria-label`](/en-US/docs/Web/Accessibility/ARIA/Reference/Attributes/aria-label) property to provide a label where we don't want the label to be visible to sighted users (see the [Signposts/Landmarks](#signpostslandmarks) section, above). Some other labeling techniques use other properties such as [`aria-labelledby`](/en-US/docs/Web/Accessibility/ARIA/Reference/Attributes/aria-labelledby) if you want to designate a non-`<label>` element as a label or label multiple form inputs with the same label, and [`aria-describedby`](/en-US/docs/Web/Accessibility/ARIA/Reference/Attributes/aria-describedby), if you want to associate other information with a form input and have it read out as well. See [WebAIM's Advanced Form Labeling article](https://webaim.org/techniques/forms/advanced) for more details.
+WAI-ARIA also enables some advanced form labeling techniques, beyond the classic {{htmlelement("label")}} element. We already talked about using the [`aria-label`](/en-US/docs/Web/Accessibility/ARIA/Reference/Attributes/aria-label) property to provide a label where we don't want the label to be visible to sighted users (see the [Signposts/Landmarks](#signpostslandmarks) section, above). Some other labeling techniques use other properties such as [`aria-labelledby`](/en-US/docs/Web/Accessibility/ARIA/Reference/Attributes/aria-labelledby) if you want to designate a non-`<label>` element as a label or label multiple form inputs with the same label, and [`aria-describedby`](/en-US/docs/Web/Accessibility/ARIA/Reference/Attributes/aria-describedby), if you want to associate other information with a form input and have it read out as well. See [WebAIM's Advanced Form Labeling article](https://webaim.org/techniques/forms/advanced) for more details.
 
 There are many other useful properties and states too, for indicating the status of form elements. For example, `aria-disabled="true"` can be used to indicate that a form field is disabled. Many browsers will skip past disabled form fields which leads to them not being read out by screen readers. In some cases, a disabled element will be perceived, so it is a good idea to include this attribute to let the screen reader know that a disabled form control is in fact disabled.
 

files/en-us/learn_web_development/core/scripting/json/index.md

@@ -49,6 +49,8 @@ As described above, JSON is a string whose format very much resembles JavaScript
 The following is a valid JSON string representing an object.
 Note that it is also a valid JavaScript object literal — just with some more [syntax restrictions](#json_syntax_restrictions).
 
+<!-- cSpell:ignore tonne -->
+
 ```json
 {
   "squadName": "Super hero squad",

files/en-us/mozilla/add-ons/webextensions/api/menus/onshown/index.md

@@ -12,6 +12,8 @@ An extension can use this event to update its menu items using information that'
 
 The handler can add, remove, or update menu items.
 
+<!-- cSpell:ignore labelled -->
+
 For example, the [menu-labelled-open](https://github.com/mdn/webextensions-examples/tree/main/menu-labelled-open) example extension adds a menu item that's shown when the user clicks a link, and that, when clicked, just opens the link. It uses `onShown` and `refresh()` to annotate the menu item with the hostname for the link, so the user can easily see where they will go before they click.
 
 Note that an extension should not take too much time before calling `refresh()`, or the update will be noticeable to the user.

files/en-us/mozilla/add-ons/webextensions/api/omnibox/oninputcancelled/index.md

@@ -33,7 +33,7 @@ The listener function is passed no parameters.
 
 ```js
 browser.omnibox.onInputCancelled.addListener(() => {
-  console.log("The user cancelled the session.");
+  console.log("The user canceled the session.");
 });
 ```
 

files/en-us/mozilla/add-ons/webextensions/api/storage/managed/index.md

@@ -16,6 +16,8 @@ For Firefox, you need to create a [JSON manifest (native manifest) file in a spe
 
 Here's an example native manifest:
 
+<!-- cSpell:ignore colour -->
+
 ```json
 {
   "name": "favourite-colour-examples@mozilla.org",

files/en-us/mozilla/add-ons/webextensions/internationalization/index.md

@@ -5,6 +5,8 @@ page-type: guide
 sidebar: addonsidebar
 ---
 
+<!-- cSpell:ignore colour -->
+
 The [WebExtensions](/en-US/docs/Mozilla/Add-ons/WebExtensions) API has a rather handy module available for internationalizing extensions — [i18n](/en-US/docs/Mozilla/Add-ons/WebExtensions/API/i18n). In this article we'll explore its features and provide a practical example of how it works.
 
 > [!NOTE]