fix: Small fix gofmt and misspell from go report

[Bablzz]

Hi there!

I've looked at goreportcard and in my mind it's not to be bad fix a few warn from that website.

If you think that it is not good I am going to close this MR.

Have a great day!

[gianarb]

Hello @Bablzz thank you for your contribution. The typo is appreciated, the other one does not really add value to me. But it is good to embrace standards because it helps maintainability. But as I said for #251 those standards have to be checked continuously in CI. I never used goreportcard but in another project, I use golangci-lint. I am not a fan of those or better, I don't have any preference.

@mdelapenya do you have a preference in terms of the static analyzer for Go?

[mdelapenya]

I've used golangci-lint, and it works fairly simple. E can enforce it in a pre-commit stage/hook (see https://pre-commit.com)

Sorry for the noise with the closer/reopen, using the phone is not always a good choice.

[Bablzz]

Maybe use golanglint-ci in travis ci, but now this tool shows a few issue which some useful some not.

[gianarb]

Yeah, personally I don't want to merge this PR because it does not add any value. I am happy to merge one that fixes the typos. I am not that excited about introducing a static check. And I don't want to change what I can't continuously assert. It will just be another thing to look during code review.

Thanks

[Bablzz]

if you don't mind, I will fix the typos in another MR