Corrections Policy
Errors are fixed in place with a dated note, never quietly deleted, so you can see what changed and when.
How an error is fixed
An error is corrected in place and marked with a dated note that says what was wrong and what it now says. We do not silently overwrite a number, and we do not delete a page to make a mistake disappear.
The dated note stays on the page so a reader who saw the earlier version can see the change. If the correction is substantial, the note explains the reason rather than just recording that an edit happened.
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 at the top of its log entry. An error is marked ERROR and must name the wrong sentence and the right sentence. An update is marked UPDATE and must name the fact that changed and the date it became effective, or say that the date is unknown. A clarification is marked CLARIFICATION and must name the sentence that was ambiguous and the sentence that replaces it, without claiming the old sentence was false. The label is the first word of the entry so a reader scanning the log can sort by kind.
An error is marked with the old and new text side by side, because the point is to show what was wrong. An update is marked with the old fact and the new fact, because the point is to show what moved. A clarification is marked with the old wording and the new wording, because the point is to show that the meaning was always the same but the expression was not clear. A clarification does not get an ERROR label even if a reader misunderstood the old sentence, because a misunderstanding is not proof of a false statement. We say which kind we chose and why in one sentence.
The three marks are not interchangeable, and we do not use CLARIFICATION to avoid admitting an error. If the old sentence stated a number that was wrong, the mark is ERROR regardless of how small the number was. If the old sentence stated a number that was right and the world changed, the mark is UPDATE. If the old sentence stated a number that was right but could be read two ways, the mark is CLARIFICATION. A reader can filter the log by mark, so the count of each kind is visible. We do not delete a mark or change it after publication without a new entry explaining the change of mark.
The Difference Between a Correction and an Update
A correction fixes something that was wrong when we published it; an update changes something that was right then but is different now. If we said one standard lot of gold is 100 oz and that was true, and later the contract specification changes, that is an update. If we said 100 oz and the true figure was always 100 oz but we typed 10 oz, that is a correction. The distinction matters because a correction admits a mistake, while an update tracks a moving world. A reader deciding whether to trust a page needs to know which one they are looking at, because a page with many corrections is a different signal from a page with many updates.
A correction is dated to the day the corrected version goes live and is marked as a correction in the log. An update is dated to the day the new fact became effective, where we can establish that date, and is marked as an update. If we cannot establish when the change happened, we date the update to the day we published it and say so. A correction always names the old and new sentence. An update names the old and new fact but does not call the old fact an error. The two markers are never mixed on the same entry; if a single edit both fixes an error and reflects a change, it is split into two entries.
A correction is not a softer word for an update, and an update is not a way to avoid admitting an error. If we published a leverage figure that was wrong for the entity serving Nigeria at the time, that is a correction even if the figure later became right. If we published a figure that was right and the broker then changed it, that is an update even if the old figure now looks wrong. The test is what was true on the publication date. We apply that test to every entry, and we say which test we applied in the entry itself so a reader can check our reasoning.
Why the Correction Log Stays Public
The correction log stays public because a reader cannot judge the reliability of a page without seeing its mistakes. A page that claims to explain gold trading in naira, margin at 1:200, and the SEC Nigeria caveat is only useful if a reader can see where we got those things wrong and how we fixed them. A private log would let us curate the record. A public log lets a reader compare the page to its history and decide for themselves. The log is linked from every page it affects, not buried in a footer, because a correction that a reader cannot find is not a public correction.
The correction log stays public because the alternative is a page that looks flawless and is therefore less trustworthy. Trading is high-risk, and a reader may act on a margin figure or a pip value with real money. If we hide a corrected margin error, a reader cannot know whether the current figure is the first version or the fifth. The log shows the sequence, so a reader can see whether a figure has been stable or repeatedly fixed. That pattern is information. We do not remove entries when a page is redesigned, and we do not move the log to a new URL without a redirect and a dated note.
The correction log stays public because the regulator caveat we publish asks readers to verify a broker on the SEC Nigeria register, and that same standard applies to us. We ask readers to check a claim against an independent source; we should let them check our claims against our own record. The log is not a marketing page and does not use the words competitive, tight, low, or best about any cost. It states what changed, when, and why. A reader who wants to see every correction to the gold page can filter the log by URL and read the full history without asking us for access.
A changed condition is not an error
A condition that merely changed since we checked is a re-check, not an error. If a broker alters its leverage cap, its funding list or its documents after our reading date, the old figure was accurate when written and the fix is a fresh check with a new date.
We treat those two cases differently on purpose. Calling a changed market condition an error would teach readers to distrust every dated figure, and dating every figure is the only honest way to publish numbers that move.
Who Decides on a Correction and in What Time
The decision on a correction is made by the editor responsible for the page, and the time limit is five working days from the day a report is logged. The editor checks the report against the published source, the page history, and any independent source named on the page, such as the SEC Nigeria register for a broker claim. If the editor cannot decide within five working days, the entry is marked PENDING with the reason and a new date. A PENDING entry is visible in the log, so a reader is not left with a silent delay. The editor who decides is named by role, not by person, to keep the log stable when staff change.
The five-working-day limit applies to the decision, not to the fix. A decision to correct is recorded on the day it is made, and the corrected page goes live within two working days of the decision. If the fix requires a new source or a check with a broker, the editor may extend the fix window once, to a total of ten working days, and must say so in the entry. A decision not to correct is also recorded, with the reason, so a reader can see that the report was considered. We do not leave a report unanswered because the answer is no.
The editor's decision can be appealed by any reader within thirty days of the entry date, and the appeal is decided by a second editor who did not make the first decision. The appeal decision is recorded as a new entry that references the first. The time limit for the appeal decision is ten working days. If the appeal succeeds, the original entry is not deleted; it is marked OVERTURNED and a new entry states the corrected position. This keeps the record complete and shows that the process has a check. The same five-day and ten-day limits apply to the appeal as to the first decision.
How a Correction Is Recorded and Dated
A correction is recorded as a dated entry in the public log with four fields: the page URL, the exact sentence before and after, the reason, and the date the corrected version went live. The date is the publication date of the corrected page, not the date the error was reported and not the date the fix was drafted. If a correction spans several pages, each page gets its own entry with the same reason but its own date. We do not backdate an entry to make the page look cleaner. A reader can sort the log by date and see every change in the order it happened.
A correction is dated in West Africa Time (WAT) because the audience is in Nigeria, and the date appears in the format YYYY-MM-DD to avoid month-name confusion. The log entry also shows the version number of the page before and after, so a reader can match the entry to a specific snapshot. If the correction is made in stages, each stage gets its own date and version. We do not merge two corrections made on different days into one entry. The date is the only field that cannot be edited after publication; if we got the date wrong, that itself becomes a logged correction with its own date.
A correction is recorded even when the fix is small, provided it changes what a reader would do. A corrected naira amount, a corrected pip value, a corrected regulator name, and a corrected leverage figure all get entries. A corrected spelling that does not change meaning does not get an entry but is noted in the page history. Each entry is written in plain English, names the instrument (XAU/USD) where relevant, and states the currency (₦ or USD) explicitly. We do not use codes that a reader would need a glossary to understand. The entry is visible on the page it corrects, not only in a separate log.
How to report one
Report an error by email to editor@oyooptionsng.com, with the page address, the sentence you believe is wrong and, if you have one, the broker document that shows the correct figure. A screenshot or a link to the broker's own page helps more than an assertion.
We check the claim against the broker's documents before changing anything. If the document supports your point, the page is corrected and dated. If it does not, we will tell you what we found and leave the page as it stands.
What Counts as an Error Worth Logging on This Site
An error worth logging is any published statement that is factually wrong, internally inconsistent, or contradicted by a source we can name. Examples include a wrong pip value for XAU/USD, a margin figure that does not match the stated leverage, a regulator name that is misspelled or attributed to the wrong body, or a naira amount that cannot be traced to a bank transfer or card charge. A typo that changes meaning counts; a typo that does not change meaning does not. The test is simple: would a reader acting on the sentence make a different decision than if the sentence were correct? If yes, it is an error worth logging.
An error worth logging must be reproducible from the page itself or from a source the reader can check. If a sentence says one standard lot of gold is 100 oz and another says 10 oz, the contradiction is an error regardless of which figure is right. If a sentence says leverage is up to 1:200 via the offshore entity and a later sentence says 1:30, that conflict is an error because the two cannot both be true for the same account. A claim that a cost is low or competitive without a number is not an error of fact, but it is a gap we treat as a correction because it misleads by omission.
An error worth logging is not the same as a change in market conditions or a broker policy update. If FxPro changes its leverage cap, that is a new fact, not a past error. If the SEC Nigeria register changes, that is an update. The log records only cases where what we published was wrong at the time of publication, or where we cannot show it was right. A reader who reports a number that differs from the page should expect us to check whether the page was wrong then or whether the world moved after. Only the first goes into the error log.