The Scrum Team members have courage to do the right thing and work on challenging problems.
The Scrum Team agree to be open (to speak and listen) about all the work and the challenges with performing the work. Scrum Team members respect each other's skills, experience, and opinions.

Development Teams are structured and empowered by the organization to organize and manage their own work. This includes deciding how to form teams when multiple teams are needed. The resulting synergy optimizes the Development Team's overall efficiency and effectiveness. They are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality.

User documentation is part of your Definition of Done, which means that it is a requirement for delivering a potentially releasable product increment. Your Scrum Team cannot ignore or postpone this requirement, even if there are not enough technical writers for all teams. Your Scrum Team is responsible for creating and maintaining the user documentation, and the Developers are the ones who have the skills and authority to do so. The Scrum Master can help the Developers learn how to write effective user documentation, and the Product Owner can provide feedback on its quality and value.

The Scrum Team members have courage to do the right thing and work on challenging problems. The Scrum Team agree to be open (to speak and listen) about all the work and the challenges with performing the work.
Scrum Team members respect each other's skills, experience, and opinions.