Start with the repository that owns the product or documentation you want to change. Follow its setup, contribution rules, and required checks. A repository's own contribution guide takes precedence over this organization default.
For documentation changes, use the Hraness documentation guidelines. Choose whether the reader needs guided learning, help with a task, exact reference, or explanation. Keep capabilities, examples, prerequisites, and effects accurate for the documented version. Review the changed reader path and the other surfaces that repeat its facts.
Use the README guidelines for repository front doors and writing style for public prose. Keep source records intact and exclude credentials, private data, and unsupported claims from public examples.