[grogenaut]

Amazon standards is you show up and dedicate at least 30 minutes to reading. You wait till everyone is done reading, and try not to pressure people to hurry.

The reason you do it in the meeting is that for more senior people, you have to block them off time to think about the document. Asking people to schedule another block of time to give feedback on YOUR problem is rude. As you get more senior you end up in way more meetings. It's hard for more junior people or ICs to understand in a lot of cases. If timing is hard, have them schedule you in a different slot.

You can tell in say google docs where everyone is reading wise. You can also see all the comments so you can also judge progress.

Ask questions in negative every 5-10 minutes "Does anyone need more time".

Once everyone is ready, start the meeting by going through comments from top to bottom.

After that it runs like a normal N-Pager meeting, or tech review or whatever.

I will say that with say google docs you can use suggestions and other things or say "I'll work on that". And just move on. It's rarely important to rabbit hole on the english, esp on engineering docs. If you're writing a actual PR or marketing doc, sure.