Corrections and How to Report One

Errors are fixed in place, with a date

When a page is wrong, it is corrected in place and a dated note records what changed. The original error is not quietly deleted and the page is not rewritten to hide it, because a reader who saw the earlier version deserves to know what moved.

The note states the date of the correction and the substance of the change, in the same plain language as the rest of the page. Corrections are not buried; they sit with the content they affect.

One editor decides, and the clock starts when the report lands

One named editor decides whether a report is an error, an update or a clarification, and that editor owns the entry until it is published. The decision is not made by the person who wrote the original sentence, to avoid defending a claim. The clock starts when the report lands, not when it is read. Reports that affect a number a reader could act on are handled first. The editor checks the claim against the source, decides the kind, and dates the entry. If the editor cannot resolve it, the entry is marked as under review with the date, rather than left silent. A visible under-review mark is better than a page that looks settled when it is not.

The time to resolution depends on the kind of claim and the availability of the source, so we do not promise a fixed number of hours. A claim about the gold contract size or the pip value is quick to check against the specification. A claim about which entity serves Australia requires checking the regulator caveat and the broker's own disclosure, which can take longer. The editor records the date the report landed and the date the entry published, so the delay is visible. If a correction takes longer than a reader might expect, the log shows why in plain terms. The aim is a dated record, not a fast-looking one.

The editor also decides when a report is not a change at all. Some reports are questions, some are about a different page, and some are about a condition that has not changed. Those are answered but not logged as corrections. The editor says which, with a date, so the reporter is not left guessing. This single-decider model is deliberate: a committee would blur the kind and the date. For a page about gold pricing and margin, the decision needs to be consistent across every sentence, and one owner is the simplest way to get that. The editor's name is not published, but the role and the date are.

A changed condition is a re-check, not an error

A condition that has simply changed since the check is a re-check, not an error. If a broker alters its leverage cap, its platform list or its funding methods after a page was read, the page was accurate when written and the fix is to read the documents again.

That is why figures are dated and why a reader should verify them with the broker before acting. The regulator position is one of the facts that can change: FxPro is licensed by the FCA (UK) and CySEC. It does not hold an ASIC licence, so Australian residents deal with an offshore entity — check this before funding.

An error is a factual claim that was wrong when published

An error worth logging is a statement that was factually incorrect at the moment it went live, not a statement that later became outdated. If a page said gold pip size is 0.01 and it is 0.01, that is correct. If it said 0.10, that is an error because the fact was wrong on publication day. In practice this means errors are usually wrong numbers, wrong names, wrong formulas, or a misattributed regulator. For gold XAU/USD, a wrong pip value, a wrong lot size of 100 oz, or a wrong margin figure at 1:200 would all qualify. A typo that changes meaning also counts.

An error is not a difference of opinion or a market move. If the page said leverage up to 1:200 and the broker later lowers it, the original statement was accurate when written, so it is an update, not an error. The test is simple: could a reader at the time have relied on the sentence and been misled? If yes, log it. If the sentence was true then and only the world changed, it is a re-check. Logging opinion as error would make the log useless, so we keep the bar at factual accuracy at publication. The date of publication is the reference point, not the date a reader notices.

An error worth logging must also be material to a reader's decision. A misspelled place name in a byline is not worth a dated correction, but a wrong margin requirement for a 0.10-lot gold position is. We log errors that affect how someone understands cost, risk, instrument specification, funding, or regulation. For this site that means the gold contract size, the pip definition, the leverage cap, the entity serving Australia, and the ASIC caveat. A cosmetic slip is fixed quietly without a log entry. Materiality is judged by whether the sentence could change a funding or trading decision, not by how embarrassing the mistake is.

Error, update and clarification each carry a different mark

The three kinds of change are marked differently so a reader can tell them apart at a glance. An error is marked with the word correction and a date, and it names the false claim and the true one. An update is marked with the word update and a date, and it names the condition that changed. A clarification is marked with the word clarification and a date, and it names the sentence that was ambiguous and how it now reads. The marks are words, not symbols, because symbols get stripped or misread. Each mark sits next to the changed text and in the log, with the same date in both places. A reader should never have to guess which kind of change they are looking at.

A clarification is for text that was true but could be misread. If a sentence said leverage is up to 1:200 and a reader could take that as a target rather than a cap, the fix is a clarification, not a correction. The original sentence was accurate; the new one is harder to misread. Clarifications are the most common change on a precise page, because precision attracts edge cases. They are marked so a reader knows the meaning shifted without the facts changing. Marking a clarification as a correction would overstate the problem and erode trust in the correction label, so the distinction is enforced.

The marks are applied at the sentence level, not only at the page level. A page can carry an update at the top and a clarification halfway down, each with its own date. The log lists them in date order, with the kind named. This matters for gold pages because a change to the pip definition is an error if it was wrong, an update if the convention changed, and a clarification if the wording was vague. The same sentence can move between kinds over time, and the log shows that sequence. The mark is the reader's shortcut to the seriousness of the change, and it is kept accurate.

A correction fixes a falsehood; an update records a change in the world

A correction fixes something that was false when published, while an update records something that was true then but is no longer current. If a page said the entity serving Australia is FxPro UK Limited and that was correct, and the entity later changes, the page is updated, not corrected. The original sentence was not wrong; the world moved. If the page had said a different entity on day one, that would be a correction. The distinction matters because it tells a reader whether to distrust the original author or the calendar. Corrections imply a mistake; updates imply maintenance. Both are dated, but only corrections carry the word correction.

The distinction also affects how much of the page is re-checked. A correction triggers a review of the specific claim and any sentence that depended on it. An update triggers a broader re-check of the conditions around that claim, because a change in the world often touches several sentences. For example, a change to the leverage cap would prompt a re-check of the margin example and the risk framing, not just the cap itself. We mark the update at each affected sentence, not only at the top. This prevents a page from looking current at the top while stale in the body, which is a common failure on financial sites.

Readers should treat a correction as a signal to re-read the corrected sentence and an update as a signal to re-read the surrounding section. Neither is a reason to discard the whole page. A page with a dated correction is more trustworthy than a page with no history, because it shows the error was caught and fixed in public. A page with an update shows the author is still watching the conditions. The worst signal is silence after a known change, which is why the log exists. The label tells you which kind of attention the page received, and the date tells you when.

How a reader reports one

A reader reports a problem by emailing [email protected] with the page and the specific figure or sentence in question. Include what you believe the correct position is and, where you can, the broker document that supports it.

Every report is checked against the broker's own documents. If the page is wrong, it is corrected with a dated note; if the page is right, the reader is told why, with the source that was used.

The log stays public so a reader can audit the page without trusting us

The log stays public because a financial page asks readers to trust numbers about cost and risk, and trust without evidence is not good enough. A public log lets a reader see every correction and update with its date, so they can judge whether the page has been maintained. It also stops us from quietly changing a claim after it has been cited or screenshotted. If a reader relied on a sentence last month, the log shows what that sentence was and what it became. This is especially important for figures like the margin example at 1:200, which a reader might use to plan a position. Without a log, that reader has no way to know the figure moved.

A public log also keeps the correction process honest internally. When every fix is visible, there is a cost to logging a correction, so errors are less likely to be buried in a silent edit. The log is not a marketing page; it is a record. It does not need to be prominent on every screen, but it must be reachable from the page it describes and must not require a login. For readers in Australia, that means a plain link, not a gated download. The log is written in the same plain English as the page, because a record no one can read is not public in any useful sense.

The log stays public even when the correction is embarrassing. A wrong number in a worked example is exactly the kind of thing a reader needs to see corrected, because it shows the example is checked. Removing the evidence would make the page look cleaner and less trustworthy at the same time. We do not delete a correction entry when the page is later updated; the entry remains as history. The only case where an entry is amended is when the entry itself contains an error, and that amendment is also dated and marked. The log is a chain, not a snapshot, and the chain is the point.

A correction is a dated entry that names the old claim and the new one

A correction is recorded as a timestamped entry that states the original claim, the corrected claim, and the date the fix went live. It is not enough to silently edit the page. The entry sits on the page or in a linked log so a reader can see what changed and when. For example, if a page said a 0.10-lot gold position needs about $85.50 margin at 1:200 and that figure was mistyped, the correction would show the wrong figure, the right figure, and the date. The date is the publication date of the fix, not the date the error was first made. Both dates can appear, but the live date is the one readers rely on.

The entry is dated to the day, in Australian Eastern time, because readers in Australia are the audience. A correction dated only to the month is not precise enough for a financial page. Each entry also names the section it affects, so a reader can jump to the corrected text. The corrected text itself carries a short note that it was revised, with the same date. That way the history travels with the sentence, not only with a central log. The log and the in-page note must agree; if they diverge, the log is treated as the record of truth. This duplication is deliberate and is checked whenever a page is next edited.

A correction is not a rewrite of the whole page. We change the minimum text needed to make the claim accurate, then date it. If the error was a wrong formula, the formula is fixed and the correction names the formula. If the error was a wrong entity, the entity is fixed. We do not use a correction as cover for a broader refresh; that would be an update and is marked differently. Keeping corrections narrow makes the log readable and makes it harder to bury a change inside a large edit. A reader should be able to see exactly which sentence moved and why, without reading a diff of the entire page.