Corrections and Updates

Errors are fixed in place, with a date

An error is corrected on the page where it appeared, and a dated note is added so a reader can see what changed and when. The original wording is not quietly swapped out and left to look as though it was always right. The note sits with the correction rather than on a separate log.

The desk does not delete a page to make a mistake disappear. If a page is retired, that is stated, and the reason is given. A correction is treated as part of the record, not as an embarrassment to be tidied away.

Three marks, three meanings: how error, update and clarification are labelled

Every log entry carries one of three marks, and the mark is decided before the entry is written. Error means the page stated something untrue when published. Update means the page stated something true that has since changed. Clarification means the page stated something true that readers reasonably misread, and the wording has been tightened without the underlying fact changing. The three are visually distinct in the log so a reader can sort by kind rather than read every entry to find the ones that matter to them.

A clarification is the mark we use most cautiously, because it is the easiest one to abuse. If a page says a 0.10-lot gold position needs about $85.50 margin at 1:200 and readers keep assuming that figure applies at any leverage, the fix is a clarification that states the cap the figure depends on. Nothing was false. But a clarification is never used to disguise a correction: if the original sentence was wrong, it gets the error mark even when the rewrite is small. The mark follows the facts, not the size of the edit.

The marks are not a ranking of severity. An error in a pip value for gold, where one pip is 0.01, can matter more than an update to a reference price, and a clarification about which entity serves Australian clients can matter more than either. What the mark tells a reader is what kind of thing happened, so they can decide whether the earlier version affected a decision they made. The mark is assigned at the time of the fix and is not changed later.

How to report one

Report an error by writing to [email protected] with the page address and the exact wording that looks wrong. A source, such as the broker's own document and the date it was read, makes the report much quicker to check. Screenshots are welcome but not required.

Every report is checked against the source before anything is changed. If the report is right, the page is corrected and dated. If the desk cannot confirm it, the reader is told why rather than left without an answer. No response time is promised, but reports are not ignored.

A re-check is not an error

A condition that has merely changed since the check is a re-check, not an error. If a broker alters a document, a funding method or a leverage cap after the date on the page, the page was accurate when it was written and is now out of date. That is handled by re-reading the source and updating the date.

The distinction matters because it changes what a reader should do. An error means the desk got it wrong and owes a correction. A re-check means the world moved and the page needs a fresh date. Both are logged, but only one is called a mistake.

What we log as an error: the page states something that was wrong when it was written

An error worth logging is a statement that was wrong at the moment we published it, not a statement that later stopped being true. If a page said a margin example used 0.10 lots when the arithmetic actually described 1.00 lot, that is an error. If gold moved and a reference price of 4275.0 no longer reflects the market, that is not an error, because the page was accurate when written and the number was labelled as a reference. The distinction matters because it decides whether the fix is a correction with a date or an update with a new version.

We log errors in figures, formulas and factual claims: a wrong pip value for gold, a margin calculation that does not reconcile, a misattributed regulator, a funding method named that the broker does not actually offer to Australian clients. We do not log spelling, phrasing, layout, or a reader disagreeing with our judgement about risk. Those go through ordinary editing and never touch the correction log. The test is simple: could a reader acting on that sentence have made a worse decision because of it? If yes, it belongs in the log.

One borderline case is worth stating plainly. A statement can be defensible and still be corrected, if it omitted something that changes how it reads. Saying FxPro serves Australian residents without noting the entity is FxPro UK Limited and that it holds no ASIC licence would be incomplete in a way that matters, so we would log the fix even though nothing in the original sentence was literally false. Omissions that mislead count; omissions that merely shorten do not.

Who signs off on a fix, and the window we hold ourselves to

A fix is approved by the editor responsible for the page, and no entry is published without that approval. The person who spots the problem does not publish the correction alone, even when the fix is a single figure, because the same person misreading a source once is the person most likely to misread it again. Approval covers the replacement text, the mark, and the reason line. Where the fix touches the regulator caveat, the leverage cap or a margin example, it gets a second read before it goes live.

We hold ourselves to acting within two business days of confirming that a reported problem is real. Confirming is the part that takes the time: a report that a margin figure is wrong is checked against the arithmetic and the lot size before anything is changed, and a report that a regulator detail has changed is checked against the source. If we cannot confirm within that window, we say so on the page rather than leaving the claim standing unqualified. The window is a commitment about our own process, not a promise about how fast a third party responds.

The time clock starts when the problem is confirmed, not when a reader first writes in, and we state which date we are using so the log cannot be read as a claim of faster response than we delivered. A fix that is confirmed on a Friday and published on the following Monday is dated Monday. Where a correction is urgent because the wrong statement could cause immediate harm, such as a margin example that understates what a position requires, we do not wait for the normal cycle.

Why the log is public: a reader cannot audit a record they cannot see

The log stays public because a correction that only we can see is not a correction, it is an internal note. A reader deciding whether to trust a margin example, a leverage cap or a regulator caveat needs to know how often those statements have been wrong and how they were handled. Publishing the record lets them judge the page on its history rather than on our assurance about it. The log is part of the page, not a support file behind it.

Public also means complete. We do not publish a selection of corrections, and we do not remove an entry because it is embarrassing or because the error was small. If a figure was wrong, the entry that fixes it is visible for as long as the page exists. The alternative, a log that shows only the corrections we are comfortable with, would be worse than no log at all, because it would look like evidence of diligence while functioning as marketing. A partial record is a claim, and we would rather publish the whole thing.

There is a cost to this and it is worth naming. A public log makes every mistake permanently visible, including the ones a reader would never have noticed. We accept that because the alternative is asking readers to take our accuracy on faith in an area where being wrong about margin, leverage or the licensing entity has real financial consequences. For Australian readers dealing with an offshore entity that does not hold an ASIC licence, the ability to check our track record is not a courtesy, it is part of the due diligence.

The correction record: a dated entry naming the old text, the new text and the reason

A correction is recorded as a dated entry attached to the page, not as a silent edit. Each entry carries the date the fix was made, the specific text that was removed or replaced, the replacement text, and one sentence on why. The date is the date of publication of the fix, not the date a reader reported it, so the log never implies we knew earlier than we acted. Entries are appended in order, so the most recent correction sits at the top or the bottom depending on the page, and the ordering is always stated.

The old text is quoted rather than paraphrased. If a page told readers that a 0.10-lot gold position needs about $85.50 margin at 1:200 and the figure had been written as $855.00, the entry shows the wrong figure and the right one side by side. Quoting the error is uncomfortable but it is the only version of the record a reader can actually check against what they remember reading. Paraphrasing the mistake would make the log useless as evidence and turn it into a summary of our own good intentions.

The reason line is written for a reader, not for us. It says what was wrong, not that a review took place. Where the cause is a source that moved, the entry names the source and the date the source changed. We do not attach the name of the person who made the fix, because the log is about the page, and we do not attach an apology, because an apology is not information. The entry stays short enough to read in one pass and specific enough that someone can verify it.

Correction versus update: fixing a wrong statement is not the same as refreshing a right one

A correction changes a statement that was wrong; an update changes a statement that was right but has aged. If a page said the maximum leverage available to Australian clients is 1:200 and that was accurate on the day, and the broker later changed it, the page gets an update, not a correction. The original claim stays in the record as accurate-at-the-time and the new claim is added with its own date. Treating the two as the same thing would either bury real errors among routine refreshes or let stale facts masquerade as corrections.

Updates are the normal life of a reference page. Reference prices move, regulator details change, and platform line-ups shift. We refresh a reference price such as 4275.0 for gold when it stops being a useful anchor, and that is logged as an update with the date of the refresh. No reader is owed an apology for a reference price ageing, but they are owed the information that the number they are looking at was set on a particular date and may no longer reflect the market.

The practical difference for a reader is what they should do next. A correction means the page previously told them something untrue, so anything they concluded from the earlier version deserves rechecking. An update means the page is current and the earlier version was simply older. We mark the two differently precisely so that a reader scanning the log can tell whether they need to go back over a decision they made, or whether they only need to read the current numbers. Nothing in the log is marked as both.