Corrections Policy

Errors are fixed in place, with a dated note

An error on this site is corrected in the same place it appeared, and the correction carries a dated note describing what was wrong and what it now says. We do not quietly overwrite a sentence and leave the reader with no record that anything changed.

The dated note is short and plain: the date of the change, the figure or claim that was wrong, and the source that settled it. If the correction changes a ranking, the note says so.

Error, update and clarification are marked with distinct labels so a reader knows which one they are looking at

Each logged change carries one of three labels: error, update or clarification. An error means we stated something false and have now corrected it. An update means an external condition changed and the page now reflects the new condition. A clarification means the original text was not false but could be read in more than one way, and we have made the intended meaning explicit. The label appears with the dated note so a reader does not have to infer the category from the wording.

The labels are not interchangeable. If we change a sentence about the leverage cap that applies to the FxPro entity serving Ghana because the cap itself changed, that is an update, even though the words on the page look different afterwards. If we change the same sentence because we had described the wrong cap, that is an error. Marking both as updates would hide a mistake, and marking both as errors would overstate our fault. The label has to match the cause, or the log stops being a reliable record.

A clarification is the label we use least and the one most likely to be argued about. If a reader says a paragraph on pip value for gold could be taken to mean 0.01 per standard lot when we meant 0.01 per pip on a 100 oz lot, and the original wording was ambiguous rather than wrong, that is a clarification. We do not relabel a clarification as an error to appear more responsive, and we do not relabel an error as a clarification to appear less at fault. The label is a factual claim about the change.

A correction fixes something we got wrong; an update reflects something outside us that changed

A correction responds to our own mistake, while an update responds to a change in the world the page describes. If we wrote that one standard lot of gold is 10 oz and later fixed it to 100 oz, that is a correction because the original statement was false. If a broker changes the leverage cap that applies to the entity serving Ghana, and we revise the page to reflect the new cap, that is an update because our earlier text was accurate when written. The distinction is about where the fault lies, not about how large the change looks.

The practical difference shows up in what a reader should do with the information. A correction tells a reader that something they may have relied on was wrong and should be disregarded. An update tells a reader that the page has moved with conditions and that earlier reading may now be out of date even though it was correct then. Both are logged, but only the correction carries an acknowledgment that the earlier text was in error. That acknowledgment is the reason the log stays useful over time.

We apply the same distinction to figures that depend on external conditions. The reference price of 4275.0 for XAU/USD is a snapshot, not a promise, so a change in that figure is an update. A margin example showing about $85.50 for a 0.10-lot gold position at the applicable cap is tied to a leverage condition, so if that condition changes the revision is an update. A wrong formula for converting pips to cedi would be a correction. The label follows the cause.

The log stays public because a reader cannot judge a page they cannot audit

The log stays public so that a reader can see the page's history without asking us for it. A trading page that quietly changes a margin example or a leverage statement gives a reader no way to know whether the current text is the first version or the fifth. Keeping the record open means a reader in Ghana comparing our gold page with another source can see exactly what we said before and when we changed it. That is the difference between a page that asks for trust and one that earns it.

Public logging also disciplines us. When every correction has to be dated and labeled in the open, there is a cost to getting a fact wrong that does not exist if fixes happen silently. That cost is reputational, and it is the right kind. It pushes us to check a claim about the FxPro entity serving Ghana, or about the SEC Ghana licensed operators list, before publishing rather than after a reader catches it. The log is not a marketing page; it is a record that can embarrass us, which is why it is worth keeping.

A public log also helps readers who arrive through different routes. Someone who read the page last month and returns today can check whether the parts they relied on have moved. Someone who saved a screenshot can compare it with the current log. For a high-risk instrument like gold, where a misread margin or pip value can lead to a position larger than intended, that check matters. The log does not remove risk, but it removes the extra risk of not knowing what changed.

Every logged correction carries the date it was made, the date of the original text, and the specific claim that changed

A correction is recorded with three fixed fields: the original publication date, the correction date, and the exact sentence or figure that changed. We do not rewrite the old text and leave it looking as if it was always right. The dated note sits next to the corrected passage so a reader arriving later sees both what we said and what we now say. For a gold page, that might mean noting that a margin example was updated after the applicable leverage cap for the FxPro entity serving Ghana was confirmed.

The date we use is the date the correction goes live, not the date a reader reported the issue. If a reader emails on a Monday and we publish the fix on a Wednesday, the note says Wednesday. This keeps the record tied to what was actually visible to the public. We do not backdate a correction to make the gap look shorter, and we do not leave a correction undated on the grounds that it was minor. Every logged entry has a date a reader can check.

The record also names what kind of change it was, using the three labels below. A correction entry without a label is incomplete. The point is that a reader scanning the log can tell at a glance whether a number moved because we got it wrong or because an external condition changed. For example, a note that the reference price of 4275.0 was updated is an update, while a note that a pip value was stated as 0.1 instead of 0.01 is an error. The label does the work.

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

If a broker changes its funding page, its leverage cap or its platform list after we read it, the old page was not wrong when it was written; it is out of date. That is a re-check, and we update the page and the date read rather than logging a correction.

The distinction matters because it tells you how to read the site: a dated figure is a snapshot, and a correction is an admission of a mistake. Both are visible, and neither is hidden.

How to report a mistake

Send the page address, the sentence you believe is wrong, and whatever document you are relying on to editor@kumasilearngh.com. A link to the broker's own page or the regulator's list is more useful than a memory of what a support agent said.

We check the source before changing anything, so a report that includes the document is faster to act on. We do not promise a response time, and we do not run a ticketing system; every report is read by the desk.

An error is a factual claim that was wrong when published, not a view that later looks unwise

An error worth logging is a statement that was factually incorrect at the moment we published it. If we wrote that gold pip value is 0.01 for a standard lot of 100 oz and that was right, it is not an error even if the price later moves. If we wrote a margin figure for a 0.10-lot XAU/USD position that did not match the leverage cap applying to the FxPro entity serving Ghana, that is an error. The test is whether the claim could be checked against the source we relied on at the time, not whether a reader disagrees with the conclusion.

Typos that change meaning count as errors, while typos that do not change meaning are fixed without a log entry. Writing GH₵ when the figure was in US dollars changes what a reader does with the number, so it goes in the log. Writing 'teh' for 'the' does not. A wrong regulator name, a wrong platform list, or a wrong formula for margin on a gold position all count because they mislead a reader making a funding or risk decision. The log exists for claims that could cost someone money if left uncorrected.

An error is not the same as an omission. If we failed to mention that MTN Mobile Money is the local funding route for Ghanaian readers, that is a gap to fill, not a false statement to correct. We record omissions as clarifications or updates depending on whether the missing fact changes the meaning of what was already there. This distinction matters because it keeps the log honest: readers can see whether we said something wrong or simply did not say enough. Both matter, but they are marked differently.

The writer who published the claim decides first, and a second reviewer confirms before the log entry goes live

The person who wrote the original claim makes the first call on whether it was an error, and a second reviewer confirms the label before the entry is published. This two-step exists because the writer has the context of what source they used, while the reviewer has distance from the draft. For a gold page, the writer may know they relied on a particular leverage statement for the FxPro entity serving Ghana, and the reviewer can check whether that statement actually supported the sentence. Neither alone is enough.

The time frame depends on the kind of claim. A factual error in a figure, such as a wrong pip value or a wrong lot size for XAU/USD, is treated as urgent and is reviewed the same working day it is confirmed. A clarification of ambiguous wording is reviewed within the normal editing cycle, because it does not misstate a fact. We do not promise a fixed number of hours for every category, because the review depends on how quickly the original source can be checked. What we do commit to is that no logged change goes live without the second review.

The reviewer can overrule the writer on the label. If the writer calls a change an update and the reviewer finds the original text was actually false, the entry is published as an error. If the writer calls it an error and the reviewer finds the original was accurate when written and the world moved, it is published as an update. The reviewer's decision is recorded with the entry. This is not a committee; it is one check, and its purpose is to keep the labels honest rather than to slow the page down.