refactor(core) rephrase error messages

[j-maas]

Fixes typo, clarifies what actions are expected.

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[x] Other: Error messages refactor

What is the current behavior?

There was a typo in an error message ("proccessed" instead of "processed").

Some messages did not clearly state what do check for ("verify whether" instead of "make sure that").

Parentheses were inlined in the sentence (like this). (Instead of this.)

What is the new behavior?

Typo is fixed and I tried to make some other messages more "actionable" by not only indicating what part to check, but also what to check for ("verify whether available" -> "make sure it is available"). (I hope I didn't actually make them worse. 😁 I am open to criticism.)

I extracted parentheses from the sentence, since they are self-contained.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

[coveralls]

Coverage remained the same at 94.973% when pulling 3e55de5 on Y0hy0h:patch-1 into ced6729 on nestjs:master.

[kamilmysliwiec]

Thanks @y0hy0h, I prefer your error messages either 🙂

[lock]

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