Fix naming inconsistency

[reevoo-samuel]

_If you're new, read the guidelines._

Good code is tested, designed for change, easy to understand and able to cope when things go wrong.

Good pull requests are descriptive, small and short-lived.

For the Author

• [ ] Description explains what you have done and why.
• [ ] Tests have been written (or you have explained why you don't need tests).
• [ ] Documentation/comments have been added/updated.

For the Reviewer

• [ ] The code is well-designed and able to cope with change.
• [ ] The code is easy to understand.
• [ ] Tests cover happy and unhappy paths in the code.
• [ ] Tests are green on CI (or pulled/tested on your machine).

[errm]

Also the github repo should be renamed, and the gem should be pushed to rubygems to sqaut the name.

[reevoo-samuel]

Er, hello?

This Pull Request is too damn old! Merge or close this, sucka.

[reevoo-samuel]

I don't see any comments on your Pull Request.

Are you too good for code reviews now? No. No you aren't.

Maybe you forgot to say who reviewed it. That's fine, but let me know.