I'm ... confused what you mean. If the junior is gonna untangle the docs anyway, why not make them directly update the parts that confused them once they're through it.

I apologize; I misunderstood. I thought you were making a “fend for yourself” argument; I was not associating “junior devs on the team making the docs, need to fix docs or make good ones”.

I think you are misreading the parent comment here.

They're not necessarily prohibited from asking questions if they're stuck, though. But also search in the chat channels for similar issues.

Updating docs in source control also onboards folks to code review. It would be weird to update docs and get a hostile reception.

While nice to walk through with someone and conduct a usability study, just leave it better for the next person (who could be yourself, if you forget). That has happened before.