Docs: Fix more spelling mistakes caught by aspell

Ref https://github.com/Krinkle/dotfiles/blob/v2024.07/Extended-Mind.md#aspell

Author: Krinkle

History.md

@@ -735,7 +735,7 @@ FYI:
 
 * Core: Prevent multiple "begin" events from calling `QUnit.load()`.
 * Core: Use callback-based pause/resume for better multi-pause isolation.
-* HTML Reporter: Fix apply/reset button visibilty.
+* HTML Reporter: Fix apply/reset button visibility.
 * Core: Ensure runtime for skipped tests is 0.
 * Dump: New parser for `Symbol` type.
 
@@ -1041,7 +1041,7 @@ FYI:
 ==================
 
 * Core: A test without any assertions now fails by default, unless [`assert.expect(0)`](https://qunitjs.com/api/assert/expect/) is called. [#178](https://github.com/qunitjs/qunit/issues/178)
-* Core: Add `QUnit.pushFailure` to log error conditions like exceptions. Accepts stacktrace as second argument, allowing extraction with catched exceptions (useful even in Safari). [#210](https://github.com/qunitjs/qunit/issues/210)
+* Core: Add `QUnit.pushFailure` to log error conditions like exceptions. Accepts stacktrace as second argument, allowing extraction with caught exceptions (useful even in Safari). [#210](https://github.com/qunitjs/qunit/issues/210)
 * Core: Apply [`notrycatch` option](https://qunitjs.com/api/config/notrycatch/) to setup and teardown hooks. [#203](https://github.com/qunitjs/qunit/issues/203) [#204](https://github.com/qunitjs/qunit/issues/204)
 * Core: Extend exports object with QUnit properties at the end of the file to export everything.
 * Core: Prefix test-related session-storage items to make removal more specific. [#213](https://github.com/qunitjs/qunit/issues/213)

docs/_posts/2012-03-10-qunit-1-4-0.md

@@ -9,7 +9,7 @@ tags:
 ## Changelog
 
 * Core: A test without any assertions now fails by default, unless [`assert.expect(0)`](https://qunitjs.com/api/assert/expect/) is called. [#178](https://github.com/qunitjs/qunit/issues/178)
-* Core: Add `QUnit.pushFailure` to log error conditions like exceptions. Accepts stacktrace as second argument, allowing extraction with catched exceptions (useful even in Safari). [#210](https://github.com/qunitjs/qunit/issues/210)
+* Core: Add `QUnit.pushFailure` to log error conditions like exceptions. Accepts stacktrace as second argument, allowing extraction with caught exceptions (useful even in Safari). [#210](https://github.com/qunitjs/qunit/issues/210)
 * Core: Apply [`notrycatch` option](https://qunitjs.com/api/config/notrycatch/) to setup and teardown hooks. [#203](https://github.com/qunitjs/qunit/issues/203) [#204](https://github.com/qunitjs/qunit/issues/204)
 * Core: Extend exports object with QUnit properties at the end of the file to export everything.
 * Core: Prefix test-related session-storage items to make removal more specific. [#213](https://github.com/qunitjs/qunit/issues/213)

docs/_posts/2016-04-21-introduce-multi-select-module-picker.md

@@ -15,7 +15,7 @@ This replaces the module select dropdown with a dropdown that opens up into a mu
 * Multi-select window with checkboxes and scrolling.
 * Search box for filtering by module or test name.
 * "Apply" button to run selected tests or modules.
-* "Reset" button to clear selection, returnig to implied default of "Select all".
+* "Reset" button to clear selection, returning to implied default of "Select all".
 
 ## Accessibility
 

docs/_posts/2016-07-23-qunit-2-0-1.md

@@ -10,7 +10,7 @@ tags:
 
 * Core: Prevent multiple "begin" events from calling `QUnit.load()`.
 * Core: Use callback-based pause/resume for better multi-pause isolation.
-* HTML Reporter: Fix apply/reset button visibilty.
+* HTML Reporter: Fix apply/reset button visibility.
 * Core: Ensure runtime for skipped tests is 0.
 * Dump: New parser for `Symbol` type.
 

docs/_posts/2025-01-19-stacktrace-cleaner.md

@@ -141,7 +141,7 @@ Notice the removal of the first `qunit.js` call, which lets the trace starts cle
 
 ### Trimming traces
 
-For assertion failures and uncaught exceptions alike, we only trim internal frames from the start or end of a stack. Removing frames from the middle would falsely present a call relationship that never happend, and would cause confusion among developers. Instead, frames we can't trim, are greyed out instead. This is similar to Node.js's own error formatter does.
+For assertion failures and uncaught exceptions alike, we only trim internal frames from the start or end of a stack. Removing frames from the middle would falsely present a call relationship that never happened, and would cause confusion among developers. Instead, frames we can't trim, are greyed out instead. This is similar to Node.js's own error formatter does.
 
 ## TAP reporter
 

docs/api/QUnit/module.md

@@ -415,7 +415,7 @@ QUnit.module('MyGroup', (hooks) => {
 });
 ```
 
-Another way that this might happen is if you have named them differently, or perhaps mispelled one, and are referring to the outer parameter from the inner module. Is is recommended to name hooks parameters the same, as this will naturally refer to the correct and closest one always, thus avoiding any mistake.
+Another way that this might happen is if you have named them differently, or perhaps misspelled one, and are referring to the outer parameter from the inner module. Is is recommended to name hooks parameters the same, as this will naturally refer to the correct and closest one always, thus avoiding any mistake.
 
 ```js
 QUnit.module('MyGroup', (hooksOuter) => {

docs/api/QUnit/test.each.md

@@ -194,7 +194,7 @@ QUnit.test.each('square', [
 
 You can give each item in your data set a custom name, by wrapping the data in an object instead of an array. The object key becomes the test case name.
 
-For example, you can self-document each item to more cleary convey what aspect or behavior you want to cover with that test.
+For example, you can self-document each item to more clearly convey what aspect or behavior you want to cover with that test.
 
 ```js
 function square (x) {

docs/api/QUnit/test.if.md

@@ -60,7 +60,7 @@ QUnit.test('render', function (assert) {
 });
 ```
 
-### Legacy idom
+### Legacy idiom
 
 Prior to QUnit 2.22, the following shortcuts were sometimes used. This may be replaced by `QUnit.test.if()`.
 

docs/api/config/fixture.md

@@ -26,7 +26,7 @@ QUnit automatically resets the contents of `<div id="qunit-fixture">`. This give
 
 By starting with an empty fixture in your test HTML file, you effectively give each test a clean start, as QUnit will automatically remove anything that was added or staged there before the next test begins.
 
-If many of your tests require the same markup, you can also set it inside the fixture ahead of time. This reduces duplication between tests. QUnit guruantees that each test will start with a fresh copy of the original fixture, undoing any changes that happened during any previous tests.
+If many of your tests require the same markup, you can also set it inside the fixture ahead of time. This reduces duplication between tests. QUnit guarantees that each test will start with a fresh copy of the original fixture, undoing any changes that happened during any previous tests.
 
 You can define a custom fixture in one of two ways:
 

docs/api/config/index.md

@@ -76,7 +76,7 @@ Preconfig allows integrations to declare configuration without needing to embed,
 
 *Version added: [QUnit 2.21.0](https://github.com/qunitjs/qunit/releases/tag/2.21.0)*.
 
-Flat preconfig allows multiple integrations to seemlessly collaborate, without the risk of projects accidentally unsetting an override (as is the case with Object preconfig).
+Flat preconfig allows multiple integrations to seamlessly collaborate, without the risk of projects accidentally unsetting an override (as is the case with Object preconfig).
 
 In browser environments, global variables that start with `qunit_config_` may override the default value of a configuration option. The following inline script (before loading QUnit), is equivalent to setting `QUnit.config.hidepassed = true; QUnit.config.seed = 'd84af39036'; QUnit.config.testTimeout = 1000;`