Corrections and Re-checks

How a correction is handled

A correction is made in place, with a dated note saying what changed and when. The page is edited rather than deleted, so a reader who saw the earlier version can see what moved. Silent edits are not used, because a figure that changes without a trace is worse than one that was wrong and is now marked.

The dated note sits with the corrected passage and names the substance of the change, not just that a change happened. If the error affected a comparison or a worked example, the note says so, and the surrounding text is checked for knock-on effects before the page goes back up.

How to report one

Send the page address, the exact wording, and what you believe the correct position is to editor@davaodemoph.com. A source helps: the broker's own document, a dated screenshot, or a link to the page where the figure appears. The desk checks the claim against its own record of the read date before changing anything.

Reports are welcome even when they turn out not to be errors, because each one triggers a fresh look at the source. The desk does not promise a response time, but every report that identifies a specific sentence is read and logged.

What is a re-check, not an error

A condition that has simply changed since the check is a re-check, not an error. If a broker alters its leverage cap, its funding rails or its document wording after the date the desk read it, the page was accurate when written and is now out of date. That is recorded as a re-check with a new read date.

The distinction matters because it keeps the correction log honest. Errors are the desk's mistakes and are marked as such; re-checks are the world moving and are marked with the date the new reading was taken. Either way the reader sees which one happened, and the page carries the date of the latest check.

What counts as an error worth logging on this page

An error worth logging is a factual statement that is wrong, incomplete, or misleading in a way that changes what a reader would do. On this page that means a wrong instrument code, a wrong lot size or pip value, a wrong regulator caveat, or a funding method listed that is not in the approved list. A typo that changes no meaning is not logged as an error; it is fixed quietly under a clarification. The test is simple: would a reader acting on this sentence make a different decision than if the sentence were correct? If yes, it is an error.

An error also includes a missing risk warning where one is required for a high-risk product such as gold (XAU/USD) trading. If a paragraph states a leverage cap without saying it is a cap and not a target, that omission is an error. The same applies to any number that appears without its unit or currency code. We log these because the page is a trading toolkit, and a missing caveat can cost a reader real money in pesos. The log entry names the sentence, the approved fact, and the date the fix goes live.

Finally, an error is not the same as a fact that has changed in the world. If the FxPro entity serving the Philippines updates its leverage cap, the old sentence was correct when written; that is an update, not an error. We log it in the same public record but under a different mark. This distinction matters because it tells the reader whether we got it wrong or whether the world moved. Both are worth knowing, but only one is a quality failure on our side.

How a correction is recorded and dated in the public log

A correction is recorded as a single log entry with four fields: the page name, the exact sentence changed, the approved fact it now matches, and the date the change went live in Manila time. The date is the publication date of the corrected page, not the date someone noticed the problem. If the fix is held for a batch release, the log shows both the notice date and the live date so a reader can see the gap. No correction goes live without a matching log entry on the same day.

The entry is written in plain English and names the source of the approved fact without inventing a citation. For this page the approved facts are the instrument details (gold, XAU/USD, 1 lot = 100 oz, pip = 0.01, reference price around 4275.0), the local funding methods (GCash and bank transfer), and the regulator caveat that FxPro is licensed by the FCA (UK) and CySEC, not by the SEC of the Philippines. The entry does not restate a spread, commission, swap, or minimum deposit as a number because those are not approved facts.

The log is append-only and ordered newest first, so the most recent correction is always at the top. Each entry keeps its original wording even after later corrections, which means a reader can see a chain of fixes on the same sentence. If a correction is itself later found to be wrong, we do not edit the old entry; we add a new entry that points back to it. This keeps the record honest and lets anyone trace how a sentence evolved over time.

The difference between a correction and an update on this page

A correction fixes a sentence that was wrong against the approved facts at the time it was written. An update changes a sentence because the approved fact itself has changed, such as a new leverage cap for the entity serving the Philippines or a new local funding method. The test is whether the old sentence was true when published. If it was true then and is false now, it is an update. If it was false then, it is a correction. Both appear in the log, but only a correction counts against our accuracy record.

An update is dated to the day the new fact takes effect, not the day we learned about it. If the change is announced in advance, the log entry can be published early with the effective date, and the page text changes on that date. This matters for a cap: a reader should never see a cap described as current before it is current. Corrections, by contrast, take effect as soon as they are published because the old sentence was never right.

The difference also shapes how we phrase the page. A corrected sentence is rewritten to match the approved fact exactly. An updated sentence is rewritten to describe what the fact depends on, because the new number may not be in the approved list. For example, if the leverage cap changes, the page says the cap is the one that applies to the entity serving this country, and the worked margin figure is recalculated only if a new approved figure is provided. We do not guess the new margin.

Why the correction log stays public and permanent

The log stays public because a reader cannot judge a page's reliability without seeing its mistakes. A trading page that hides its corrections is asking for trust it has not earned. By keeping every entry visible, including the ones that make us look careless, we let a reader decide whether the page is precise enough for their purposes. This is especially important for high-risk material such as gold trading, where a wrong lot size or a missing risk warning can lead to a real loss in pesos.

The log is also permanent because deleting an entry would break the chain of evidence. If we removed a correction after the fact, a reader who saw the old sentence would have no way to confirm what changed or when. Permanence means the log is append-only: new entries are added, old ones are never edited or removed. Even if a correction is later superseded, the original entry stays, and a new entry explains the supersession. This is the same principle as keeping a dated audit trail.

Finally, the log is public because it holds us to a standard we can be checked against. Anyone can compare a log entry to the current page text and see whether the fix was applied as described. That check does not require an account or a request; it is open to any reader in the Philippines or elsewhere. The log does not list an author name or a personal contact because those are not approved facts, but it does list the page, the sentence, the approved fact, and the date.

How error, update, and clarification are marked in the log

Each log entry carries one of three marks: ERROR, UPDATE, or CLARIFICATION. ERROR means the published sentence was wrong against the approved facts when written. UPDATE means the approved fact changed after publication, so the sentence was true then and is false now. CLARIFICATION means the sentence was not wrong but could be read in a way that misleads, so we rewrote it without changing the underlying fact. The mark is the first field in the entry and is never changed after publication.

The mark determines what the entry must contain. An ERROR entry must quote the wrong sentence and the approved fact it now matches. An UPDATE entry must state the old fact, the new fact, and the effective date, or say that the new fact depends on the entity serving this country if no number is approved. A CLARIFICATION entry must quote both the old and new wording and explain what reading was being prevented. No entry is published without the required fields for its mark.

The marks are also used on the page itself, in a short history note at the foot of each section that has changed. A reader who does not want to open the full log can see at a glance whether a section was corrected, updated, or clarified, and on what date. The note does not repeat the full entry; it points to the log for the detail. This keeps the page readable while still making the change visible at the point of use.

Who decides a change is needed, and within what time

The decision to log a change is made by the person who maintains this page, using the approved facts as the only standard. There is no committee and no author byline, because no individual name is an approved fact. The maintainer compares the published sentence to the approved list and decides whether the gap is an error, an update, or a clarification. If the gap is not covered by the approved list, the maintainer does not invent a number; the sentence is rewritten to say what the fact depends on.

The time limit is the same working day for an error that affects a risk warning, a regulator caveat, or a number a reader could act on. For example, a wrong statement that FxPro is licensed by the SEC of the Philippines would be corrected the same day it is confirmed, because the approved caveat is that FxPro is licensed by the FCA (UK) and CySEC, not by the SEC of the Philippines. Less urgent errors, such as a broken sentence that changes no meaning, are batched and fixed within five working days.

An update follows the effective date of the new fact, not the date of discovery. If a new leverage cap for the entity serving the Philippines is announced with an effective date, the page changes on that date and the log entry is dated to it. If the new fact has no approved number, the page is rewritten to describe the cap as the one that applies to the entity serving this country, and the worked margin figure is left as the last approved figure with a note that it depends on the cap. We do not publish a guessed margin.