How errors are corrected

Fixed in place, with a date

A correction is made to the page itself, so the wrong version does not survive anywhere, and it carries a dated note describing what was wrong and what it now says. We do not delete a page to make a mistake disappear, and we do not rewrite history by removing the record of the change.

This matters most with figures. If we stated a leverage cap or a margin example and it turns out we read it wrongly, the corrected figure and the date of the fix are shown together, so a reader can see both the current statement and the fact that it was once different.

How to report one

Send the page address, the exact sentence, and what you believe is correct to editor@iloilocoinph.com. If you can point to the broker's own document and the date you read it, that speeds things up considerably, because it gives us the same kind of source we use ourselves.

We look at every report. We cannot promise a response time, and we will not always agree, but a specific, sourced report is the one most likely to change a page.

Who Decides a Change and in What Time

The decision to change this page sits with the editorial owner of the page, who is responsible for the accuracy of every figure and caveat on it. That person decides whether a reported issue is an error, an update, or a clarification, and assigns the mark and the date. The decision is not delegated to a marketing function, because a change that affects a leverage cap or a margin example is an accuracy decision, not a promotional one. The owner also decides when a reported issue does not meet the threshold and is fixed in place without a log entry.

The time frame depends on the kind of change. An error that could mislead a reader about the instrument, the lot size, the pip value, or the regulator caveat is treated as urgent and is corrected as soon as it is verified. An update that follows an external condition is made when the condition is confirmed, not before. A clarification is made when the wording is reviewed. There is no single clock for all three, because a wrong pip value and a clumsy sentence do not carry the same risk. Urgency follows the potential for financial harm.

Verification means checking against the source that governs the statement. For the regulator caveat, that means the licence status of the entity serving the Philippines. For the leverage cap, that means the cap that applies to that entity. For the margin example, that means recalculating at the applicable cap so the figure remains about $385.00 for a 0.10-lot bitcoin position, or updating it if the cap has moved. The owner does not change a figure on the strength of a reader's report alone; the report starts the check, and the source ends it.

Three Kinds of Change and How Each Is Marked

Every change to this page is marked as one of three kinds: error, update, or clarification. An error mark means the earlier statement was wrong and has been replaced; the entry quotes the old and new text. An update mark means the earlier statement was right when written but a condition changed; the entry names the condition and the date it changed. A clarification mark means the statement was not wrong but could be misread; the entry shows the before and after wording. The mark sits next to the dated entry so a reader can tell at a glance which kind of event occurred.

The marks are not interchangeable. An error is never relabeled a clarification to soften it, and an update is never relabeled an error to appear more rigorous. If a page said one pip equals 1.0 for bitcoin and that is correct, a rewording is a clarification. If a page said one pip equals 0.1, that is an error. If a page said the margin for a 0.10-lot position is about $385.00 at the applicable cap and the cap later changes, that is an update. The label follows the facts, not the mood of the editor.

Each mark carries the same date discipline: the date the change goes live. Clarifications are the most common and the least dramatic; they often add a phrase such as 'this is a cap, not a setting to aim at' where the original wording could be read as a target. Errors are the least common and the most important to mark plainly. Updates are routine when external conditions move. A reader who wants to know whether a statement was ever false should look for the error mark; a reader who wants to know whether it is current should look at the date.

The Difference Between a Correction and an Update

A correction fixes something that was wrong; an update changes something that was right but is now out of date. If the page said one standard lot equals 1 BTC and it does, but a reader misreads it, that is not a correction. If the page said the margin for a 0.10-lot bitcoin position is about $385.00 at the applicable cap, and the cap later changes so that figure no longer holds, the page is updated, not corrected. The distinction matters because it tells the reader whether the earlier statement was false or merely time-bound. Corrections carry an admission; updates carry a date.

An update is triggered by a change in an external condition: a regulator's licence status, a funding method available to readers in the Philippines, or the leverage cap that applies to the entity serving this country. A correction is triggered by an internal failure: a wrong instrument code, a wrong currency symbol, a wrong regulator name, or a misstated formula. The log marks the two differently so a reader can see whether the page was ever inaccurate or simply moved with the facts. Both are dated, but only the correction says the earlier version was in error.

The practical test is simple: could the statement have been true when it was written? If yes, and it is now false because the world changed, it is an update. If no, it is a correction. A page that says FxPro is licensed by the SEC of the Philippines was never true and needs a correction. A page that says GCash is a funding method and later that method is removed needs an update. The log keeps both kinds of entry, but the label tells the reader which kind of event occurred.

How a Correction Is Recorded and Dated on This Page

A correction is recorded as a dated entry that names the exact sentence or figure changed, the old wording or number, the new wording or number, and the reason. The date is the date the correction goes live, not the date it was reported. Each entry sits in a public log tied to the page, so a reader can see that a change happened and when. If the correction concerns a number, the entry shows both values; if it concerns wording, the entry quotes both versions. Nothing is summarized as 'minor fixes' — the log is specific enough that a reader can verify the change without guessing.

The date matters because a trading page is read as of a moment. A statement about the leverage cap or the margin example is true relative to the conditions on a given day. The log therefore uses a full date, not a month or a quarter, so a reader comparing two versions can tell which came first. If a correction is made to a page that also carries an update, the two entries are dated separately even if they happen on the same day. That separation keeps the record honest: an error fixed is not the same event as a condition changed.

Recording is not the same as announcing. The entry is written in plain English, without blame and without hedging, and it stays attached to the page permanently. If a reader finds a discrepancy between the live page and the log, the log is the authority on what changed and when. The correction record does not include promotional language or commentary on market direction; it is a factual audit trail. For a page about bitcoin (BTC/USD), where a wrong pip value or lot size can mislead a position calculation, that audit trail is part of the page's usefulness.

What Counts as an Error Worth Logging on a Bitcoin Page

An error worth logging is any statement on this page that misstates a fact, a figure, or a condition in a way that could change what a reader does with their money. That includes a wrong instrument code, a wrong pip value, a wrong reference price, a wrong leverage cap, a wrong regulator caveat, or a wrong funding method. On a bitcoin page, a pip is 1.0 and one standard lot is 1 BTC; if either is printed wrong, that is an error. If the page says GCash when the listed method is bank transfer, that is an error. Typos that do not change meaning are not logged; they are fixed in place.

A number that is merely outdated is not automatically an error. If the reference price of about 77000.0 moves with the market, the page is not wrong; it is dated. The error threshold is whether the statement was false when published, or whether it became false because a condition it depended on changed without the page saying so. A margin example of about $385.00 for a 0.10-lot bitcoin position is correct only at the applicable leverage cap; if the cap changes and the example is left standing, that becomes an error, not an update.

A missing caveat counts as an error when its absence could mislead. The regulator caveat for the Philippines — that FxPro is licensed by the FCA (UK) and CySEC, not by the SEC of the Philippines — is not decorative. If a page discusses leverage or funding without that caveat in view, the omission is loggable. The same applies to the leverage cap itself: it is a cap, not a setting to aim at, and a page that frames it as a target has an error of framing. Readers can report such issues; the log records what was wrong and what changed.

Why the Correction Log Stays Public on a Trading Page

The log stays public because a trading page is only as good as its trail. A reader deciding whether to trust a statement about the leverage cap, the margin example, or the regulator caveat needs to see whether that statement has been changed and why. A private log asks for trust; a public one lets the reader check. On a page about bitcoin (BTC/USD), where a wrong lot size or pip value can distort a position size, the cost of an unseen correction is real money. The log is part of the page, not an internal memo.

Public also means durable. The log is not cleared when the page is redesigned, and entries are not removed when they become inconvenient. A reader can see that a figure was once stated differently and that the change was recorded at a date. That record does not depend on the reader having visited before; it is available to anyone who looks. For readers in the Philippines comparing funding rails such as GCash or bank transfer, the log shows whether a method was added, removed, or re-described, and when.

The log does not publish reader reports or personal details. It publishes the correction: what was wrong, what it became, and the date. That is enough to make the page auditable without turning the log into a forum. The regulator caveat for the Philippines — that FxPro is licensed by the FCA (UK) and CySEC, not by the SEC of the Philippines — is exactly the kind of statement that should never change silently. If it ever needs a correction, the public log is where a reader would see it first.

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

If a broker altered its terms after we read them, our earlier statement was accurate when written and the right action is a re-check, not a correction. We update the page and note the date of the re-check, but we do not label it an error, because calling a correct historical statement wrong would mislead you about our accuracy.

The distinction is simple: an error means we misread or misstated the source, while a re-check means the source itself moved. Both get a dated note, and both are visible to you.