Corrections

Corrections and re-checks

Errors are fixed in place with a dated note, never silently, and a condition that merely changed since the check is a re-check, not an error.

Errors are fixed in place, with a date

When a page is wrong, it is corrected in place and a dated note is added to the page saying what changed. The desk does not quietly edit a page and pretend the earlier version never existed, and it does not delete a page to hide a mistake. The dated note stays with the correction so a reader can see the history.

A correction is for something the desk got wrong: a misread figure, a wrong entity name, a formula that did not work, a statement that contradicted the source. It is not for a broker that changed its terms after the date read. That distinction is the whole point of the next section.

Who Decides on a Correction and in What Time

The person who decides on a correction is the editor responsible for the page, not the original writer alone and not an automated tool. The editor checks the report against the facts we hold, confirms whether the statement was wrong when published, and decides whether the change is an error, an update, or a clarification. For facts that depend on a regulator, such as the FCA, CySEC, or FSCA licence status of FxPro, the editor confirms the source before marking a correction. The editor also writes the log entry and sets the date. This keeps one accountable decision point.

The time to decide depends on the severity and the source. A wrong number that could mislead a reader about margin, such as a leverage figure or a pip value for gold, is treated as urgent and checked as soon as it is reported. A wording clarification can wait until the next scheduled review. We do not promise a fixed number of hours because verification depends on the source, but we do promise that every report is read and that the log shows the date of the decision. If a source cannot be confirmed, the page says so rather than guessing.

The editor also decides when not to change the page. If a report is based on a misunderstanding, the editor may add a clarification rather than a correction, or may leave the page and explain in the log why no change was made. That decision is also dated and public. For a page that cites conflicting leverage caps from a review, the editor may decide to keep the conflict visible rather than pick one number. The decision is recorded so a reader can see the reasoning, not just the outcome.

How to report an error

Report an error by writing to editor@calabartryoutng.com with the page address, the sentence you believe is wrong, and the source you are relying on. A link to the broker's own document or to the SEC Nigeria register is more useful than a screenshot alone, because the desk has to read the source before it changes a page.

The desk will check the claim against its own note of the date read. If the page is wrong, it is corrected with a dated note. If the page was right on the date read and the broker has since changed, the reader is told that, and the page is re-checked and re-dated rather than marked as an error.

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

A condition that changed after the check is a re-check, not an error. If a broker moves its Nigerian clients to a different entity, adds or drops a funding route, or changes its leverage terms, the page was not wrong when it was written; the world moved. The desk re-checks the page, updates the figure and moves the date read forward.

This matters most for figures that are known to be unstable. The leverage position is a good example: the page records that the maximum is up to 1:200 via the offshore entity while one review cited 1:30/1:20 caps, conflicting and not verified at review. If that changes, the page is re-checked and the conflict is rewritten, not labelled a correction of an earlier lie.

The Three Kinds of Change and How Each Is Marked

The three kinds of change are error, update, and clarification, and each is marked with a distinct label in the log. An error is marked as a correction and states the wrong fact and the right fact. An update is marked as an update and states what was added or refreshed, such as a new platform or a changed source. A clarification is marked as a clarification and states what wording was sharpened without changing the underlying fact. The labels are plain words, not symbols, so they read clearly in English and do not rely on colour or icons.

An error mark includes the date, the old wording, the new wording, and the reason. An update mark includes the date, what changed, and the source or trigger for the change. A clarification mark includes the date and the sentence that was clarified, with a note on what ambiguity was removed. For example, if we clarified that one pip for gold is 0.01 and that one standard lot is 100 oz, that is a clarification if the facts were already right but the sentence was vague. If we had said one pip was 0.1, that would be an error. The mark tells the reader which happened.

The marks are applied consistently across the page so a reader can scan the log and see the pattern. They are not used to soften a correction: an error is never marked as a clarification to avoid admitting a mistake. They are also not used to inflate updates: a routine refresh is not marked as an error. This discipline keeps the log meaningful. For a page about gold (XAU/USD), where a small wording change can alter how a reader calculates margin, the difference between clarification and correction is worth marking carefully.

What Counts as an Error Worth Logging on the Corrections Page

An error worth logging is a factual statement on the page that is wrong in a way that could change a reader's decision or understanding. That includes a wrong number, a wrong formula, a wrong instrument specification such as lot size or pip value for XAU/USD, a wrong regulator name, a wrong funding method, or a wrong platform name. It does not include a difference of opinion, a change in market conditions, or a typo that does not alter meaning. The test is simple: if a reasonable reader acting on the statement would be misled about gold trading mechanics, costs, or risk, it is an error.

An error worth logging also includes a statement that was true when written but is now false because a named source changed, and the page did not flag the change. For example, if a broker's entity serving Nigeria changes, or the leverage cap available to Nigerian clients changes, the old statement becomes an error of omission if left unmarked. The correction log records that the page previously stated the old fact and now states the new one, with the date the change was confirmed. A statement that depends on an unverified review, such as conflicting leverage caps, is not logged as an error unless we presented it as settled fact.

Finally, an error worth logging is one that affects the page's core promises: accuracy, honesty about risk, and clarity about what is known versus unknown. A misspelling of a platform name like cTrader is logged because it affects search and trust; a clumsy sentence that still conveys the right meaning is not. We do not log every edit. We log edits that correct a wrong fact, restore a missing caveat, or fix a number that a reader could act on. That keeps the log useful and short enough to read.

Why the Correction Log Stays Public on This Page

The correction log stays public because a reader cannot judge the reliability of a page about gold trading risk without seeing what has changed and why. Hiding corrections would let us appear more consistent than we are, which is a form of misleading. The log is part of the page, not a separate archive, so a reader who lands on the page sees the history without searching. This is especially important for facts that affect money, such as margin at a given leverage or the regulator caveat for Nigeria. A public log lets a reader check whether a statement was corrected before or after they acted on it.

A public log also keeps us accountable to the sources we cite. If we say FxPro is licensed by the FCA, CySEC, and FSCA, and later a reader finds that the entity serving Nigeria is FxPro Markets Direct Costa Rica Latam SRL, the log shows when we learned that and what we changed. It prevents quiet edits that would make the page look as if it always said the right thing. For a site aimed at Nigerian readers, where bank transfer and card funding are common, trust depends on being able to see the trail. The log is that trail.

Finally, a public log is useful to readers who want to learn how to check a broker or a fact themselves. Seeing that we corrected a leverage figure, or that we flagged conflicting caps as unverified, teaches the reader what to look for. It also reduces repeated reports: a reader can see that an issue was already logged and dated. The log does not need to be long, but it must be visible and specific. That is why it stays on the page rather than in an internal file.

The Difference Between a Correction and an Update on a Gold Trading Page

A correction fixes something that was wrong; an update adds or refreshes something that was right but is now incomplete or out of date. If the page said one standard lot of gold equals 100 oz and that was correct, changing it would be an error to correct. If the page said the maximum leverage available in Nigeria is up to 1:200 via an offshore entity, and a later review cites conflicting 1:30 or 1:20 caps, that is not a correction of a wrong number; it is an update to reflect a conflict we cannot resolve. The distinction matters because corrections admit fault, while updates admit change.

An update is recorded when a source changes, when a new platform or funding method becomes relevant, or when a caveat needs to be sharpened. For example, adding a note that FxPro is licensed by the FCA, CySEC, and FSCA but that readers should confirm any broker on the SEC Nigeria register is an update if the caveat was missing, not a correction of a false statement. An update is dated and described, but it does not use the language of error. It says what was added or refreshed and why. This keeps the log honest about the difference between being wrong and being incomplete.

The practical test is whether the old statement misled a reader at the time it was published. If it did, it is a correction. If it was accurate but later became insufficient, it is an update. A change in a broker's entity serving Nigeria, from one legal name to another, is an update if the old name was correct when written. A wrong regulator name is a correction. We mark them differently so readers can judge the page's reliability over time without assuming every change is a fix for a mistake.

How a Correction Is Recorded and Dated on This Page

A correction is recorded as a dated entry that states what the page said before, what it says now, and the source or reason for the change. The date is the date the correction was published, not the date the error was first made or first reported. Each entry sits next to the corrected text or in a visible log on the page, so a reader does not have to hunt for it. The entry uses plain language and avoids blame. It names the specific fact changed, such as a leverage figure or a regulator caveat, and it keeps the old wording visible so the history is honest.

The date is recorded in full, with day, month, and year, and it is not backdated to make the page look cleaner. If a correction takes three days to verify, the date is the third day, and the entry may note that verification was pending. For facts that depend on a source, such as the FCA, CySEC, or FSCA licence status of FxPro, the entry names the source checked and the date it was checked. For facts that depend on a review we could not verify, such as conflicting leverage caps, the entry says so rather than picking a number. That way the date marks a real act of checking, not a cosmetic edit.

A correction is also recorded with a stable identifier, such as a short entry number, so readers can refer to it without ambiguity. The identifier does not change if the page is later updated again; a new entry is added instead. This matters for a page about gold (XAU/USD), where a wrong pip value or lot size can mislead a reader about margin. The record is kept in the same place as the page, not in a separate document that can drift. If the page is translated or reformatted, the correction record travels with it.

FAQ

Common questions

How do I report a mistake on a page?

Report it through the contact form, quoting the page address and the exact sentence, and say what you believe is wrong. A correction is easier to make when the error is a checkable fact, such as a wrong contract size, a wrong pip value or a figure that does not follow from the stated inputs.

What happens after I flag an error?

The desk re-checks the sentence against its source, and if the error is confirmed the page is amended and the change is noted. If the sentence turns out to be correct but unclear, it is rewritten rather than removed. If it cannot be verified either way, it is labelled as unverified instead of being left as a plain claim.

Do you correct worked examples and calculator inputs?

Yes. Worked examples are corrected when the arithmetic does not follow from the stated inputs, since gold is fixed at 100 oz per standard lot and one pip at 0.01. If a margin, pip value or profit figure is wrong, it is recalculated from those inputs and the corrected number replaces it on the page.

Will you remove a page just because someone disagrees with it?

No. A page is changed when a fact is shown to be wrong, not when a reader disagrees with the conclusion. Disagreement about risk framing or about a broker is not itself an error. Where the desk cannot verify a claim, it says so on the page rather than deleting the surrounding explanation.

How are corrections to broker information handled?

Broker information is corrected only against what the broker publishes, and the regulator sentence is kept exactly as written: FxPro is licensed by the FCA (UK), CySEC and FSCA; confirm any broker on the SEC Nigeria register of capital market operators. Unverified items, such as the conflicting leverage caps, stay flagged as unverified.