Corrections and re-checks
Errors are fixed in place with a dated note, never silently, and a reader can report one to [email protected].
How an error is fixed
When a page is wrong, the wrong sentence is corrected where it stands and a dated note is added beside it saying what changed. The page is not quietly rewritten and the error is not deleted as if it never existed, because a reader who relied on the earlier version deserves to see that it moved. The note stays with the page.
This applies to figures as much as to wording. If a leverage cap, an entity name or a funding list was stated and later turns out to have been misread, the correction says so plainly. We do not use a correction to slip in a new claim that was never checked; the corrected sentence has to meet the same sourcing rule as the original.
How Error, Update and Clarification Are Marked in the Log
Each log entry carries one of three labels: Error, Update, or Clarification. Error means the original statement was wrong and has been replaced. Update means the original was right when published but conditions changed, such as a new leverage cap or funding option. Clarification means the original was not wrong but could be misread, so we added a condition or example without changing the core fact. The label appears at the start of the entry and in the page’s change history, so a reader can filter by type.
The marking is consistent across the site. An Error entry always shows the old and new wording side by side and names the evidence used to confirm the mistake. An Update entry shows the date the change took effect and the source of the new condition. A Clarification entry shows the added sentence and why it was needed, for example to state that leverage caps for Nigeria are conflicting and unverified. We do not use Clarification to smuggle in a correction; if the original was wrong, it is labelled Error even if the fix is small.
Readers can see the label in two places: the log itself and a small marker next to the changed sentence on the page. The marker links to the log entry ID. This means a reader who lands on the page months later can tell whether a sentence has been corrected, updated, or clarified without reading the whole log. For gold pip values and lot sizes, where precision is critical, that immediate signal helps. The three labels are not decorative; they tell you what kind of change happened and how much weight to give the current wording.
The Difference Between a Correction and an Update
A correction fixes something that was wrong when it was published; an update changes something that was right then but is no longer current. For example, if we wrote that 1 lot of gold equals 100 oz and that was always true, changing it would be a correction only if we had written the wrong number. If a broker changes its leverage cap for Nigeria, that is an update because the old statement was accurate at the time. The distinction matters because corrections admit error, while updates track reality. We mark them differently so readers know which is which.
Updates are dated and logged too, but they are labelled as updates, not corrections. They do not imply the earlier page was wrong. A typical update is a change in the regulator caveat wording or a new funding method such as local NGN bank transfers becoming available. We do not use an update to quietly fix a mistake. If a change is both, we split it into two entries: a correction for the error and an update for the new condition. That keeps the record precise and prevents corrections from being hidden as routine updates.
The practical test is: was the original statement true on the day it was published? If no, it is a correction. If yes, but circumstances changed, it is an update. For gold (XAU/USD), a change in the reference price from 4275.0 is an update, not a correction, because the old price was a snapshot. A wrong statement that one pip equals 0.1 would be a correction. Readers can rely on the label to know whether the page made a mistake or simply moved with the market.
What Counts as an Error Worth Logging on This Site
An error worth logging is any statement on the page that is factually wrong, misleading, or contradicts the source we cited, and that could change a reader’s decision about gold trading. That includes a wrong pip value for XAU/USD, a misstated lot size, an incorrect margin example, or a regulator caveat that misnames the authority. It does not include a change in market conditions, a new broker policy, or a difference of opinion about strategy. If a reader following the page would be misled about cost, risk, or regulation, it belongs in the log.
The threshold is materiality: if the mistake affects how a Nigerian reader funds an account, sizes a gold position, or checks a broker against the SEC Nigeria register, it is logged. Typos that do not change meaning, formatting glitches, and broken links are fixed quietly and not logged. We do not log every wording tweak. The test is simple: would a careful reader who relied on the sentence have made a different choice? If yes, it is an error. If no, it is housekeeping. This keeps the log focused on what matters for trading decisions.
We also log an error when a figure we presented as fixed turns out to depend on something we did not state. For example, if we wrote that a 0.10-lot gold position needs about $85.50 margin at 1:200 without noting that leverage caps for Nigeria are conflicting and unverified, that omission is an error because it hides a condition. The same applies to any cost description that implies a number we were not given. Precision about what a number depends on is part of accuracy, so failing to state a dependency is loggable.
A changed condition is a re-check, not an error
If a broker changed its terms after the date a page was checked, the page was not wrong when it was written. That is a re-check, not a correction: the old figure was accurate on the day it was read, and the new one is recorded with a new date. The distinction matters, because calling every change an error would make the correction log useless.
The practical rule for a reader is the same either way. Every figure on this site is dated, and the date is the thing to look at. If the date is old, confirm the current term with the broker before you act on it, including the leverage cap and the funding methods available from Nigeria.
Why the Correction Log Stays Public
The log stays public because trust in a trading resource depends on being able to see how it handles its own mistakes. A reader in Nigeria deciding whether to fund an account by bank transfer or card needs to know if a cost or margin figure was ever wrong and how it was fixed. A private log would let us quietly rewrite history. A public one makes every change checkable. It also forces discipline: knowing an entry will be visible discourages casual edits and encourages verifying against the source before publishing.
Public logging also helps other writers and educators who cite the page. If they quoted an old margin example, they can see the correction and update their own material. It reduces the spread of stale numbers about gold lot sizes or leverage caps. For a high-risk instrument like XAU/USD, where a small misunderstanding about pip value can lead to oversized positions, that matters. The log is not a marketing feature; it is part of the safety of the page. It shows the page is maintained, not abandoned.
Finally, the log stays public because the regulator caveat itself asks readers to confirm any broker on the SEC Nigeria register. That habit of checking is undermined if our own record is hidden. A public log is consistent with the advice we give: verify, don’t assume. It also lets a reader spot a pattern, such as repeated corrections on the same topic, which might signal a weak area. We would rather be judged on that record than hide it. The log is permanent and linked from every page it affects.
Who Decides on a Correction and Within What Time
The decision to correct rests with the editor responsible for the page, acting on a report from a reader or a scheduled re-check. That editor confirms the error against the original source before approving any change. No single writer can quietly alter a published figure. For a numerical change, such as a margin example, a second reviewer checks the arithmetic. The aim is to separate the person who spots the issue from the person who fixes it, so that a correction is not just one person’s opinion. The log entry records the approving role.
The time target is to acknowledge a reported error within two working days and to publish a correction or a reasoned rejection within ten working days. If verification takes longer, the log shows the issue as open with the date it was reported. We do not leave a known error live without a note. For a high-risk topic like gold trading, where a wrong pip value could affect position sizing, we aim to act faster, but we do not promise a number we cannot meet. The ten-day target is the outer limit for a decision.
If the report concerns the regulator caveat or a funding method, the editor checks the named authority or the broker’s current terms before deciding. We do not correct based on a single unverified review; the leverage caps for Nigeria are an example where reviews conflict, so we state the conflict rather than pick a number. The decision and its rationale go into the log. A reader who disagrees with the outcome can see the reasoning and the evidence, which is the point of making the process visible rather than opaque.
How to report one
Send the page address, the exact sentence, and what you believe is wrong to [email protected]. A source helps most: the broker document, the date on it, or the page where the correct figure appears. Without a source the desk can still look, but the check will be slower and may end with the original sentence standing.
You do not need an account or any relationship with the desk to report an error, and there is no charge for it. Reports are read in the order they arrive, and a report that turns out to be right is noted on the page like any other correction.
How a Correction Is Recorded and Dated in the Log
A correction is recorded as a dated entry in a public log that names the page, the sentence or figure changed, the old wording, the new wording, and the reason. The date is the date the correction goes live, not the date it was reported. Each entry gets a sequential ID so readers can cite it. We do not backdate entries or merge them silently. If a correction takes several days to verify, the log shows the live date and, where useful, the date the issue was first reported. This gives a clear timeline from report to fix.
The entry also states who approved the change and what evidence was used, such as the regulator caveat from the FCA, CySEC and FSCA, or the worked margin figure at 1:200. We do not publish personal names, but we do publish the role, for example editor or fact-checker. If the correction involves a number, the entry repeats the number and its condition, such as 0.10 lot gold needing about $85.50 margin via the offshore entity. That way the log itself is a standalone record a reader can check without reopening the whole page.
Dating is in West Africa Time and shown as day, month, year. If a correction is later found to be wrong, we do not edit the original entry; we add a new entry that supersedes it and cross-reference the ID. The log is append-only in that sense. Readers can therefore see not just the current state but the sequence of fixes. This matters for a page about gold trading where a wrong pip value or lot size can mislead, and it keeps the record honest about how the page evolved.