Fix typo for @bors cheetsheet

[alexispurslane]

r? @steveklabnik

[rust-highfive]

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @pcwalton (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way Github handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

[alexispurslane]

r? @steveklabnik

[TimNN]

There's still a typo in there: it's "cheat sheet" (cheat with an EA) and according to google search result counts, cheat sheet is also more commonly spelled as two words "cheat sheet" instead of one "cheatsheet".

[alexispurslane]

Oh. ok.

[alexispurslane]

Fixed.

[alexispurslane]

This is ready to be merged.

[Gankra]

@bors r+ rollup

[bors]

📌 Commit 4543dad has been approved by Gankro

[bors]

⌛ Testing commit 4543dad with merge 405f8f1...

[bors]

☀️ Test successful - auto-linux-32-nopt-t, auto-linux-32-opt, auto-linux-64-nopt-t, auto-linux-64-opt, auto-linux-64-x-android-t, auto-mac-32-opt, auto-mac-64-nopt-t, auto-mac-64-opt, auto-win-gnu-32-nopt-t, auto-win-gnu-32-opt, auto-win-gnu-64-nopt-t, auto-win-gnu-64-opt, auto-win-msvc-32-opt, auto-win-msvc-64-opt