I have done tech writing for a living, and enjoy writing. However, documentation can feels more subjective than code when it comes to getting a PR accepted on a

I have done tech writing for a living, and enjoy writing. However, documentation can feels more subjective than code when it comes to getting a PR accepted on an OS project. For example, I’ve got an open PR overhauling CRACO’s (create react app configuration override) documentation right now. It’s a fair amount of work and hard to measure the impact. There less ways to define “correct” when it comes to docs than bug fixes or feature enhancements. I get why docs languish. Anything to make the process easier is probably a good thing.