docs: fix various typos in source and documentation (#5834)

Co-authored-by: Josh Goldberg ✨ <git@joshuakgoldberg.com>

Author: Abhi3975

docs/src/content/docs/running/configuring.mdx

@@ -67,7 +67,7 @@ In case of conflict, the priority is:
 Options which can safely be repeated (e.g., `--require`) will be _concatenated_, with higher-priority configuration sources appearing earlier in the list.
 For example, a `.mocharc.json` containing `"require": "bar"`, coupled with execution of `mocha --require foo`, would cause Mocha to require `foo`, then `bar`, in that order.
 
-This also includes `spec`. For example, a `.mocharc.json` containing `"spec": ["**/*.test.js"]` coupled with execution of `mocha bar.spec.js` would be the same as runninng `mocha bar.spec.js **/*.test.js`, and it would still run all `.test.js` files. To workaround this, you can comment out the `spec` property or use a different config file via `--config`.
+This also includes `spec`. For example, a `.mocharc.json` containing `"spec": ["**/*.test.js"]` coupled with execution of `mocha bar.spec.js` would be the same as running `mocha bar.spec.js **/*.test.js`, and it would still run all `.test.js` files. To workaround this, you can comment out the `spec` property or use a different config file via `--config`.
 
 ## Extending Configuration
 

test/node-unit/mocha.spec.js

@@ -223,7 +223,7 @@ describe("Mocha", function () {
     });
 
     describe("loadFilesAsync()", function () {
-      it("shoud pass esmDecorator to actual load function", async function () {
+      it("should pass esmDecorator to actual load function", async function () {
         const esmDecorator = (x) => `${x}?foo=bar`;
 
         await mocha.loadFilesAsync({ esmDecorator });