This page records every correction made to EnginStack: what changed, when, and why. It exists because a reference site is only as trustworthy as its willingness to say where it was wrong.
Correction Policy
- Corrections are logged whether or not a reader reported them. A log that contains only reader complaints measures the readers, not the site.
- A correction names its source. If a constant changes, the standard that governs it is named. If a historical claim changes, the investigation record is named.
- Disagreement is stated, not resolved by vote. Where two authorities give different figures, the page gives both and the range, rather than choosing the version that is repeated most often.
- Silent edits are not made to conversion values. The constants themselves are exact and should not need editing; when one does, it means a page was wrong, and being wrong is something this log exists to record.
How to Report a Correction
Email [email protected] with five things: the page URL, the value or sentence you believe is wrong, the value you believe is correct, the source you are checking it against, and whether the error changes any answer the page gives. Reports that include a citation are verified first because the work is then confirmation rather than research.
If you are checking a conversion constant, the most useful sources are listed in full on the methodology page.
Correction Log
| Date | Scope | Change | Reason |
|---|---|---|---|
| 2026-10-07 | Site-wide | Harmonised the converter count to 269 across the homepage, the about page and llms.txt; corrected the area category (8 to 12 converters) and the volume category (24 to 30) in llms.txt. | Three surfaces disagreed with each other and with the actual page inventory. Found during a full-site audit. |
| 2026-10-07 | Homepage | Removed a duplicated brand name from the page title, and replaced an em dash used as a minus sign in the Fahrenheit to Celsius formula shown in the popular conversions table. | Title defect and typographic error found during the same audit. |
| 2026-10-07 | Time Conversion Guide | Replaced two external references that had stopped resolving: the IERS bulletins page and the BIPM TAI page both returned 404 after their publishers reorganised. They now point to the current IERS Bulletin C file and the BIPM time department. | A page whose argument rests on published timekeeping standards must not cite dead links. |
| 2026-10-04 | S-81 Isaac Peral case study | Checked the weight and cost figures against the primary reporting and added the sourcing caveat that the official inquiry never confirmed a decimal point error specifically. | The popular account of the submarine's overweight problem ascribes it to a decimal point. The official record describes a weight deviation without naming its cause, so the page now separates the two. |
| 2026-09-22 | Deployment surface | Removed internal documentation and tooling from the publicly served directory and from the public repository, and rewrote the exclusion rules so that internal files are excluded by pattern rather than by an enumerable list. | Enumerated exclusion lists fail open: a new internal file is published by default. Pattern rules fail closed. |
| 2026-09-18 | 351 pages, site-wide | Repaired a batch-generation defect that had replaced certain symbols and the character following them with a single em dash. Affected sequences included subscripts such as CO2, superscripts such as 10 to the ninth, and minus signs in ranges such as 15 to 20 percent. | A character-level corruption introduced by an earlier bulk edit. Each repair was reconstructed from context and checked for conservation of characters. |
The log is ordered newest first and is not pruned. Older entries remain even after the pages they refer to have been rewritten several times, because the sequence is the record.
Frequently Asked Questions
How do I report an error on EnginStack?
Email [email protected] with the page URL, the value or statement you believe is wrong, the value you believe is correct, and the source you are checking it against. A report that names the standard is acted on fastest, because the fix is then a matter of confirming the citation rather than re-deriving the constant from scratch.
Do you publish corrections even when nobody noticed the error?
Yes. The log below includes changes that no reader reported. A reference site that only records the corrections someone complained about is telling you about its readers, not about its accuracy. Silent fixes destroy the only evidence a reader has that the site is being maintained.
What happens if a published standard changes and a page becomes outdated?
The page is updated and the change is logged with the date the standard changed and the date this site followed it. Recent examples include the retirement of the US survey foot at the end of 2022 and the 2019 redefinition of the SI base units.
Do you remove pages instead of correcting them?
Not as a way of hiding an error. A page is only withdrawn if the subject itself no longer exists, and if that happens the withdrawal is recorded in the log. Quietly deleting a page that contained a mistake would leave every inbound link and every reader who copied the number still holding the bad value.
Can I reuse a conversion from this site?
The constants themselves are legal definitions or published conversion factors and belong to nobody. The wording, the layout and the case-study research are this site's work, and republication requires an attribution link to the original page. Each page carries that condition in its metadata.