Substantive edit

[cwcromwell]

When we next have a group of writers to work on the Lone Writers Guide, the first task should be to discuss the scope of it.
Some of the advice we've written is useful to all technical writers, in a general way, but isn't necessarily needed by Lone Writers. Based on the conversations in the Lone Writers channel on Slack, writers need help with tasks like:

• helping managers understand the size of technical debt
• demonstrating the need to hire an additional writer
• deciding where to start so that they can make an impact, but also knowing how much is realistic

They might be less likely to have time for:

• Writing an entire style guide
• Adopting a new documentation tool
• Testing documentation

Maybe instead these could be part of a general guide about technical writing, and the LWG could focus more on issues that are unique to lone writers.