Editorial transparency
Corrections and source challenges
Every product claim can be challenged. A useful correction identifies the exact page and passage, a current primary source, and the requested change.
The Open Mercato Guide is an unofficial educational resource published by an Open Mercato implementation business. We also offer commercial implementation services. It is not the official Open Mercato documentation.
What to include
- The full page URL and the exact passage being challenged.
- A primary-source link: code, documentation, license, release record, or official public document.
- The date on which the source was checked and a short explanation of the discrepancy.
- The proposed correction and whether it concerns a product fact, editorial assessment, or deployment-specific conclusion.
Send a correction
Send us the page URL and describe what needs correcting. You can use our contact form.
Keep confidential information, personal data, keys, tokens, and undisclosed security details out of the submission. Product defects should follow the official product repository’s reporting policy. That repository does not contain this guide.
How corrections are assessed
Current code, licenses, and dated primary records take priority. Documentation can drift, so a discrepancy between documentation and code must be disclosed explicitly.
A material factual change should update the page review date. Editorial judgments and deployment conclusions must remain clearly separated from product facts.