Corrections Policy

How we fix errors

If we publish something that is factually wrong, we correct it on the same page. We add a dated note at the bottom of the article that says what was changed and when. We do not silently edit a sentence and pretend it was always right.

The original error remains visible in the correction note, so readers can see what we got wrong. We do not delete articles just because they contain a mistake. Transparency about our errors is part of our trust layer.

How to report an error

Send an email to editor@krugerpath.com with the article title, the sentence you think is wrong, and the correct fact if you know it. Please include a source if you have one. We check every report against the broker's own documents.

We do not promise a reply within a specific time, but we do review every correction request. If we agree that an error was made, we fix it and add the dated note. If we disagree, we may reply to explain why.

What is not an error

A broker changing its spreads, leverage, or regulations after we publish is not an error on our part. It is a re-check. We note the date we read each document, so if the broker changes something later, our article is simply out of date.

We update reviews when we learn of a material change, but we do not monitor every broker every day. If you see a figure that no longer matches the broker's current documents, tell us and we will re-check it as soon as we can.

What Counts as an Error Worth Logging

An error worth logging is any factual inaccuracy that could mislead a reader about a traded instrument, cost, rule, or regulatory status, and it is logged when it has a material impact on understanding. On this site, that includes a wrong gold contract size or pip value, an incorrect margin example where the arithmetic does not match the stated leverage cap, a funding method that is not actually offered, or a misleading regulatory claim. If a number is missing and a reader could act on the gap, that is also logged as an omission, because absence of a cost or limit can be as harmful as a wrong figure.

An error is not worth logging when it is a stylistic choice, a difference of opinion, or a change in market conditions that does not alter a stated fact. For example, the spot gold price shown as 4275.0 is a reference point and will move; that is not an error. A sentence that says margin depends on the chosen leverage and gold price is also not an error when those variables change, because it describes a dependency rather than a fixed value. The test we apply is simple: would a reader make a different trading decision if the text stayed as it is? If yes, it is logged.

The scope of what we log covers every page on this site, including this corrections page itself. If a previous correction note says a fix was made on a date but the change is not visible in the archived version, that is an error. If a cross-reference points to a section that does not exist, that is logged. We also log errors in formulas, such as a margin example that does not align with the stated leverage cap of 1:200 for retail or 1:500 for eligible clients, because a reader might copy that formula. Anything that touches a number, a rule, or a claim is in scope.

How a Correction Is Recorded and Dated

Every correction is recorded as a dated entry in the public log with three parts: the original text, the corrected text, and the date the change went live on the page. The date is the day the page was republished, not the day the error was first noticed or reported, because readers need to know which version they are looking at right now. For example, if an error is reported on a Monday and fixed on a Wednesday, the log shows Wednesday as the correction date. This avoids confusion when someone compares an old screenshot with the current page.

The log entry also includes a short reason for the change, written in plain language so a beginner can understand why the old text was wrong. We do not hide behind vague phrases like 'updated for accuracy'; instead, we say exactly what changed, such as 'the previous margin example used a leverage of 1:500 but the retail cap is 1:200, so the margin amount was recalculated'. The entry is immutable: once a correction is published, we do not edit that entry later, even if we make another correction to the same sentence. Each fix gets its own dated entry.

For corrections that affect a number, the log shows both the old and new number side by side, along with the unit. If a page said a 0.10-lot gold position needs about $85.50 margin at a leverage cap that was later clarified, and the correct figure under the stated cap is different, we do not state the new figure here unless it is already on the page; instead, the log points to where the corrected margin example now appears. The date format is always day month year, for example 15 March 2025, to avoid confusion between US and international date orders.

The Difference Between a Correction and an Update

A correction fixes a factual error that was wrong at the time of publication, while an update adds new information that was not known or not included before but does not make the old text false. For example, if we had written that FxPro offers only MT4 and MT5, and later cTrader was added to the list, that is an update, not a correction, because the original statement was true at the time. A correction would be if we had written MT6, which never existed. The distinction matters because corrections are logged with a date, while updates may be noted as 'added on' without implying the old text was wrong.

In practice, many changes are updates rather than corrections, and we do not log every update in the corrections log. If the reference gold price moves from 4275.0 to a new level, that is an update to a market data point, not a correction, and it is changed silently on the page with a 'last updated' timestamp. If a new funding method becomes available, that is an update. Only when an existing statement becomes false, such as a funding method that is withdrawn, does it cross into correction territory. We log corrections, not routine updates.

There is one grey area: a change that corrects an omission. If a page failed to mention that local bank transfers can take up to two business days, and that delay could affect a reader's plan, adding that information is a correction of an omission, because the absence was misleading. In contrast, adding a new paragraph about e-wallet fees is an update, because the previous text did not imply there were no e-wallets. We treat material omissions as errors and log them with the same detail as a wrong number.

Why the Log Stays Public

The log stays public because readers in South Africa need to verify that the information they acted on was correct at the time they used it, and a public record is the only way to do that honestly. If we fixed errors silently, a reader who lost money because of a wrong margin example would have no way to prove the page once said something different. By keeping the log public and dated, we give readers a tool to check whether a mistake they remember was real and when it was fixed. This is especially important for trading content, where a small error in a gold contract size can change a position's risk.

A public log also forces us to be careful before publishing, because every error becomes a permanent entry that anyone can see, including competitors and regulators. We cannot quietly edit a mistake and pretend it never existed. This does not mean we are error-free; it means we are accountable. For a beginner, this matters because you can see how often we correct ourselves and what kinds of mistakes we make. If a page has many corrections, that is a signal to double-check the current version before relying on it.

Finally, the public log is our way of showing that corrections are not just for compliance but for reader trust. We do not hide corrections behind a login or a support ticket. The log is linked from the footer of every page, so a reader can always find it. It includes the date of each correction, the old and new text, and the reason, so there is no ambiguity. In a market where brokers and publishers often bury changes, a public log is a simple promise: if we got something wrong, you will know exactly what, when, and why.

What Counts as an Error Worth Logging on Krugerpath

An error worth logging is any factual inaccuracy in our gold trading content that could mislead a reader about costs, risks, or how the market works. A wrong number for a pip value, an incorrect margin formula, or a claim that leverage is a guaranteed profit tool all qualify. We log mistakes that affect a reader's financial decisions, not just cosmetic slips. For example, if we wrote that one standard lot of XAU/USD is 10 ounces instead of 100, that is an error worth logging because it changes position sizing and risk calculations. Our standard is whether a reasonable beginner relying on the page could be financially harmed by the mistake.

An error in a worked example is always worth logging, especially when it involves the gold margin calculation. If we state that a 0.10-lot position requires about $85.50 margin at 1:200 leverage and the actual figure is different, we record the correction. We also log errors in regulatory statements, such as saying FxPro's South African entity is regulated by the FCA when the precise caveat is that an FSCA licence applies to a specific entity. Any mistake that misrepresents the maximum leverage cap of 1:200 for retail clients is logged, as that directly influences risk. We do not log subjective wording choices, but we do log objective errors.

An error worth logging includes a broken formula or a mislabelled instrument detail. If we say one pip in gold is 0.10 instead of 0.01, that is logged because it distorts profit and loss calculations. We also log errors in the funding methods list, such as claiming a payment option we do not support. A wrong currency symbol or an incorrect local payment method like stating e-wallets are unavailable is logged. The test is simple: if a reader in South Africa could act on the false information and lose money or misunderstand a risk, we fix it and add it to the public log.

How a Correction Is Recorded and Dated on Krugerpath

Every correction is recorded in the public log with the exact date it went live on the page, using the format of day, month, and year in South African style. We add a new entry at the top of the log, not silently editing old entries. Each entry states the original error, the corrected fact, and the page affected. For example, if we corrected a margin figure for gold from $85.50 to another amount, the log would say: 'On 15 March 2025, corrected the margin for a 0.10-lot XAU/USD position at 1:200 leverage on the leverage page.' We do not backdate corrections; the date is the day the fix was published.

The log uses a simple, dated format without timestamps, because readers need to see the sequence of changes, not the exact minute. Each entry is permanent and cannot be edited or removed later. If a correction itself is found to be wrong, we add a new entry that supersedes the old one, rather than altering the original log entry. We also note whether the error was in a numerical value, a formula, or a regulatory statement. For instance, if we had stated the wrong pip size for gold, the log would record: 'Corrected XAU/USD pip value from 0.10 to 0.01 on the pip value page.'

A correction is recorded only after it has been verified against the source facts, such as the FxPro entity that serves South Africa or the standard contract size for gold. We do not log a correction until the page is actually updated, so the date in the log matches the visible change. Each entry is concise and factual, with no explanation of why the error happened unless it is relevant to the reader. We include the section or page name, but not the author's name, because the log is about the content, not the person. This keeps the record clean and focused on accuracy.