code clean up as per coding standard

There are so many pending issues with needs review patches. This is not the right time to do coding standard fixes.
All other patches would be broken.

Thanks for your help trying to triage issues. If you have the time, helping us review some of the waiting patches would be great. Given the popularity of the module, we almost always have 10 or more issues waiting for review. As our entire team are git experts, rerolls needed because of coding standards improvements won't be a problem.

@Greg Boggs we usually commit code clean-ups right after or short before tagging a release. Core did so in a code freeze phase. No matter how experienced you are, committing an issue like this breaks patches and you not only need to reroll issues, but also wait for the bot to pass to commit things, right. These situations slow me down with reviews and are IMHO a waste of time. But hey, thx for your great maintenance work and glad you want to handle this pain. I like clean code too! :-)

I hear you for sure. I've been putting this one off until the next release is done which I'm doing this week. After that, I plan to get the code cleanup done like a band aid.

The queue isn't completely clean but now is as good a time as any to get this in. Thanks for the patience all.