Technology moves and mistakes happen. If something here is wrong, out of date, or
no longer matches how the platform behaves, we want to know — this is the most
useful mail we get, and it is handled before everything else.
How to report an error
Email thorsteinn.halldorsson@gmail.com with:
- the URL of the article (a link to the exact section helps most);
- what is wrong — the claim, command, or configuration step in question;
- what you saw instead, and the product, API, or CLI version you saw it on.
That last point matters more than it sounds. Most guidance that stops working
stops working because a platform version moved, so knowing your version usually
tells us whether the article was wrong or has simply aged past its "Tested
against" line.
What happens next
This is a one-person publication, so replies are personal rather than instant. We
aim to answer within a few business days. Even when a reply takes longer, a
confirmed factual error gets fixed in the article as soon as it is verified.
The claim is checked against current platform behaviour. If it is confirmed, the
article is corrected; if it turns out to be right as written, we will tell you
why.
How corrections are marked
Correcting an article updates the article itself and its modified date. When a
revision lands more than a day after publication, a "Reviewed" date appears
beside the byline showing when the article was last updated — so you can always
see that a page has been revised, and when. The original publication date stays
on the page too.
Where a correction changes the substance of the guidance rather than fixing a
typo, we say so in the article rather than quietly editing it. Articles that are
superseded are noindexed or redirected to their replacement, never silently
deleted — see the editorial policy.
Corrections issued
No corrections have been issued to date. Any that are will be listed here,
with the date and what changed.