Corrections and how to report one

Errors are fixed in place, with a date

When we get a fact wrong, we correct it in place and add a dated note saying what was wrong and what it now says. We do not quietly rewrite a page and pretend the earlier version never existed, because a reader who acted on the old figure deserves to see that it changed. The note stays with the page rather than being filed away somewhere else.

The date on the note is the date of the fix, and the page's checked date is updated at the same time. If a correction changes the substance of a ranking, we say so in the note rather than letting the ranking shift without explanation. A correction that would embarrass the desk is still published, because the alternative is a site a reader cannot audit.

Correction versus update: how the two differ in practice

A correction fixes something that was wrong; an update changes something that was right but is no longer current. If the page said a 0.10-lot gold position needs about $85.50 margin at the stated cap and that arithmetic was mistaken, fixing it is a correction. If the page correctly described the available leverage cap and that cap later changed, revising the page is an update. The distinction matters because a correction admits fault, while an update simply keeps pace with reality. Readers deserve to know which one they are looking at.

Updates are dated the same way but are not framed as errors. When a source changes, the page is revised and the change is noted as an update with its date, without implying the previous wording was false at the time it was written. For example, if a review cited 1:30 or 1:20 caps and that conflicting information is later resolved, the page is updated to reflect the resolution and the note says so. We do not label that a correction because the earlier text accurately reported a conflict that existed. The label follows the nature of the change, not the convenience of the editor.

The practical test is simple: could the original sentence have been defended on the day it was published using the sources then available? If yes, the change is an update. If no, it is a correction. This test keeps us from quietly reclassifying mistakes as updates to soften them. It also stops us from calling every source revision a correction, which would overstate how often we get things wrong. Both labels carry a date, and both stay on the page permanently.

Why the correction log stays visible to every reader

The log stays public because a trading page that hides its mistakes is asking readers to trust numbers they cannot verify. Gold trading involves real money, and a Nigerian reader sizing a position or checking the SEC Nigeria caveat needs to know whether a figure was recently changed. A visible log lets that reader see the page's history without asking anyone. It also creates a record that we cannot quietly rewrite, which is the point. Trust here is built from what is shown, not from what is claimed.

A public log also protects against the slow drift that affects financial content. Numbers such as the reference price of 4275.0 or the margin example of about $85.50 can become misleading if surrounding text is edited without notice. When every change is logged and dated, drift becomes visible and correctable. Readers can compare what the page says now with what it said before and judge for themselves whether the revision was justified. That scrutiny is useful, not threatening, because it forces precision in a domain where vague wording causes real losses.

Keeping the log public is also a discipline on the writing itself. Knowing that a change will be dated and shown discourages casual edits and encourages checking a source before publishing a number. It makes the page slower to change and faster to correct, which is the right trade-off for high-risk material. We do not publish the log to perform transparency; we publish it because a reader who cannot see the history has no way to tell a careful page from a careless one. The log is the difference made visible.

The three change types and the mark each one carries

Every change on the page is marked as one of three types: error, update, or clarification. An error mark means the previous text was wrong and has been replaced, with the date of replacement shown beside the corrected passage. An update mark means the previous text was accurate when written but the underlying fact has moved, and the date of revision is shown the same way. A clarification mark means the original wording was not wrong but could be misread, and the revised wording is dated so readers can see it changed without implying a mistake.

The marks are applied by the editor making the change, and the choice of mark is itself reviewable. If a reader disputes whether something was an error or a clarification, the dispute is logged and the mark can be changed, with the change of mark also dated. We do not use colour, icons, or symbols to carry the meaning, because plain text survives copying and translation better. The word error, update, or clarification appears in the note itself, followed by the date. A reader scanning the page can tell at a glance which kind of change they are looking at.

The three marks are not interchangeable, and we do not downgrade an error to a clarification to make the page look cleaner. Nor do we upgrade an update to an error to appear more rigorous. The mark must match what actually happened. For local details such as the SEC Nigeria caveat or the list of accepted funding methods, a missing caveat is an error, a changed regulator wording is an update, and ambiguous phrasing about the register is a clarification. The label follows the facts of the change, not the impression it creates.

A change in conditions is a re-check, not an error

If a broker changes its own terms after we checked, the page was not wrong when it was written, so the fix is a re-check rather than a correction. A new leverage cap, a new funding route or a new entity serving Nigeria falls into this category. We update the page and move the checked date forward, and the correction note is not used because no error was made.

The distinction matters because it tells a reader what kind of problem they found. An error means the desk misread a document; a re-check means the world moved. Both are worth reporting, and both go to the same mailbox, but only the first gets a correction note. Where we cannot tell which has happened, we say so on the page rather than guess.

When a cited source changes without saying so

When a source changes silently, the page is re-checked against the source's current content and the difference is logged as an update, not an error, provided the page accurately reflected the source at the time of writing. The old wording is not restored and the source is not accused of wrongdoing in the note. Instead, the note states that the source changed and the page now follows the current version, with the date of the re-check. This keeps the page aligned with reality without pretending the earlier text was a mistake.

Silent source changes are the hardest case because there is no announcement to point to. Where a source that previously cited conflicting leverage caps, such as 1:30 or 1:20, later settles on one position, the page is updated to reflect the settled position and the note records that the earlier conflict was reported as found. We do not invent a resolution date for the source; we date our own re-check. If the source becomes unavailable entirely, the page says so and marks the affected passage as unverified rather than leaving a stale number standing as if it were current.

The rule is that our credibility depends on following the source, not on defending an earlier sentence. If a silent change makes an earlier statement wrong in hindsight, we still mark it as an update if it was accurate when written, because the fault lies with the source's silence, not with our reporting. But we do not use that reasoning to avoid re-checking. A source that changes silently is a reason to check more often, and the log shows the pattern. Readers can see how often a given source has moved and judge the page accordingly.

Why no correction, update, or clarification is ever deleted

Nothing is deleted because a deleted correction is indistinguishable from a page that never had a problem, and that ambiguity is exactly what a public log exists to prevent. When a passage is corrected, the old wording is removed from the body but its correction note and date remain in the page history. When an update supersedes an earlier update, both remain visible in sequence. The current page shows only the current text, but the history shows every change and its mark. A reader can therefore reconstruct what the page said at any point without relying on our summary.

Deletion would also make the log useless as a check on the editors. If a wrong margin figure or a misstated regulator caveat could be removed after the fact, the incentive to publish carefully would weaken. Keeping every entry means a mistake stays attached to the page that made it, which is a real cost and therefore a real discipline. We accept that cost because the alternative, a page that looks flawless because its flaws were erased, misleads readers about how financial content is actually produced.

The one exception is not a deletion but a redaction: if a correction note itself contained personal data or a security-sensitive detail, that detail is removed while the fact and date of the change remain. We do not otherwise shorten, merge, or tidy the history to make it read better. A long log is not a shameful thing on a page about gold trading, where numbers matter and sources move. It is evidence that the page has been maintained. Readers in Nigeria checking local funding or the SEC Nigeria caveat can see every revision that touched those passages.

How a correction is recorded and dated on the page

A correction is recorded by editing the sentence in place and attaching the date the edit was made, not the date the error was first noticed. The dated note sits next to the corrected passage so a reader sees both the current wording and the fact that it changed. We do not backdate a correction to the original publication date, and we do not leave the old wording visible in the body. The date is the calendar date of the fix, written in full, and it stays with the passage permanently.

The record also states what was wrong in plain terms, without reproducing the incorrect number as if it were still valid. For example, a note might say the margin example for a 0.10-lot gold position was corrected to about $85.50 at the stated leverage cap, rather than repeating a wrong figure. This keeps the page accurate for readers who arrive after the fix while still being honest that a change happened. The note is short, specific, and placed where the error was, so it cannot be missed by someone reading the section.

Dating is tied to the page's visible history, not to an internal ticket. If a correction is made on a Monday but the page history is only refreshed later, the note carries the Monday date and the history entry matches it. We do not use vague labels such as recently corrected. A reader in Nigeria checking a naira example or the SEC Nigeria caveat should be able to see exactly when that sentence last changed. If the date cannot be shown, the correction is not considered complete.

How to report one

To report an error, write to editor@enugucopyng.com with the page address, the sentence you believe is wrong, and the source that shows the correct position. The strongest reports cite the broker's own document and the date it was read, because that is the standard we hold ourselves to. A screenshot or a link to the relevant clause helps more than a general complaint.

We do not promise a response time in hours or days, and we do not promise that every report leads to a change. What we do promise is that a report with a document behind it is read and checked against the source. If the report is right, the page is fixed with a dated note; if it is not, the page stands and we will say why.

Who makes the call on a change and how quickly it is made

The decision on whether a reported issue is an error, an update, or a clarification rests with the editor responsible for the page, not with the person who reported it and not with an automated check. That editor compares the sentence, the number, and the cited source, then applies one of the three marks and dates it. The editor does not need approval to correct a clear factual error. Where the source itself is ambiguous, the editor records the ambiguity rather than forcing a label. The call is a judgement, and it is made in the open because the mark and date are visible.

The time frame depends on the severity and the evidence, not on a fixed promise we cannot keep. A clear numerical error, such as a wrong pip value or a margin figure that contradicts the stated cap, is treated as urgent and corrected as soon as it is confirmed. A disputed interpretation or a source that is itself unclear takes longer because it requires checking before changing. We do not publish a response deadline we cannot meet, and we do not leave a confirmed error standing while a broader review is arranged. Confirmation triggers the fix.

When the editor and the reporter disagree, the page shows the current wording with its mark and date, and the disagreement is noted in the log rather than hidden. The editor's call can be reversed later if new evidence appears, and a reversal is itself dated. This means no single person has the final word forever, but someone always has the responsibility now. For Nigerian readers checking local details, the relevant editor is the one accountable for the page, and the visible mark is the evidence that a decision was actually made rather than deferred.

What qualifies as a loggable error on a gold trading page

A loggable error is any statement on the page that is factually wrong, internally inconsistent, or contradicted by the source it cites. For gold (XAU/USD) content, that includes a wrong pip value, a mistaken lot size (1 lot = 100 oz), an incorrect margin figure such as the $85.50 needed for a 0.10-lot position at the stated cap, or a regulator reference that names the wrong authority. It also covers a broken formula, a currency symbol misapplied, or a claim that a cost is a fixed number when no number was supplied. Matters of opinion, style, or emphasis are not errors.

An error must be reproducible from the page itself or from the cited source, not from memory. If a reader believes the reference price of 4275.0 is stale, that is not automatically an error because prices move; it becomes loggable only if the page presents the figure as current when the timestamp shows otherwise, or if the arithmetic built on it no longer holds. The test is whether a careful reader can point to the exact sentence, the exact number, and the exact source that conflicts. If that chain cannot be shown, the item is logged as a query rather than a correction.

Errors in locally sensitive details count, especially around funding and regulation for Nigerian readers. If the page names a funding method that is not on the approved list (local NGN bank transfers, Visa/Mastercard debit cards, e-payments, crypto), or states a leverage ratio other than the cap given, that is loggable. The same applies to the SEC Nigeria caveat: if the wording drops the instruction to confirm any broker on the SEC Nigeria register of capital market operators, it is an error. We do not log disagreements with a source's opinion, only failures of fact, consistency, or required caveats.

How a reader can trace the full history of a page

A reader can trace the history by opening the page's change log, which lists every correction, update, and clarification in date order with the mark applied to each. The log is separate from the body so the current text stays readable, but every entry points to the passage it affected. The date on each entry matches the date shown beside the corrected passage in the body. A reader who wants to know whether a specific number, such as the $85.50 margin example or the 4275.0 reference price, has ever changed can search the log for that figure and see every entry that mentions it.

The log also shows the sequence of marks, so a reader can see whether a passage was first clarified and later corrected, or updated twice as a source moved. That sequence is more informative than a single latest date because it reveals how stable the underlying fact has been. We do not compress the sequence into a summary that hides the order. If a reader finds a discrepancy between the body and the log, the log is the authority on what changed and when, and the body is the authority on what the page currently asserts. Both are needed to check the page properly.

Checking the history requires no account and no request to the editors. The log is part of the page, not a document released on application. That matters for a Nigerian reader who may be comparing the page against the SEC Nigeria register or against a broker's own materials and wants to know which version of our text they are reading. If a passage has no log entry, it has not changed since publication. If it has entries, their dates and marks tell the reader exactly how much weight to give the current wording.