Corrections Policy

Our commitment

Technical documentation can become inaccurate when software changes or when an error is missed during review. We aim to investigate credible reports and correct confirmed issues in a transparent and proportionate manner.

What can be reported

Useful correction reports may include:

• Commands that fail on the stated operating-system version
• Incorrect package names, service units or file paths
• Obsolete repositories or installation methods
• Unsafe permissions, firewall rules or authentication advice
• Missing prerequisites
• Incorrect version claims
• Broken links
• Misleading diagrams or screenshots
• Contradictory steps
• Typographical errors that change technical meaning

How to submit a correction

Email corrections@linix.online and include:

• The article title and URL
• The affected heading or quoted sentence
• The Linux distribution and version
• The software version
• The command or configuration used
• The actual result or error message
• The expected result
• A link to authoritative documentation, where available

Protect sensitive information

Before sending logs or configuration, remove:

• Passwords and password hashes
• API tokens
• Private keys and certificates containing private material
• Session cookies
• Internal hostnames and IP addresses where sensitive
• Customer or employee information
• Database contents

Review process

When a report is received, we may:

1. Confirm that the report refers to the current published article.
2. Reproduce the issue where practical.
3. Compare the procedure with official documentation or supported behaviour.
4. Determine whether the problem is factual, version-specific, environmental or unclear wording.
5. Correct the article, add a limitation, update the supported version or decline the report with a reason.

Correction priority

Higher priority is generally given to:

• Security vulnerabilities or unsafe instructions
• Commands that may cause data loss
• Broken production procedures
• Incorrect repository or signing instructions
• Errors affecting many readers
• Incorrect claims about supported releases

Types of correction

Minor correction

Spelling, grammar, formatting, link or wording improvements that do not materially change the procedure may be corrected without a separate notice.

Material technical correction

A command, configuration, version, security recommendation or procedural sequence that changes the expected result may lead to an article update and a revised review date.

Major correction or withdrawal

If a tutorial is unsafe, fundamentally inaccurate or no longer maintainable, it may be substantially rewritten, temporarily unpublished, redirected or marked as outdated.

Disagreements

Technical behaviour can vary between distributions, package sources and environments. A report may be accurate for one environment without proving that the article is universally wrong. Where appropriate, we may clarify scope rather than replace the original procedure.

No payment required

Readers are not required to pay to report an error. Donations, advertising relationships or commercial status do not determine whether a correction is accepted.

Acknowledgement

We may acknowledge a contributor when they request it and when doing so is appropriate. We will not publish private contact details without permission.