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 a huge fan of the colon-ifying (so to speak) and I welcome any feedback as to how I could improve the logic for this. Thanks.

[vdemeester]

@Daanikus thanks for the contribution 🤗

1. As from effective go "The first sentence should be a summary that starts with the name being declared.", this means it should be a sentence — thus something like HashString generates a hash string used to detect service volume config changes for example (no need for :)
2. As written in the README, This is not really maintained anymore — the reason are diverse but mainly lack of time from the maintainers. I should archive it to mark is as such and put it in read-only mode.