Fix function comments based on best practices from Effective Go

[Daanikus]

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.

I generated this with CodeLingo and I'm keen to get some feedback, but this is automated so feel free to close it and just say "opt out" to opt out of future CodeLingo outreach PRs.

[Daanikus]

I'm not sold on the use of colons here. Happy to hear feedback on this strategy and how I could fix the automation logic. Thanks.