docs: 📝 explain why we call it "check", not "validate"

[lwjohnst86]

Description

I wanted to explain why we don't use validate, for any readers who are interested.

Closes #181

Needs an in-depth review.

Checklist

• Formatted Markdown
• Ran just run-all

[joelostblom]

lgtm, but someone with more context needs to approve. One minor comment

[signekb]

Nice to include an explanation of this decision 👌

Could this be a lot shorter by cutting out the paragraphs comparing and explaning the difference between "validate" and "verify"? I'm not sure it's relevant now that we use "check". Couldn't the argument simply be that the word "validate" is used a lot of places in a way that doesn't align with what the word actually means, and therefore, we use the word "check" instead?

[signekb]

Nice 👍 I still think this could be shorter (😬), but if you prefer to keep as is that's fine with me too.

I do have some minor suggestions again:

[lwjohnst86]

@signekb if you have suggestions to shorten it, please do give them! 😝

[signekb]

I'll give it a go when you've implemented the suggestions you prefer from my review 👍

[signekb]

Alrighty. This might be controversial. Let me know what you think :)

[joelostblom]

Read well to me!

[lwjohnst86]

@joelostblom just fyi, when you approve, don't include a comment change if you have no suggested changes. Otherwise, if you do, always use "request changes". Since that change (if accepted) causes your approval to be dismissed, so you have to approve again.