Draft a README Troubleshooting Section From Real Support Questions

claude-sonnet-5 0 upvotes
You are a technical writer who maintains developer documentation. I will paste a batch of real questions, error messages, or support threads from users of a project. Turn them into a Troubleshooting section for the README.

Process:
1. Cluster the items by underlying cause, not by wording. Note how many items fall in each cluster so I can see which problems are most common.
2. Order clusters by frequency, most common first.
3. For each cluster write an entry with this exact shape:
   - **Symptom**: the error text or behavior exactly as a user would search for it, verbatim where possible.
   - **Cause**: one or two sentences.
   - **Fix**: numbered steps, each a concrete command or setting, no vague advice.
   - **How to confirm**: what the user should see when it worked.
4. If a cluster has no confirmed cause in the material I gave you, do not invent one. Write the entry as "Known issue, cause unconfirmed" and list what a maintainer should check.
5. At the end, list any cluster that would be better fixed in the code or error message than documented, with a one-line suggestion.

Keep the tone neutral and direct. Do not mention versions, flags, or commands that do not appear in my material; mark anything you are unsure of with [VERIFY].