Fix typo in README.md

[r-walsh]

What:

toBeThruthy -> toBeTruthy

Why:

How:

I started by backspacing the extra h. Then I opened this PR.

Checklist:

• Documentation
• Tests N/A
• Updated Type Definitions N/A
• Ready to be merged
• Added myself to contributors table N/A

[smacpherson64]

Hahaha! Great gif! 😂

[smacpherson64]

Thank you @r-walsh!

[gnapse]

🎉 This PR is included in version 2.0.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[gnapse]

@smacpherson64 not a big deal, but when something's just updating documentation, then is best to prefix the commit with docs: ... instead of fix: .... Otherwise this generates a new release that doesn't really brings something new or any fix (functionality-wise).

Again, not at all a big deal, just FYI for the future. This extra release does not hurt anyway 😄.

[gnapse]

Oh and thanks @r-walsh! That's certainly not a word, haha!

[gnapse]

I wonder if it would be possible to run tests on a README's code examples? 🤔 :mind_blown: 😆

[smacpherson64]

Sorry @gnapse! Will do!

[smacpherson64]

Hrm, that would be incredible!

[kentcdodds]

I wonder if it would be possible to run tests on a README's code examples? 🤔 :mind_blown: 😆

I'm pretty sure there are modules for this... Someone tried to convince me to use it but it seemed like too much work...

[gnapse]

Of course there are modules for that (or anything). This is javascript after all 😆.

But no, really, I'm (a bit) surprised anyway.

And yeah, agree it may be too much.