Corrections

How to report an error

Email support@tunebible.com. Put the page address in the message and quote the sentence, table row or figure that is wrong.

Tell us what the page says, what it should say, and what you based that on. A tune file, a log, a screenshot from the tuning software or a link to the software's documentation all help. Do not send a file you do not have permission to share.

What happens next

We read every correction. We aim to reply within one business day. A clear factual error is usually fixed within two business days. A claim that needs a file check or a research-machine test can take longer, and we tell you when it will.

If we cannot confirm the correction, we say so and explain what we found. We do not change a page to match an unsupported claim.

How corrections are noted

Every corrected page gets a date-stamped note near the top of the page. The note names the change in plain words. The page's updated date changes with it. We do not make a silent edit.

A correction note looks like this:

The note stays on the page. A reader can see what changed and when without comparing old copies.

What to include

• The page address, copied from the browser.
• The exact sentence, table row or figure that is wrong.
• The correction you propose and the source for it, such as a file, a log or a screenshot.
• The software version and platform, when the error is about a table or a menu path.

You do not need an account, and you do not need to give your name.

What is not a correction

A tuning question is not a correction. If you want us to read your file and log, use the free Tune Report from your platform hub. If you disagree with a recommendation, send the file and log that support your view, and we will check it.

Contact