Or let the Junior rewrite the docs while they're scratching their head, and push an update once they've figured it out.
Fixing and updating the README when I join a new team and set up their dev environment is always extremely well-received.
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.