I've technical reviewed 3 books and still don't have a way of saying that that doesn't sound awkward. For those 3 books, the production manager sent me Word doc files by email, which I would comment on, rename with my initials at the end, and then send back by email. I've also sent copy edits as pull requests on GitHub, with comments in the commit message, and sometimes a back and forth with the author in the pull request or issue queue.
I'd like to see more books posted to GitHub, so that people can fork and submit corrections to and submit issues. I've contributed to The Little Redis Book (just copy edits here and there) and loved the process. I've seen this with technical books, and would like to see this with less technical topics.
Advantages of this approach:
everybody gets credit for the individual work they do. A small contribution gets a small credit, a bigger contribution a bigger credit, all shown by how big the 'diff' is
since every pull request has a comments thread on GitHub, the author can push back. Maybe some spellings are irregular and/or intended, or the author can convince the editor that the technical information is correct/explained well/etc. Discussion about individual commits or issues.
a fork can be seen as an indication of deep engagement
a passionate community can offer translations into different languages, reformatting so that they can be converted into other reader formats, etc.
Some barriers to this happening:
copyright (a fork is a copy)
fear of publishing something imperfect
relatedly, fear of having silly mistakes exposed