Corrections Policy

Fixed in place, never silently

Errors are corrected in place with a dated note, never quietly edited away. The page keeps its address and its purpose, and a short line records what changed and when, so a reader who saw the earlier version can see that it moved and why.

We do not delete a page to make an error disappear, and we do not rewrite history by removing the trace of the fix. If a correction changes a conclusion, the note says so plainly rather than softening it.

The Difference Between A Correction And An Update

A correction fixes a statement that was wrong when published; an update changes a statement that was right when published but is no longer current because an external fact moved. If a page states the reference price of XAU/USD as approximately 4275.0 and that figure was accurate on the date of publication, a later change to a new reference price is an update, not a correction. If the same page had stated the pip value as 0.10 when the instrument specification is 0.01, that is a correction, because the statement was false at the time it was written. The distinction is about the truth of the original statement, not about how large the change looks.

Updates are marked as updates in the log and are dated the same way as corrections, but they do not carry the same implication that the original publisher made a mistake. A reader who sees an update entry knows the page is being maintained against moving facts, such as a change in the leverage cap that applies to the entity serving the Philippines or a change in the funding methods listed. A correction entry, by contrast, tells the reader that a factual error existed and has been fixed. Both are logged publicly, but the label matters because it tells the reader whether to trust the earlier version of the page for historical purposes.

The practical test is simple: if the original statement would still be true today under the conditions it described, a change to it is an update; if it would be false today under those same conditions, the change is a correction. This test prevents the log from being used to quietly reclassify mistakes as updates. It also means that a page can have both a correction and an update for the same figure at different times, and each is recorded separately with its own date and reason.

Why The Log Stays Public

The log stays public because a reader cannot judge the reliability of a page without seeing what has been changed and why. If corrections were made silently, a reader who relied on an earlier version of a margin example or a regulator caveat would have no way to know that the page had moved. Keeping the log public means that a reader in the Philippines can check whether a statement about FxPro's licensing, the applicable leverage cap, or the margin needed for a 0.10-lot gold position has been corrected, and can see the date of the correction. Public access is the mechanism that makes the correction meaningful rather than cosmetic.

A public log also creates a record that can be checked against the page itself, which is a stronger form of accountability than a private note. If the log says a correction was made on a given date to a specific section, a reader can compare the current page with the log entry and see whether the fix is actually present. This matters for high-risk topics such as leveraged gold trading, where a wrong figure can mislead a reader about the margin required or the risk of a position. The log does not prevent errors, but it makes them visible and traceable, which is the minimum a reader should expect from a page that asks to be trusted.

The log stays public even when a correction is embarrassing, because hiding it would undermine every other statement on the page. A reader who finds that one correction was concealed has no reason to trust the rest of the log or the page. The same standard applies to updates and clarifications: they are logged publicly so that the page's history is a complete record, not a curated one. The log is not a marketing page and does not need to present the site in a favourable light; it needs to be accurate, dated, and complete.

The Three Kinds Of Change And How Each Is Marked

Every change to a page is marked as one of three kinds: error, update, or clarification. An error mark means a statement was wrong when published and has been fixed, and the entry shows the original and corrected text with the date. An update mark means a statement was right when published but an external fact has moved, such as a change in the leverage cap that applies to the entity serving the Philippines or a change in the reference price used in an example. A clarification mark means the original statement was not wrong but could be misread, and the wording has been adjusted without changing the underlying fact. Each mark is applied at the time of the change and is not changed later.

The three marks are visually distinct in the log so a reader can scan the history and see what kind of change has been made without reading every entry. An error entry carries the original and corrected text side by side; an update entry carries the old and new external fact with the date the fact changed; a clarification entry carries the old and new wording with a note on what was ambiguous. The mark is part of the permanent record and is not removed if the page is later changed again. If a clarification later turns out to have been an error, a new error entry is added rather than the clarification being reclassified.

The marking system exists so that a reader can tell the difference between a page that is being maintained and a page that is being quietly rewritten. A page with many update marks is not necessarily unreliable; it may simply cover facts that move, such as the margin required for a 0.10-lot gold position at the applicable cap. A page with an error mark is telling the reader that a mistake was made and fixed, which is different from a page with no log at all. The marks are not a score; they are a record, and their value comes from being applied consistently and publicly.

Who Decides, And In What Time

The decision to log a change is made by the person responsible for the page's factual accuracy, not by a marketing or sales function, and the decision is recorded with the entry. That person checks the reported issue against the source, decides whether it is an error, an update, or a clarification, and applies the mark and the date. The time taken depends on the complexity of the check: a clear factual error such as a wrong pip value for gold can be corrected and logged quickly, while a claim about a regulator's scope may need to be checked against the licensing disclosure before a decision is made. The log does not promise a fixed turnaround, but it does record the date the decision was made.

The decision is not made by the reader who reports the issue, and a report does not automatically become a correction. The reader's role is to point to the statement and the reason it may be wrong; the page owner's role is to verify and decide. This separation matters because a reader may be mistaken about the facts, and logging a change that is not warranted would make the log less reliable. If the page owner finds that the original statement was correct, no change is logged, but the report is still considered. The log records only changes that were actually made, not reports that were rejected.

The time between a report and a decision is not fixed, but the date of the decision is always recorded, so a reader can see how long the page carried a statement after it was questioned. For a high-risk topic such as leveraged gold trading, the page owner aims to resolve clear factual errors before leaving them live for long, but the log does not claim a guaranteed response time. What the log does guarantee is that once a decision is made, it is dated and public. A reader who wants to know whether a statement has been reviewed can check the log for the date of the most recent entry affecting that section.

How A Correction Is Recorded And Dated

A correction is recorded as a separate log entry with the date it was made, the page and section affected, the original text or figure, the corrected text or figure, and the source relied on. The date recorded is the date the correction goes live, not the date the error was first reported, and the entry stays attached to the page permanently. For example, if a margin example said a 0.10-lot gold position needs $85.50 margin at the applicable cap and the figure was later found to be misstated, the entry would show both the old and new figures and the date of the fix, with no silent overwrite of the page history.

Each correction entry also records who made the decision and what kind of change it is, so a reader can tell an error fix from an update or a clarification without reading the whole page. The date is stored in a fixed format and is not edited later, even if the page is subsequently updated for an unrelated reason. If a correction itself is later found to be incomplete, a new entry is added rather than the old one being changed, so the sequence of dates remains a true record. The log is ordered by date, and the most recent entries appear first so a returning reader can see what changed since their last visit.

The date on a correction is not the date the underlying fact changed; it is the date the page was brought into line with the fact. This distinction matters when a source changes silently, because the log will show a gap between when the source changed and when the page was corrected. That gap is part of the record and is not hidden. Readers in the Philippines who check the log can see, for instance, that a regulator caveat was added on a specific date after the entity serving the country changed its licensing disclosure, rather than assuming the page was always correct.

What Counts As An Error Worth Logging

An error worth logging is any published statement that is factually wrong about a verifiable input, such as a price reference, a lot size, a pip value, a margin figure, a regulator name, a platform name, or a funding method. If a page says one standard lot of gold is 100 oz and the correct figure is 100 oz, that is not an error; if it says one pip is 0.10 when the instrument specification is 0.01, that is an error. The test is whether the statement can be checked against a source and found to be false, not whether a reader disagrees with the trading view expressed.

Errors worth logging also include omissions that change the meaning of a factual statement, such as leaving out the regulator caveat that FxPro is licensed by the FCA (UK) and CySEC and not by the SEC of the Philippines. A missing caveat is not a style preference; it changes what a reader understands about who supervises the broker. The same applies to a missing risk warning on a leveraged product, or a margin example that uses a leverage ratio other than the cap that applies to the entity serving the Philippines. If the omission could lead a reader to a wrong factual conclusion, it belongs in the log.

Errors worth logging do not include changes in market conditions, such as a movement in the XAU/USD reference price away from the 4275.0 figure used in an example, or a change in the leverage cap set by the entity serving this country. Those are updates, not errors, because the original statement was correct when published. They also do not include differences of opinion about strategy, risk appetite, or the suitability of gold trading for a particular reader. Logging is reserved for statements that were wrong at the time of publication against the facts available then, or that became wrong because a source changed and the page was not corrected in time.

A changed condition is not an error

A condition that has merely changed since we checked is a re-check, not an error. If a broker alters its leverage terms, its funding options or the entity serving the Philippines after the date we read its documents, our earlier sentence was accurate when written, and we update it as a fresh check rather than a correction.

That is why we date what we read. When you see a figure on this site, treat the date attached to it as the point at which it was true, and verify the current terms with the broker before you rely on them.

How to report an error

Send the report to editor@benguetgoldph.com and include the page, the sentence you believe is wrong, and, where you can, the broker document or source that contradicts it. A pointer to the exact clause is worth more than a general complaint, and it lets us check quickly.

We do not promise a response time in hours or days, but every report that identifies a real error gets looked at. If you are right, the page changes and the note is dated. If the wording was defensible but easy to misread, we will usually rewrite it anyway.