Corrections Policy

How an error is fixed

An error is corrected in place and marked with a dated note, so a reader can see that the page changed and when. The desk does not quietly overwrite a wrong figure and pretend it was always right.

The note says what was wrong and what it now says, in plain words. If the error affected a ranking or a comparison, that is stated too, because a reader is entitled to know whether a conclusion moved.

The Difference Between a Correction and an Update

A correction fixes something that was wrong; an update changes something that was right and has since become out of date. The distinction matters because the two carry different weight. If we said gold's pip is 0.01 and it is 0.01, that sentence never needed correcting. But if the leverage cap applicable to the FxPro entity serving the Philippines changes, the page was accurate when written and is now stale, and that is an update. Readers deserve to know which of the two they are looking at, because one implies we made a mistake and the other does not.

The practical test is whether the original sentence would have been defensible on the day it was published. If a reader could have checked it then and found it correct, the later change is an update. If a reader could have checked it then and found it false, it is a correction. We apply that test before writing the entry, and the entry's label follows from it. A worked figure such as roughly $85.50 margin on a 0.10-lot gold position at the applicable cap is updated when the cap moves and corrected only if the arithmetic was wrong.

Updates are not an admission of sloppiness, and we do not dress them up as corrections to seem diligent. A page that quietly relabels a stale fact as a mistake is misrepresenting its own history, which is worse than the staleness. Equally, we do not soften a genuine error into an update to protect the page. The label is decided by the test above and by nothing else. Where the line is genuinely arguable, we say so in the entry and explain the reasoning, rather than picking whichever label looks better.

What Counts as an Error Worth Logging on a Gold Page

An error worth logging is a statement that was wrong when we published it, not one that later stopped being true. On a gold (XAU/USD) page that means a wrong pip value, a wrong contract size, a mislabelled leverage cap, a regulator caveat that names the wrong body, or a margin figure that does not follow from the stated inputs. The test is simple: could a reader acting on that sentence have lost money or filed the wrong paperwork? If yes, it goes in the log. If the sentence was accurate on the day and the market simply moved, it is not an error.

Tone, style and layout problems do not enter the log. A clumsy sentence, a heading that reads awkwardly, or a table that wraps badly on a phone is fixed quietly and without a dated entry, because nothing factual was ever at stake. The same applies to a broken link that we simply repoint. What does qualify is anything that changes a number a reader might act on: the pip value of gold, the 100 oz contract size, the reference price we used, or the leverage cap that applies to the FxPro entity serving the Philippines.

Errors of omission count when the missing fact would mislead by silence. If a page explained gold margin without saying the leverage figure is a cap rather than a target, that absence was a defect and we log it as one. If a page named a funding rail that does not apply to Philippine readers, that is logged too. Readers in the Philippines fund with GCash or bank transfer, and a page that implied otherwise was wrong, not merely incomplete. We log the correction and state plainly what the page said before.

How Each Correction Is Recorded and Dated in the Log

Every correction is recorded as a dated line, and the date is the day the corrected text goes live, not the day someone noticed the problem. Each entry carries four things: the page and section affected, the wording that was wrong, the wording that replaced it, and the reason. Nothing is recorded as a vague note that a page was improved. A reader who opens the log should be able to reconstruct exactly what the page said before the change and why it no longer says it, without needing to ask us.

The date follows Philippine time, so a correction published on a Monday morning in Manila is dated that Monday even if the editor was working late in another time zone. Where a correction follows a reader report, the entry notes that it came from a report without naming the reader. Where it came from our own re-check, the entry says so. We do not backdate entries to make a page look cleaner, and we do not date an entry to the day a source published something if our own text only changed later.

Superseded wording stays visible inside the entry rather than being overwritten in place. The log line keeps the old sentence in quotation marks beside the new one, so the record shows a before and after rather than a single current state. For figures that depend on the broker entity, such as the leverage cap that applies to the FxPro entity serving the Philippines, the entry states that the figure was re-checked against the applicable cap rather than asserting a new ratio. This keeps every logged figure traceable to the day it was written.

How to report one

Report an error by writing to editor@cebufeesph.com with the page address and the sentence or figure in question. A source, such as the broker document and the date it was read, helps the desk check it faster.

The desk will look at the report against the broker's own documents. If the page is wrong, it is corrected with a dated note; if the page is right, the reader is told why, with the same source.

Who Decides a Correction, and Within What Time

A correction is decided by the editor responsible for the page, and it goes live as soon as the corrected wording is verified against a source we can point to. There is no committee and no queue waiting on a scheduled release. The constraint is verification, not approval: we would rather hold an entry for a day than publish a correction that is itself unverified. Every entry names what it was checked against, so the decision is auditable after the fact rather than resting on someone's memory of why they were confident.

Speed depends on what kind of claim is in question. A wrong pip value for gold, a wrong contract size, or a margin figure that does not follow from the stated inputs is treated as urgent, because a reader could act on it the same day. A wording problem that does not change any number is handled in the normal course. We do not publish a response time we cannot keep, and we do not promise a fixed window in hours. What we do commit to is that a material error is not left standing while a cosmetic one is polished.

Where the fact in question is a broker's applicable cap, we do not guess and we do not fill the gap with a number we were not given. If we cannot verify the current cap for the FxPro entity serving the Philippines, the page says the figure depends on that cap rather than asserting a ratio. That is a deliberate choice: an unverified number is worse than a stated dependency. The editor records the verification step in the entry, so a later reader can see that the number was checked rather than assumed.

A changed condition is a re-check, not an error

A condition that simply changed since the check is a re-check, not an error. If a broker alters its entity, its platform list or the leverage cap for the Philippines, the old page was accurate when read and is now out of date.

That distinction is kept because it protects the record. Re-checks are dated the same way, so a reader can always see when a page was last verified against the broker's documents.

Three Kinds of Change: Error, Update, Clarification

Every change we make to a fact-bearing sentence is marked as one of three kinds: error, update or clarification. An error means the sentence was false when published, and the mark sits beside the dated entry with the old and new wording quoted. An update means the sentence was true when published and the underlying fact has since moved, such as a leverage cap that applies to the entity serving the Philippines. A clarification means the sentence was true but could reasonably be read two ways, and we have tightened it without changing what it asserts.

The three marks are not decorative. They tell a reader what kind of trust to place in the page's history. A cluster of error marks on a topic is a signal that the page was weak there and has been repaired. A cluster of update marks is a signal that the underlying facts move often, which is normal for anything tied to a broker entity's applicable cap or to market prices. Clarification marks are the quietest of the three and should never be used to disguise a substantive change as a wording tidy-up.

Each mark is applied by the person who made the change and reviewed before the entry goes live, so the label is not a single person's private judgement. Where a change is part clarification and part update, we split it into two entries rather than blending the marks, because a blended entry hides which part of the change was substantive. The reference price of about 4275.0 for XAU/USD is a figure that gets updated rather than corrected, and it is marked as such, with the date, every time the page is re-based to a fresh reference.

Why the Correction Log Stays Public

The log stays public because a reader cannot judge a page's reliability from the page alone. Anyone can present a clean current version. What separates a maintained reference from an abandoned one is the visible record of what changed and when. For a high-risk subject like gold trading, where a wrong pip value or a misread leverage cap has a direct cost, the history is part of the evidence. Keeping it behind a login or in an internal file would remove exactly the information a cautious reader needs before acting on anything we write.

Public also means the log is not curated for appearance. We do not delete the entries that show us in the worst light, and we do not bury them under a long list of trivial clarifications. A reader scanning the log should be able to find the entries that actually changed a number, because those are the ones that affect a decision. The regulator caveat is a good example: FxPro is licensed by the FCA (UK) and CySEC, not by the SEC of the Philippines, and any entry touching that sentence is material to a Philippine reader and stays visible.

There is a practical benefit too. A public log lets readers in the Philippines point at a specific dated line when something still looks wrong, which makes a report faster to resolve. It also stops us from re-litigating settled questions, because the reasoning behind each change is already written down. The log is not a marketing page and it is not a blog. It is a working record, kept in the open because the alternative, a private record we describe but never show, asks readers to trust a claim rather than check it.