On the other hand, I very much appreciate knowing which celebrities support an administration that poses a threat to my family. I will not vote for someone based on a celebrity endorsement, but the celebrity may gain or lose my business over it.
I really liked Kid Rock in his early days. The music was catchy, and it had the right mix of redneck, rock, and rap to make this country boy happy. Now I won't listen to him because he chose to openly throw in with politicians who do not care if their policies and rhetoric kill my friends or kids.
Good documentation should, in part, tell people where to click. I have designed software documentation for high performing individuals at leading global companies, and I have designed software and hardware documentation for minimum wage fast food workers with limited English proficiency. In both extremes, I showed them exactly where to click on the screen at each step.
You might not need that level of help, but many people do. Others do not strictly need it, but they prefer the simple instruction set. "Click here then here," instructions ease the transition into a new system one needs to learn, or it removes the need entirely to learn a system one uses infrequently.
The problem is that making good documentation is difficult and time consuming. It relies on a fundamentally different skill set than coding or even UI design.
I agree that the ideal is for software to not need any documentation. In my experience, I have yet to see software that rises to that task and is used across a variety of experience levels and societal cross sections.