Corrections Policy
Accuracy matters in electronics. If you find an incorrect pinout, unsafe wiring suggestion, code issue, outdated specification, or broken reference, please tell us.
What to report
- Incorrect pin numbers, polarity, wiring, voltage, or current information.
- Code that fails to compile or behaves differently from the documented result.
- Outdated board, component, library, or firmware details.
- Broken links, missing references, misleading images, or unclear instructions.
- Simulator behavior or compatibility claims that do not match the current implementation.
How to submit a correction
Email [email protected] with the subject “Content correction”. Include the exact page URL, the section or step, what you believe is wrong, and the corrected information or a reliable source where possible.
For code or simulator issues, include the board model, component/module version, library version, compiler or runtime message, and the steps needed to reproduce the issue. Screenshots or a small code sample can help. Never send passwords, API keys, or private access tokens.
You can also start from our Contact page.
How we review reports
We review reports against relevant datasheets, official documentation, reproducible tests, and other reliable technical evidence. We may ask for clarification before changing a page. A report is not automatically accepted simply because it is submitted; we aim to verify the issue first.
How corrections are made
When an error is confirmed, we update the affected information. For material changes that could alter a reader's build, wiring, safety, or understanding, we aim to add a brief correction or update note to the page. Minor spelling or formatting fixes may be made without a separate notice.
Safety-critical information
If you identify advice that could damage equipment or create a safety risk, please put “Safety-critical correction” in the email subject. Do not rely on an online tutorial or simulator alone to determine whether a physical circuit is safe. Check manufacturer documentation and use appropriate electrical precautions.
Response times
We aim to acknowledge useful reports within a reasonable period, but review time depends on the complexity of the issue and the availability of hardware or documentation. SolderHub is independently operated, so urgent corrections may not receive an immediate response.