Use the issue tracker in the repository that owns the tool or documentation you want to improve. Before opening an issue, search for an existing report and check the documentation.
For a bug report, include the version, environment, expected behavior, actual behavior, and a minimal reproduction. Remove credentials and customer data from logs and screenshots. Report sensitive vulnerabilities through SECURITY.md.
For a change, create a branch and open a focused pull request. Follow the repository's own contribution instructions, preserve its license, and run checks appropriate to the change. Product setup and feature documentation should link to the canonical docs instead of duplicating volatile instructions.
For product questions that cannot be discussed publicly, contact [email protected]. This guidance does not promise a support response time.