Corrections policy

How an error is fixed

When a published fact is wrong, the page is corrected in place and a dated note records what was changed. The old wording is not quietly swapped out, because a reader who relied on it deserves to see the edit. The note stays on the page rather than being removed later.

This matters most with figures that carry a date, such as a leverage term or a contract specification read from a broker document. If the document said one thing when it was read and the page said another, that is an error and it is corrected with the date it was found.

How a reader can check the history of this page

A reader checks the history by opening the correction log on the page and reading it from the most recent entry backwards. Each entry gives the date, the label (error, update or clarification), the section, the before text and the after text. To check a specific sentence, search the log for a distinctive phrase from that sentence; the entry will show whether it was corrected, updated or clarified, and when. This works for the naira amounts, the gold lot size of 100 oz, the pip value of 0.01 and the SEC Nigeria caveat, because each is quoted in the entry that changed it.

The log is ordered by date, with the newest first, so a reader can see the current state of the page at the top and the earliest state at the bottom. A reader who wants the page as it stood on a past date reads the entries above that date and applies them in reverse; the before text of each entry gives the earlier wording. This is why the before text is quoted rather than summarised: it lets a reader reconstruct the earlier sentence without needing an archive of the whole page. The method is manual but exact.

A reader who cannot find an entry for a sentence they believe is wrong should report it using the reporting route already on the page, naming the section and the fact it conflicts with. The absence of an entry is itself information: it means the sentence has not been logged as an error, update or clarification, not that it has been cleared. The reviewer then decides within the time target above. The reader can check back for the entry, which will appear with its own date if the report is loggable.

Why the correction log stays public on this page

The correction log stays public because a trading page that hides its fixes is asking readers to trust it without evidence. Gold (XAU/USD) is a high-risk instrument, and a wrong lot size, a wrong pip value of 0.01, or a missing leverage caveat can change a reader's risk calculation. A public log lets a Nigerian reader see whether a naira figure or a regulator statement was corrected, and when. It also lets a reader check whether the page has a pattern of the same defect. That check is the point; a private log would defeat it.

A public log also keeps the editorial rule honest. The rule against praising a spread or cost without a given number is only credible if a breach is visible and dated. If a sentence once called a cost competitive and was later stripped, the log should show that correction rather than the sentence quietly disappearing. The same applies to the regulator caveat: if the SEC Nigeria register wording was ever wrong, the fix should be on the record. Publicness turns an internal standard into something a reader can audit.

The log is kept short and specific so that publishing it does not become a second, competing article. It lists date, section, type and the changed sentence, not a narrative. It does not name individual authors, because the facts list does not give us author names and inventing them would breach the grounded-facts rule. It does not include promotional material or bonuses, because none are given. What remains is a factual trail that supports the page rather than distracting from it.

How a correction is recorded and dated on the page

A correction is recorded as a dated entry in the page's public correction log, with the date the correction was made, the section affected, the before text and the after text. The date is the date of publication of the fix, not the date the error was first reported, and both can appear if they differ. Each entry carries a short reason: factual error, internal inconsistency, missing required caveat, or unsupported claim. That reason maps to the three change types below. The entry stays on the page permanently, so a reader can see what changed and when without asking.

The dating convention is calendar date in plain text, with no relative wording such as recently or last week. If a correction is itself corrected, the new entry is added above the old one and the old one is not edited; the chain shows the sequence. For figures, the entry names the figure and its context: for example, the worked margin figure of about $85.50 for a 0.10-lot gold position at 1:200 via the offshore entity is recorded with that leverage context, not as a standalone number. This prevents a later reader from treating a contextual figure as a universal one.

The record is kept on the same page as the content it corrects, not in a separate document that can drift. That placement matters for a Nigerian reader checking a naira amount or the SEC Nigeria caveat: the correction sits beside the sentence it fixes. The log entry does not restate the whole section; it quotes only the changed sentence and the replacement. The result is a short, auditable trail that a reader can scan in under a minute and that a reviewer can check against the facts list.

Who decides a correction and within what time on this page

The decision to log a correction rests with the page's editorial reviewer, who checks the report against the facts list and the editorial rules. The reviewer decides whether the report is an error, an update or a clarification, and whether it is loggable at all. The time target is to decide within two working days of a report reaching the review queue, and to publish a loggable correction within five working days of that decision. These are internal targets, not guarantees to readers, and they depend on the report containing enough detail to locate the sentence and the supporting fact.

A report that does not identify the section, the sentence or the fact it conflicts with is returned for detail before a decision is made, and that return stops the clock. A report about a figure that is contextual, such as the about $85.50 margin for a 0.10-lot gold position at 1:200 via the offshore entity, must say which context is missing or wrong; otherwise the reviewer cannot tell a defect from a preference. The reviewer does not decide on tone, style or scope, and a report on those is closed as not loggable with a one-line reason.

The reviewer also decides when a source itself has changed, which is covered separately below. If the reviewer is unsure whether a sentence was defensible at publication, the default is to treat it as an error and log it, because a visible correction is safer than a silent judgement call. The reviewer does not name a person in the log, and does not state a date that was not given. The decision and its date are recorded in the log entry itself, so the process is checkable after the fact.

A change is not always an error

A condition that merely changed since the check is a re-check, not an error. If a broker altered its leverage terms, funding route or entity after the date a page was read, the old page was accurate when written. The fix is to re-read the source and update the page with a new date.

The distinction is kept because it tells a reader something useful. A dated note saying the broker changed its terms is different from a note saying the desk got it wrong, and only the second one is a correction.

Why nothing is deleted from the page or its log

Nothing is deleted because deletion destroys the evidence a reader needs to judge the page. If a wrong leverage statement or a misnamed funding method is removed without a trace, a reader cannot tell whether the page was ever wrong, how long it was wrong, or whether the same defect recurs. Keeping the entry, dated and labelled, preserves that evidence. It also stops a correction from becoming a quiet rewrite, which is the failure mode a public log is meant to prevent. Deletion is therefore treated as a defect in itself.

Nothing is deleted from the content either, in the sense that a corrected sentence is replaced in place but its before text is preserved in the log entry. That way the live page reads cleanly while the history remains complete. A reader who wants the old sentence can find it in the log, quoted, with the date and the reason. The same applies to a clarification: the ambiguous sentence is quoted in the entry and the added sentence sits beside it on the page. The pair is the record.

The no-deletion rule has one boundary: material that breaches the grounded-facts rule, such as an invented spread, commission, swap, minimum deposit, bonus or author name, is removed from the live page and recorded in the log as an error entry with the removed text quoted. That is not a contradiction; the log preserves the fact of the removal while the live page stops asserting something unsupported. The entry explains the removal, so the reader sees both the breach and the fix. Nothing vanishes without a dated trace.

What we do when a source itself changes silently

When a source changes silently, we treat the page's earlier sentence as correct at the time it was written and add an update entry rather than an error entry. A silent source change means the underlying reference moved without a public notice we can cite, so the earlier text was not wrong against what was available then. The update entry states the new position and the fact that the source changed without notice, and it does not claim the earlier text was an error. This keeps the log honest about what was knowable and when.

The practical case on this page is leverage. The facts list records up to 1:200 via the offshore entity, and notes that one review cited 1:30 or 1:20 caps, which is conflicting and not verified at review. If that conflict resolves later, the page is updated, not corrected, because the earlier text already carried the conflict. The same applies to the regulator caveat: if the SEC Nigeria register wording changes, the page is updated to the new wording and the update entry says the change came from the source, not from an earlier mistake.

A silent source change does not erase the earlier entry. The update is added above it, and the earlier entry stays visible with its original date. If the silent change makes an earlier number impossible to defend, the reviewer may add both an update and a clarification, but never a retroactive error label. The rule is that the log records what was known and when, not a cleaned-up version of history. That is what lets a reader reconstruct the page's state at any past date.

How to report one

Report an error by writing to editor@ibadanaccountng.com with the page, the sentence and the source you are relying on. A link to the broker's own document, with the date you read it, is the most useful thing you can send. You do not need an account or any other details.

Every report is read. If it is an error, the page is fixed and a dated note is added. If it is not, the reply explains why the published wording stands, and points to the source it came from.

How error, update and clarification are marked in the log

Every log entry is marked with exactly one of three labels: error, update or clarification. An error entry means the earlier text was wrong against the facts list or the editorial rules, and it shows the before and after text. An update entry means the earlier text was not wrong but is now revised for currency or completeness, and it shows what was added or changed. A clarification entry means the earlier text was correct but ambiguous, and it shows the added sentence that removes the ambiguity. The label is the first word of the entry, so a reader can sort by type at a glance.

The marking is deliberately rigid. An error entry cannot be relabelled as a clarification later, because that would hide the admission; if the fix itself was wrong, a new error entry is added above it. An update entry cannot be used to smuggle in a correction, because the test is whether the earlier sentence was defensible when written. A clarification entry must add text, not replace it, unless the replacement is purely a rewording with the same meaning. These constraints keep the three labels from collapsing into one vague changed label.

The label also determines what the entry must contain. Error entries must quote the defective sentence and the replacement. Update entries must state the new information and why it was not available before. Clarification entries must quote the ambiguous sentence and the added clarifying sentence. None of the three may state a spread, commission, swap or minimum deposit as a number, because those are not in the facts list. A label without its required content is treated as an incomplete entry and is finished before publication.

What counts as an error worth logging on this page

An error worth logging is any statement on this page that is factually wrong, internally inconsistent, or unsupported by the facts we are allowed to use. That includes a wrong instrument code, a wrong lot size for gold (XAU/USD) where 1 standard lot is 100 oz, a wrong pip value of 0.01, a naira figure that does not match the stated source, or a regulator caveat that misnames the SEC Nigeria register. A typo that changes meaning counts; a typo that does not change meaning does not. The test is simple: would a reader acting on this sentence make a different decision than the facts allow? If yes, it is an error worth logging.

An error worth logging also covers a missing caveat that the facts require. If a paragraph states leverage without saying it is a cap rather than a setting to aim at, or states a funding method that is not on the approved list (local NGN bank transfers, Visa or Mastercard debit cards, e-payments, crypto), that omission is loggable. The same applies to any sentence that praises a spread, fee or commission without a given number, because that is an unsupported claim by our own rule. The log exists so these are visible, dated and fixed, not quietly smoothed over.

An error worth logging is not a difference of opinion about style, tone or emphasis. If a reader prefers a shorter sentence or a different example, that is feedback, not an error. If a reader believes the page should mention a broker we do not cover, that is a scope request, not an error. Keeping the log to factual and rule-based defects is what makes it useful; if everything is an error, nothing is. The standard is the facts list and the editorial rules, not preference.

The difference between a correction and an update on this page

A correction fixes something that was wrong when it was published; an update changes something that was right when published but is no longer current or complete. A correction is triggered by a defect against the facts list or the editorial rules. An update is triggered by new information, a new source, or a scope decision, and it does not imply the earlier text was false. The distinction matters because a correction carries an admission and an update carries a revision; mixing them makes the log misleading and makes it harder for a reader to judge how reliable the page has been.

On this page, a correction example is a sentence that named a funding method outside the approved list, or a sentence that treated the 1:200 maximum leverage as a setting to aim at rather than a cap. An update example is adding a clarification that the leverage figure is the maximum available via the offshore entity and that one review cited 1:30 or 1:20 caps, which is conflicting and not verified at review. The update adds context; the correction removes a defect. Both are dated, but only the correction says the earlier text was wrong.

The practical test is whether the earlier sentence could have been defended against the facts list at the time it was written. If it could not, it is a correction. If it could, and the change is about currency, completeness or clarity, it is an update. A reader checking the history should be able to tell which is which from the label alone, without reading the whole entry. That is why the log labels every entry as error, update or clarification and never leaves the type implicit.