Skip to main content
Dev Utilities Pro

Editorial

Corrections

Maintained by · Last updated .

Bedrocka Tools believes that transparent corrections strengthen trust more than silent fixes. When we identify an error in a calculator or piece of content — a wrong algorithm, a misread spec, a platform behavior that diverges from our implementation — we acknowledge it here, fix it promptly, and document what was wrong, when it was identified, and who reviewed the fix. This page lists every correction made. As of today, no corrections have been logged — but we will add them as they happen.

For the full update-and-correction policy, see Section 5 of our editorial standards.

How to report an error

Email info@bedrockatools.com with the calculator slug or article URL, the inputs you used, the output you received, and what you believe the correct output should be (with a reference to the spec or platform documentation, if applicable). We respond to every report within three business days. If the tool is wrong, we fix it, publish a correction note here, and update the “Last Reviewed” stamp on the affected page.

Correction log

No corrections logged yet. As of , the calculators on this site have not had any material errors reported and confirmed. We expect that to change over time — when it does, entries will appear here in reverse-chronological order.

What counts as a correction

We log a correction when any of the following changes after a page has been published:

  • A calculation result changes for a given input set — the algorithm was wrong, or a spec constant (field range, encoding rule, base value) was inaccurate.
  • A cited primary source is found to have been misread, misquoted, or wrongly attributed (e.g., citing the wrong RFC section for a Base64 alphabet value).
  • A material claim in explanatory copy is found to be inaccurate — not just imprecise, but wrong (e.g., claiming a cron day-of-week numbering that contradicts the POSIX spec).
  • A platform dialect behavior documented on this site is found to differ from actual platform behavior (e.g., an AWS EventBridge validation rule changed).
  • A prior correction itself was incorrect — a meta-correction, logged with reference to the original correction.

Routine updates that do not change a result — refreshing a platform URL, replacing a cited URL with a canonical redirect, copyediting for clarity — are tracked in the page's “Last Updated” date but not logged here as corrections.