PerpDifferent statements need different evidence
Source behaviour is checked against the provider's documentation and the fields our integration actually receives. A successful request does not establish every related field. Platform procedures and referral conditions are checked against current official guidance, with the review date attached to the relevant content.
Arithmetic examples state their assumptions and are labelled hypothetical. Live observations have data times separate from editorial dates. We do not change an article's revision date just because a collector ran or the page was rebuilt.
English articles are written for the question they answer
Editorial pages use the same product facts across languages, but the English guides develop their own examples and reading paths. Shared buttons and data labels stay consistent so a returning user can find the same action.
AI tools assist with drafting, coding and checks. This is not a claim of human-only authorship or an independent expert sign-off. We do not invent experience, credentials, interviews, account screenshots or trading outcomes to make a page appear authoritative.
A correction should identify what changed
A report is assessed against its source, date and scope. If a factual or calculation issue is confirmed, the affected explanation or code is corrected and the relevant behaviour checked again. Formatting changes are not presented as new research.
Send specific evidence through Corrections. Commercial presentation is described separately in Referral disclosure; it does not change how missing data or calculation limits are labelled.