Software guides go stale, and sometimes they are simply wrong. This page describes what happens in both cases.
How corrections are made
- Corrections happen in the article itself. When an error or an outdated fact is found, the affected text is corrected in place and the page's modified date is updated. Substantive changes get a visible, dated update note — an amber "Update" box near the top of the article — rather than a silent edit.
- Related pages are swept, not spot-fixed. When one fact changes, every page that repeats it is checked. Example from July 2026: after Boris FX acquired iZotope on July 2, 2026, all 44 articles were scanned for outdated iZotope references; four pages needed changes and were updated the same week, while historical mentions of older bundled versions were kept and labeled as MAGIX-era facts.
- Structured data follows the text. When a visible answer changes, the matching FAQ schema is updated with it, so search results do not show a stale answer.
What does not count as a correction
Style edits, layout changes and internal-link housekeeping do not get correction notes and do not change the substance of a guide.
Reporting an error
If you find a factual error — a wrong price, a menu path that no longer exists, a claim that does not match the current build — report it via the author's profiles on Facebook or X. Reports that check out are corrected as described above.