chore: fix typos in docs and comments (#9527)

Author: msmx-mnakagawa

docs/api/advanced/runner.md

@@ -41,7 +41,7 @@ export interface VitestRunner {
    */
   onAfterTryTask?: (test: Test, options: { retry: number; repeats: number }) => unknown
   /**
-   * Called after the retry resolution happend. Unlike `onAfterTryTask`, the test now has a new state.
+   * Called after the retry resolution happened. Unlike `onAfterTryTask`, the test now has a new state.
    * All `after` hooks were also called by this point.
    */
   onAfterRetryTask?: (test: Test, options: { retry: number; repeats: number }) => unknown

docs/guide/parallelism.md

@@ -12,7 +12,7 @@ By default, Vitest runs _test files_ in parallel. Depending on the specified `po
 - `forks` (the default) and `vmForks` run tests in different [child processes](https://nodejs.org/api/child_process.html)
 - `threads` and `vmThreads` run tests in different [worker threads](https://nodejs.org/api/worker_threads.html)
 
-Both "child processes" and "worker threads" are refered to as "workers". You can configure the number of running workers with [`maxWorkers`](/config/#maxworkers) option.
+Both "child processes" and "worker threads" are referred to as "workers". You can configure the number of running workers with [`maxWorkers`](/config/#maxworkers) option.
 
 If you have a lot of tests, it is usually faster to run them in parallel, but it also depends on the project, the environment and [isolation](/config/#isolate) state. To disable file parallelisation, you can set [`fileParallelism`](/config/#fileparallelism) to `false`. To learn more about possible performance improvements, read the [Performance Guide](/guide/improving-performance).
 

packages/runner/src/types/runner.ts

@@ -139,7 +139,7 @@ export interface VitestRunner {
     options: { retry: number; repeats: number },
   ) => unknown
   /**
-   * Called after the retry resolution happend. Unlike `onAfterTryTask`, the test now has a new state.
+   * Called after the retry resolution happened. Unlike `onAfterTryTask`, the test now has a new state.
    * All `after` hooks were also called by this point.
    */
   onAfterRetryTask?: (

packages/vitest/src/node/module-diagnostic.ts

@@ -13,7 +13,7 @@ import type { StateManager } from './state'
 import { originalPositionFor, TraceMap } from '@jridgewell/trace-mapping'
 import { createIndexLocationsMap } from '../utils/base'
 
-// this function recieves the module diagnostic with the location of imports
+// this function receives the module diagnostic with the location of imports
 // and populates it with collected import durations; the duration is injected
 // only if the current module is the one that imported the module
 // if testModule is not defined, then Vitest aggregates durations of ALL collected test modules