I love your point on there being no single right or wrong way to do product management.

This is slightly off topic, but am noticing a lot of comments here telling you how to make your PRD better. I think it's great to always challenge and improve yourself.

However, my only advice if it's of any worth is to manage your expectations with people critiquing your PRDs.

Some people conflate PRDs with product specifications or feature specifications. Know that the end user reading each doc is different.

Some people just won't get what you are communicating from reading strings of sentences alone, you must walk them through it verbally.

In contrast, some people have a deeper understanding of the technologies you work with, the problem space, and can literally understand a couple of lines from what you are trying to convey.

Some people will ask you to draw diagrams, illustrate, write in tables etc. This makes it easier for them to read, but you will always find others who simply still don't get it, and if anything after adding all this information find your PRDs too long.

I have written a lot of PRDs in my short career, and have come to realise that most people won't understand it at first glance unless they requested for the feature. They will always ask you for more detail, better formatting, blah. Figure out the PRD expectations of the organisation you work/want to work for, figure out ways to teach people who don't understand your domain of expertise (not always successful by adding to a spec), figure out the people who stretch your thinking/content (good) vs critique your presentation style (ignore unless valid).

Be smart. Your time is most precious.