docs: spelling corrections

[10xLaCroixDrinker]

Just fixing some spelling errors through docs, comments & tests

Checklist

• run npm run test and npm run benchmark
• tests and/or benchmarks are included
• documentation is changed or added
• commit message and code follows the Developer's Certification of Origin
  and the Code of conduct

[Fdawgs]

Will review properly next week.
FYI, Fastify uses American/Simple English over British/Traditional English, so "Behavior" is correct.

[jsumners]

Other than my comments (and subsequent lines that are the same but I left uncommented), this looks good. Please resolve the issues highlighted.

[jsumners]

Looks good to me.

[10xLaCroixDrinker]

FYI, Fastify uses American/Simple English over British/Traditional English

Should https://fastify.dev/organisations/ be https://fastify.dev/organizations/ then? Is that a PR you'd be open to (with a redirect of course)?

[jsumners]

I'll leave that up to the @fastify/website team. But I don't think we need to be so pedantic as to break the website.

(FYI: I'm American, having never left the country in my 4+ decades [record to be broke in April 🎉], and I routinely write British variants of words before spellcheck kicks in. I'm not a stickler for the variants. We just have a style guide and should adhere to it as much as makes sense for consistency.)

[mcollina]

lgtm

[gurgunday]

FYI, Fastify uses American/Simple English over British/Traditional English

Should https://fastify.dev/organisations/ be https://fastify.dev/organizations/ then? Is that a PR you'd be open to (with a redirect of course)?

I think for consistency sake it should be "organizations", is it hard to add a redirect to "organisations"? Not familiar with what framework the website uses

[10xLaCroixDrinker]

@gurgunday the site is built with docusaurus and already uses a plugin for a few other redirects, so it would just take a couple additional lines to that plugin config

[mcollina]

let's do it

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.