Name the things users ask about
Keep exact error strings, configuration keys and API names near their explanations. Consistent naming makes relevant evidence easier to retrieve.
Make boundaries explicit
State the product version, prerequisites and limitations. An answer about the wrong environment can be more harmful than no answer.
Link the next step
Help readers move from a conceptual explanation to a procedure, example or troubleshooting path. These links also help an assistant provide useful follow-up guidance.