Corrections and How to Report an Error

How a correction is made

A correction is made in place: the wrong text is replaced and a dated note says what changed and when. The page is not silently rewritten and the old wording is not quietly deleted, because a reader who relied on the earlier version deserves to see that it moved. The date on the note is the date the fix was made, not the date the original was written.

The same rule applies to figures taken from a broker's documents. If a leverage cap, a funding method list or a margin example was recorded on one date and the broker later publishes something different, the page is updated and the note says both what was read before and what is read now. The desk does not guess which version is right; it records what the document said on each date.

Correction Versus Update: Where the Line Sits

A correction fixes something that was wrong; an update changes something that was right when written but has since stopped being true. If the page said a broker was supervised by one set of authorities and that was accurate on the day, and the position later changed, replacing it is an update, not a correction. If the page named the wrong authority from the start, that is a correction. The distinction is not pedantry: it tells a reader whether to distrust the earlier version or simply to note that time has passed. Both are logged; they are not logged as the same thing.

The line matters most with regulatory detail, which is exactly where readers in Nigeria need clarity. The standing caveat on this site is that FxPro is licensed by the FCA (UK), CySEC and FSCA, and that any broker should be confirmed on the SEC Nigeria register of capital market operators. If that sentence were ever misattributed, it would be corrected. If the register itself were reorganised and the instruction needed rewording to stay accurate, that would be an update. Readers deserve to know which of the two happened.

In practice, an update is triggered by an external change and a correction by an internal mistake, and the log entry says which. A correction also carries a short acknowledgement that the earlier text was wrong, without dressing it up. An update does not apologise, because nothing was done badly. Keeping the two categories separate stops the log from becoming a place where mistakes hide inside routine maintenance, and it stops routine maintenance from looking like an admission. The label is part of the record, not an afterthought.

Why the Correction Log Stays Public and Permanent

The log stays public because a reader cannot judge a number without knowing its history, and a private log gives them no way to do that. Trading content is used to size positions and move money, so the difference between a figure that has been checked and one that has quietly drifted is material. Publishing the record also removes the temptation to smooth over a mistake by editing silently: if every change is visible, the cheapest path is to describe it accurately. A public log is a commitment device as much as a service.

Permanence is the other half. Entries are not removed when they become old or unflattering, because an expired correction is still evidence of how the page was maintained. A reader who wants to know whether this site fixes things promptly can count the entries and read the gaps between report and fix. That is only possible if nothing is pruned. For a Nigeria-facing page dealing in naira funding, bank transfers, cards and crypto, where a reader may be deciding how to move real money, a visible maintenance record is a fair thing to ask of the publisher.

Public also means legible to the person the page is written for, not just to an editor. The log is written in plain English, without internal ticket numbers as the only identifier, and it sits with the page rather than behind a request. No reader should have to email anyone to find out whether a sentence was changed. Where a correction touches risk framing, such as leverage being a cap rather than a target, the entry says so in the same sober terms the page uses, because the log is part of the teaching, not a legal annex.

What Counts as an Error Worth Logging on This Page

An error worth logging is a statement on the page that is wrong on the facts, wrong on the arithmetic, or wrong on the attribution, and that a reader could act on to their cost. A wrong margin figure in a gold worked example, a pip value stated as 1.00 instead of 0.01, a regulation caveat that names the wrong authority, or a funding method attributed to a broker that does not offer it all qualify. A typo that changes no meaning does not. The test is whether a careful reader following the page could be misled about money, risk or who supervises the firm.

A logged error must be specific and locatable, not a general disagreement with tone or emphasis. Pointing at a single sentence, a number, a table cell or a named entity is what makes a report actionable; saying the page feels wrong about leverage gives an editor nothing to verify. The distinction matters because this site covers gold (XAU/USD) trading, where a mis-stated lot size of 100 oz or a margin figure tied to a leverage cap can change a reader's position sizing in naira terms. Precision in the report is what allows a precise fix.

Genuine errors include stale regulator detail, an incorrect platform list, and any figure presented as fixed when the underlying input is variable. If a page states a margin requirement without saying which leverage cap produced it, that is an error of omission worth logging, because the same 0.10-lot gold position needs about $85.50 margin only under the 1:200 offshore cap and a different figure under another. Anything that hides its own assumption from the reader belongs in the log. Style preferences, headline wording and layout do not.

How a Correction Is Recorded and Dated on the Page

A correction is recorded as a dated entry that states what the page said, what it now says, and the reason for the change, kept alongside the page rather than buried in a changelog nobody opens. The date attached is the date the corrected version went live, not the date the report arrived and not the date an editor first looked at it. That single rule keeps the record honest, because it ties the timestamp to the version a reader can actually see. Where the original wording matters, it is quoted so the change is legible without guesswork.

Each entry carries the section it touches, so a reader can match the note to the sentence they are reading. For a page like this one, an entry might read that the margin example was tied explicitly to the 1:200 offshore cap after the earlier text left the leverage assumption unstated. Entries are written in plain English, in the same voice as the page, and avoid internal jargon. The point is not to perform transparency but to let a Nigerian reader confirm, in seconds, whether the number in front of them is the corrected one.

Dating also covers the source, not just the page. If a correction rests on a regulator register check or a broker's own documentation, the entry notes when that check was made, because a fact that was true in March can be false by September. This is why the log shows dates rather than version numbers alone: a reader in Lagos comparing two printouts needs to know which came later. Where a figure is approximate, as with the reference gold price near 4275.0, the entry says so rather than implying a precision the page does not have.

How to report an error

Report an error by writing to editor@ileshaingotng.com and naming the page and the sentence. If you can, include the broker's own document or a link to the page where the correct figure appears, with the date you saw it. That lets the desk compare the two readings instead of arguing about memory.

Useful reports are specific: a wrong lot size, a pip value stated incorrectly, a funding method listed that the broker does not offer to Nigeria, or a regulator statement that does not match the source. Vague dissatisfaction is read, but it is hard to act on. A precise note with a source is what gets a page fixed.

What is a re-check, not an error

A condition that merely changed since the check is a re-check, not an error. If a broker dropped a funding method, changed its leverage cap or moved the entity that serves Nigeria after the date on the page, the earlier text was accurate when it was written. It is updated as a re-check with a new date, and it is not logged as a mistake.

The distinction matters because it keeps the record honest. An error means the desk wrote something that was wrong at the time, and that is corrected and noted. A re-check means the world moved, and the page is brought up to date. Both are dated, and both are visible to the reader.

How Error, Update and Clarification Are Marked Differently

Each change carries one of three labels, and the label is chosen before the edit is written, not after. Error means the page was wrong and is now right. Update means the page was right and external facts moved. Clarification means the page was accurate but a reasonable reader could misread it, so wording or an added assumption now removes the ambiguity. The three are marked in the log with their own label and their own short entry, so a reader scanning the history can tell at a glance whether trust in the earlier text was misplaced or merely overtaken.

A clarification is the most easily abused of the three, so it is held to a test: if the original sentence could have led a careful reader to a wrong action, it is a clarification and not an error only when the underlying fact was correct. For example, a margin example showing about $85.50 for a 0.10-lot gold position that failed to name the 1:200 offshore cap would be clarified by naming the cap, because the arithmetic was sound but the assumption was hidden. If the arithmetic itself were wrong, the same sentence would be logged as an error.

Marking is consistent across the site so the labels mean the same thing on every page. An error entry names what was wrong. An update entry names what changed externally and when it was confirmed. A clarification entry names the misreading it prevents. None of the three is merged into another to tidy the count, and none is left unlabelled. A reader comparing this page with another on the site should find the same vocabulary doing the same work, which is the only way the labels carry information rather than decoration.

Who Decides on a Change, and the Clock It Runs On

A single editor with responsibility for the page decides, and the decision is made within a stated turnaround from the moment a report is logged. The turnaround is counted in working days and is published with the log so a reader can hold the page to it, rather than being told vaguely that reports are reviewed. The editor's job is to establish three things: whether the claim is wrong, what the correct statement is, and which of the three labels applies. Reports that cannot be verified against a source are not actioned as errors, and the log says why.

Time is split between acknowledgement and resolution, because they are different promises. Acknowledgement confirms the report was received and logged; resolution confirms the page has been changed or the report closed with a reason. Splitting them stops a slow verification from looking like silence. Where verification depends on an external register or a broker's own documentation, the clock reflects that dependency and the entry states what is still outstanding. A reader is never left guessing whether a report vanished or is simply mid-check.

The editor also decides when not to change the page, and that decision is recorded too. A closed report with no change is still an entry, because a reader who raised it deserves to see the outcome and the reasoning. This matters where a claim is contested: leverage availability for Nigerian clients has been described inconsistently across reviews, and where the site cannot verify a figure it says so rather than picking one. The clock runs on the decision, not on certainty, and an unresolved question is logged as unresolved.