Corrections and how we handle them

Fixed in place, with a date

An error on Karoo Picks is corrected in the place where it appeared, and the correction carries a note with the date it was made. We do not delete a page to make a mistake disappear, and we do not swap a wrong figure for a right one without saying that we did. A reader who read the earlier version should be able to see what changed.

This matters most with numbers. If a leverage cap, an entity name or a funding route was stated incorrectly, the corrected sentence stands next to a short note explaining what was wrong and when it was fixed. The rest of the page is left as it was so the correction is visible rather than buried in a rewrite.

Who decides on a correction and how quickly it is logged

The decision rests with the editor who owns the page, and the target is to log a confirmed error within two working days of verification. Verification means checking the claim against the facts we hold, such as the instrument specification for gold (XAU/USD), the stated leverage cap, or the correct FxPro entity for South Africa. If the check confirms an error, the editor corrects the page and writes the log entry on the same day. If the check is inconclusive, the entry waits rather than guessing.

A reader report starts the process but does not decide it. The editor compares the reported passage with the source facts and with the rest of the page, because a sentence can be wrong in isolation but right in context, or the reverse. For example, a report that a margin figure is wrong may turn out to be a misunderstanding of the lot size, in which case the fix is a clarification rather than an error entry. The editor records which label applies and why, so the decision is visible.

Time-sensitive statements, such as a leverage cap or a regulator caveat, are checked first because they carry the most risk for a South African reader. A wrong entity name or a missing caveat about checking which FxPro entity your account is opened with is treated as urgent. Routine clarifications can take longer, but they are still dated when they go live. The two-working-day target is a target, not a guarantee, and the log shows the actual date rather than the target date.

How to report an error

Send the report to [email protected] with the page address, the sentence you believe is wrong, and the broker document that shows the correct position. A report with the document attached can be checked quickly; a report without one usually cannot be checked at all, because we will not change a figure on the strength of a memory.

We do not promise a response time in hours or days, and we would rather be slow and right than fast and wrong. What we do commit to is that every report with evidence is looked at, and that a confirmed error is corrected in the way described above.

Correction versus update: two different records on Karoo Picks

A correction fixes something that was wrong on the day it was published; an update records something that became different after publication. If we wrote that a 0.10-lot gold position needs about $85.50 margin at 1:200 and that was correct when written, a later change to the leverage cap makes the page out of date, not wrong, and the fix is an update. If we had written $8.55 when the correct figure was $85.50, that is a correction. The distinction matters because it tells the reader whether to trust the method or only the date.

Updates are dated and logged too, but they carry a different label and do not imply earlier negligence. A gold reference price moving away from 4275.0, a new funding method being added or removed, or a regulator caveat being reworded by the broker all produce updates. The original text is preserved in the log with its original date, and the new text is added with the update date. Readers can therefore see what the page said at any point, which is the only way to judge whether an old screenshot or quote was accurate when it was made.

The practical difference for a reader is what to do next. A correction means the earlier figure should be discarded and any decision based on it revisited. An update means the earlier figure was right for its date but should not be used now. Both are visible in the same public log, separated by label and date, so a reader who quotes a Karoo Picks number can say whether it was corrected or simply superseded. That is the distinction that keeps a trading reference honest over time.

Why the correction log stays public on Karoo Picks

The log stays public because a reader deciding whether to trust a margin example or a leverage statement needs to see whether the page has been fixed before. If corrections were private, a reader comparing an old screenshot with the current page would have no way to tell whether the difference was a fix or a revision of opinion. Public entries also discourage careless drafting: knowing that a wrong pip value will be quoted in the log is a reason to check the number before publishing. The log is part of the page, not a separate notice.

Public logging also matters because South African readers may rely on the regulator caveat about checking which FxPro entity their account is opened with. If that caveat was once missing and later added, the log shows when it appeared, which helps a reader understand why older copies of the page may not contain it. The same applies to the leverage cap: if a page once implied that 1:200 was a target rather than a ceiling, the correction entry records that fix. The log is the audit trail for those specific statements.

Keeping the log public does not mean every edit is announced. Routine copy-editing, such as shortening a sentence or fixing a typo that does not change meaning, is not logged. The public record is reserved for changes that affect what a reader would understand as a fact, a figure, or a condition. That boundary is stated so the log does not become noise, and so a reader can trust that an entry means something substantive changed.

What rises to a loggable error on Karoo Picks

A loggable error is a statement on a Karoo Picks page that is factually wrong against the source we cited at publication, not a matter of interpretation. Examples include a wrong lot size for gold (XAU/USD) where we wrote anything other than 100 oz per standard lot, a pip value stated as anything other than 0.01, a leverage cap that does not match the FxPro entity serving South Africa, or a rand amount that does not follow from the stated USD figure at the exchange rate we referenced. If the page said one thing and the source said another, it is an error.

A change in market conditions is not an error. If the gold reference price moves away from the 4275.0 level we used in a worked example, or if a broker changes its own terms after we published, the original page was still correct on its date. Those cases go through the update process, not the error log. The test is simple: could we have known the correct fact at the time of writing by checking the source we named? If yes and we got it wrong, it is loggable. If no, it is an update.

Errors of omission also qualify when the missing fact changes the meaning of the page. A margin example that leaves out the leverage cap, a funding section that names a method FxPro does not offer to South African clients, or a regulator note that omits the entity caveat all count. So do broken internal links to a source, a mislabelled table column, and a rand conversion that used the wrong direction. Typos that do not change meaning, formatting glitches and stylistic preferences are not logged as errors; they are fixed quietly and do not enter the log.

How error, update, and clarification are marked in the log

Each entry carries one of three labels: error, update, or clarification. An error entry quotes the wrong text, gives the corrected text, and states the date. An update entry describes new information added, such as a note that local funding includes e-wallets, without quoting an old sentence as false. A clarification entry keeps the original wording but adds a condition or example that removes ambiguity, such as stating that 1:200 is a cap and not a setting to aim at. The label appears at the start of the entry.

The labels are not interchangeable. A clarification is used when the original sentence was accurate but could be read two ways, for example a margin figure that did not say which lot size it referred to. An update is used when the facts themselves have moved, such as a change in the leverage available to eligible clients. An error is used only when the original statement contradicted the facts we hold at the time of publication. Mixing them would blur the record, so each entry is assigned one label and one only.

Readers can filter the log by label if they want to see only corrections, only updates, or only clarifications. The label also appears in the page history view, so a reader looking at an old version can see which entries apply to the passage they are reading. This three-way split is more precise than a single changed marker, and it lets the site show that most edits are clarifications or updates rather than outright errors, without hiding the errors that do occur.

The difference between a correction and an update on Karoo Picks

A correction fixes something that was wrong when it was published; an update adds or refreshes something that was right when published but has since changed or become incomplete. For example, if we wrote that the maximum retail leverage was 1:100 when the stated cap is 1:200, that is a correction. If we later add a note that eligible or professional clients may see up to 1:500 depending on the instrument, that is an update, because the original statement was not false, just incomplete for that audience. The log marks them differently.

Updates are dated and described in the same log but are not framed as errors. They carry a note such as added detail on professional leverage or expanded funding methods to include local cards, bank transfers in ZAR, and e-wallets. A correction entry always includes the original wording; an update entry describes what was added without quoting a false sentence. This distinction keeps the record honest: readers can see that we are not labelling every improvement as a mistake, and they can judge how often each type occurs.

The practical effect is that a page can have several updates and no corrections, or the reverse. A page with many corrections is not automatically unreliable, but it does show where the original drafting was weak. A page with many updates shows where the topic moves, such as changes in leverage caps or funding options. Both are visible, and neither is hidden by merging the two categories into a single change log with no labels.

Changed conditions are a re-check, not an error

If a broker changes its entity, its leverage cap or its funding routes after we read the documents, the page was not wrong when it was written. That is a re-check, not a correction, and it is handled by updating the page to the current documents with the new read date recorded. We do not treat a changed fact as a mistake we made.

The distinction is worth keeping because it tells a reader what kind of problem they have found. An error means we misread a document; a re-check means the document itself moved. Both are worth reporting, and both are handled, but only the first gets a dated correction note.

How a correction is recorded and dated on the page

A correction is recorded as a dated entry in the public log that names the page, quotes the original wording, states the corrected wording, and gives the date the change was made. The date is the day the corrected version goes live, not the day the error was first reported. Each entry carries a short reason, such as a misstated pip value or an incorrect entity name, so a reader can see what changed without opening the old version. The entry stays attached to the page permanently, even after the page is rewritten.

The record is kept in a single log rather than scattered across page footnotes, so a reader can scan every correction in one place. Each entry uses the page title and the section heading where the error appeared, which makes it possible to find the exact passage. If the correction affects a worked figure, such as the margin needed for a 0.10-lot gold position at 1:200, the entry shows both the old and new amounts. Dates are written in full, with day, month, and year, to avoid the ambiguity between South African and international formats.

Dating a correction separately from an update matters because the two answer different questions. A correction date tells you when a factual mistake was fixed; an update date tells you when new information was added. The log shows both, but only the correction entry quotes the old text. This means a reader comparing an old printout with the current page can match the change to a specific entry and a specific day. No correction is backdated to the original publication date, because the fix did not exist then.

How a correction is dated and entered in the log

Every correction is dated on the day the fix goes live, not the day it was reported. The log entry shows the publication date of the original page, the correction date, the section affected, the old wording and the new wording, and the source that settles the point. For a gold pip or lot-size error, that source is the contract specification we cite; for a leverage or entity error, it is the FxPro legal documentation for the entity serving South Africa. The date is the audit trail, so it is never backdated to make a page look as if it was always right.

The entry is written before the page is edited, so the log and the live page cannot drift apart. A correction that changes a number in a worked example, such as the $85.50 margin figure for a 0.10-lot gold position at 1:200, is recorded with both the old and new numbers visible. Rand amounts are recorded with the exchange rate and date used, because a rand figure without its rate is not reproducible. If the correction touches more than one section, each section gets its own line in the log under the same correction date.

Dating follows South African time and is shown in plain day-month-year format. A correction made after a page has been live for months is still dated on the day it is made; the gap between publication and correction is visible in the log and is not hidden. If a correction is itself corrected, the second entry is dated separately and links to the first, so the chain of changes remains readable. Readers can see not just the current wording but the sequence of dates on which each wording was live.

What qualifies as an error worth logging on Karoo Picks

An error worth logging is any published statement that misstates a verifiable fact, such as a wrong instrument code, an incorrect pip value for gold (XAU/USD), a leverage figure that exceeds the stated cap of 1:200 for retail clients, or a regulator attribution that names the wrong FxPro entity. A worked example is a margin calculation that produces a different rand amount from the one shown, or a claim that a standard lot equals 10 oz instead of 100 oz. If the statement can be checked against the facts we hold, and it is wrong, it belongs in the log.

Errors also include omissions that change the meaning of a sentence, such as leaving out that 1:200 is a cap rather than a default setting, or failing to state that the FxPro entity serving South Africa is FxPro Markets Direct Costa Rica Latam SRL. A missing regulator caveat about checking which entity your account is opened with is an error because it removes a condition the reader needs. Style preferences, tone, and whether a paragraph could be shorter are not errors and are not logged; they are handled through ordinary editing without a public entry.

A number that depends on conditions we do not publish, such as a spread or a minimum deposit, is not an error if it is described as depending on the broker and the account type. The error test is whether we asserted a specific figure we were not given. If we said a spread was a particular value, that is an error because no such figure is in our source facts. If we said spreads vary by account and market conditions, that is correct and stays. The same test applies to rand amounts, leverage ratios, and dates.