Want to report a problem? Keep it short and specific. The fastest feedback is the kind that names the page, the issue, and what you saw.

What to include

• Page name or URL so the team can find the exact item.
• What looks wrong in one sentence.
• What you expected instead if the fix is obvious.
• Any evidence label involved if the point came from published terms, direct testing, or a reader report.

What helps most

If you are flagging a casino-related detail, note whether the issue is about wording, access, timing, or a missing source. That saves back-and-forth. A clear report is better than a long one.

What we can use

We can act on corrections, broken links, confusing labels, and reader-reported issues that need a second look. We can also use plain usability notes, especially if a page is hard to scan on mobile.

What to avoid

• Do not send vague praise where a correction is needed.
• Do not paste a full story if one line explains the issue.
• Do not treat a reader report as confirmed until it is checked.

How the review works

Feedback is used to improve the page, not to rewrite the evidence behind it. If a report changes a label or a note, the page should still show where the point came from. That keeps the site readable and honest.

Next step

Send the shortest version that still makes the issue clear. If the problem can be fixed in one pass, that is usually the best report.