Corrections
How to report an error on FPGA Guide, what happens when you do, and the public log of corrections made.
Errors happen, and on a site that publishes daily they will happen more than once. This page says how to report one, what we do about it, and where the record is kept.
How to report an error
Email the editor through the contact page. Include the page address, what is wrong, and if you can, what is right and where that can be checked. A link to a datasheet, a user guide or a standard is the fastest way to get a fix.
You do not need to be certain. “This looks wrong to me” is a useful report. We will check it.
What happens next
| Step | When |
|---|---|
| Triage: we read the report and decide whether it is a correction, an update or a disagreement | Within a few days |
| Fix: the page is changed, and its “updated” date moves | As soon as we have confirmed the right answer |
| Note: a dated line at the bottom of the page says what was changed | At the same time as the fix |
| Log: the correction is added to the public log on this page | At the same time as the fix |
If a report turns out to be wrong, we reply to say why, with a source. If we cannot decide, the page is marked as disputed until we can.
Reports that reach us by email are answered when they are resolved, not when they are received. A silent week means we are still checking, not that the report was ignored.
Correction or update
A correction is a change to something that was wrong at the time it was published: a wrong number, a wrong part name, code that did not do what the text said, a claim not supported by the cited source. Corrections get a dated note on the page and an entry in the log below.
An update is a change to something that was right when published and is no longer: a new tool version, a renamed product, a board that went out of production, a link that moved. Updates move the “updated” date and, on reference pages, the “last verified” date. They do not get a log entry, because the old content was not an error.
A matter of opinion, such as whether synchronous resets are better than asynchronous ones, is neither. We may add a counterpoint to the page if the argument is a good one.
The “last verified” convention
Every reference page shows two dates. “Updated” is the last time the content changed. “Last verified” is the last time a person or an automated check confirmed that the versions, device lists, prices and links on the page were still current. A page can be updated without being verified (a typo fix) and verified without being updated (everything checked out).
A weekly job rechecks the facts that change most often and moves the date forward when they pass. When a check fails the page is marked stale until a person has looked at it. The date is there so you can judge for yourself how much to trust a page.
Corrections log
Each entry gives the date, the page and a one-line description of what was wrong and what was changed. Entries stay here permanently.
The log starts empty. FPGA Guide was launched on 13 November 2026 and no corrections have been recorded yet. The first entry will appear here when the first error is fixed.