Fix function comments based on best practices from Effective Go

[CodeLingoBot]

Every exported function in a program should have a doc comment. The first sentence should be a summary that starts with the name being declared. From effective go.

PR generated by CodeLingo. Install here to drive Continuous Higher Standards.

[BlakeMScurr]

Hi there!

@BlakeMScurr from CodeLingo here. This PR is testing out a new service. I'd love to hear your feedback or answer your questions. We're keen to learn how we can best help dev teams without getting in your way.

@BlakeMScurr & the CodeLingo Team

[BlakeMScurr]

@kabukky how valuable do you find these changes? You should pass golint now - is that worth much to you? Would it be a significant improvement if we rewrote the first comment to Ghost converts a Ghost database to use with Journey rather than Ghost: Function to convert a Ghost database to use with Journey?