Corrections Policy
We want to get things right, and to fix things promptly when we do not.
Reporting an error
If you believe an article contains a factual error, an outdated statement, a broken link, or an accessibility problem, check the contact page for an available reporting channel. No verified public contact channel is configured yet. When one is available, include the page address and, if possible, a description of the problem and a source that supports the correction.
What we do
- We review the report and verify the information against reliable sources, such as official product documentation or public-agency guidance.
- If we confirm an error, we correct the article as soon as practical.
- For significant corrections that change the meaning or practical advice of an article, we add a visible note describing what changed and when.
- For minor fixes, such as typos and broken links, we correct them without a note.
- If we decide not to make a change, we will explain why where a reply is possible.
Outdated information
Software changes constantly. When product behavior described in an article changes, we update the article and its “last updated” date. Readers should always confirm product-specific details in the official documentation for their own software and plan.
Corrections log
- November 2, 2026: Corrected the annual time-saving example in Automating repetitive office tasks. Five minutes saved twice a week totals 8 hours and 40 minutes over 52 weeks, not more than 40 hours.
- November 2, 2026: Corrected File permissions explained to distinguish file owners from administrators and clarify that organizational restrictions still apply.