Corrections

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

An error is corrected in the text itself, with a short dated note saying what changed and when. We do not quietly overwrite a wrong figure or delete a sentence and pretend it was never there, because a reader who relied on the old version deserves to see the change.

The note stays with the page so the correction is visible to anyone who checks later. If the error affected a worked example, such as the margin figure for a 0.10-lot gold position, the corrected version is shown and the old one is not left standing elsewhere on the site.

Changed conditions are re-checks, not errors

A condition that merely changed since we checked is a re-check, not an error. If a broker alters its leverage cap, its funding methods or its entity for the Philippines after our date read, the original statement was accurate when written and the fix is to update it with a new date.

That distinction matters because it tells you how to read the site. A dated figure is a record of what the broker published on that date, and you should verify the current version with the broker before you rely on it. When we re-check, we say so.

Correction Versus Update: Two Different Records

A correction says we were wrong; an update says the world changed. If a regulator description, a funding method or a leverage cap moves and our page had it right beforehand, nothing was wrong and no correction is due. What is due is an update: a dated note that the underlying fact moved, with the old and new positions both visible. Mixing the two would let us quietly reclassify our own mistakes as the passage of time, which is exactly the habit this log exists to prevent.

The distinction matters to a reader deciding whether to trust the rest of the page. A page with several corrections is not necessarily worse than one with none; it may simply be one that checks itself and admits things. A page with corrections disguised as updates is worse, because it hides the admission. So the label is applied strictly, and when a change is both, we split it into two entries rather than blur them into one.

Practical example: if we had described the FxPro entity for the Philippines incorrectly, that is a correction. If the entity serving this country changes its applicable leverage cap, that is an update. The worked margin figure of about $85.50 for a 0.10-lot gold position would then be re-derived and noted as an update too, since the arithmetic was never wrong, only its input.

Who Makes the Call and on What Timeline

The decision sits with the person who owns the page and checks it, not with whoever reported the issue and not with a committee. That person reads the report, checks the claim against the source the page was built from, and assigns one of the three labels. Reports are read in the order received, and anything that could cause a reader to place a position on a wrong number is handled ahead of wording matters, because the peso consequence of a wrong margin figure is immediate.

The timeline depends on what the claim touches. A claim about the instrument itself, meaning the 100 oz lot size, the 0.01 pip, the reference price near 4275.0, or the leverage cap for the entity serving the Philippines, is treated as urgent and looked at first. A claim about phrasing, structure or a heading is scheduled with ordinary editing. No fixed hour count is promised here, because promising one and missing it would itself be the kind of claim this page logs.

Where the check is inconclusive, the entry is published anyway and marked as unresolved, with a note on what is still being verified. Publishing an open question is better than staying silent until it closes, because a reader may be deciding today. The owner is also the one who signs off the wording of the entry, so the person accountable for the page is the same person accountable for the record of it.

What Qualifies as a Loggable Error on This Page

A loggable error is a statement that was wrong when it was published, not one that has since become outdated. If a figure, a formula, a platform name or a regulator description did not match the source it was drawn from on the day we wrote it, that is an error and it goes in the log. If it was right then and the world moved, that is a different category entirely and is handled as an update. The test is what the source said at publication, not what it says today.

Formatting and tone are not errors. A clumsy sentence, a heading that could be sharper, or a paragraph that reads slowly is an editing job, not a correction, and it does not enter the log. What does enter is anything a reader could act on: a wrong lot size, a pip value stated incorrectly, a platform we do not actually offer, a claim about which entity serves the Philippines, or a description of margin that does not match the worked figure of about $85.50 for a 0.10-lot gold position at the applicable cap.

Borderline cases are logged rather than argued about. If it is genuinely unclear whether a statement was wrong at publication or merely aged, we treat it as an error and say so, because a reader who spotted the problem deserves an entry they can point to. Being over-inclusive costs us a line in a log; being under-inclusive costs a reader money if they traded on the wrong number. Only the second one matters.

How Errors, Updates and Clarifications Are Marked

Three labels are used and nothing else: error, update and clarification. Error means the page was wrong at publication and the fix changes what a reader should do. Update means the underlying fact moved and the page was right before. Clarification means the page was accurate but a reader could reasonably have read it as saying something else, so the wording changed without the substance changing. Each label carries its own dated entry and its own one-line reason.

The label determines what is shown. An error entry shows the old and new wording side by side, because a reader may have acted on the old version and needs to see exactly what it said. An update entry shows the previous position and the new one, since both were true in their time. A clarification shows only the new wording plus a note on the misreading it prevents, because no factual position changed and there is nothing to correct.

Clarifications are the most common of the three and the least dramatic, but they are marked anyway. A page that only logs outright errors will slowly fill with sentences that are technically true and practically misleading, and no log entry will ever flag them. Marking clarifications keeps that drift visible. The label is never used to dress up a real error as a wording tweak, and a change that alters what a reader should do is always an error.

Why the Log Stays Public and Unedited

The log stays public because a correction a reader cannot see is not a correction, it is a private note. Anyone deciding whether to rely on a page about gold trading, margin and leverage should be able to see how often that page has been wrong and what kind of wrong. Hiding the record would make every claim on the site slightly less checkable, and checkability is the whole point of publishing in a market where a wrong pip value or lot size has a peso cost.

Public also means unedited. Entries are not softened, merged or removed once they age, and a correction is never rewritten later to look more flattering. If an entry itself turns out to be wrong, it gets its own correction entry on top rather than a silent edit. The log therefore accumulates rather than tidies, and that is deliberate: a tidy log is a log someone has been through with a cloth.

The cost is that the log looks worse than a curated one would. We accept that. A reader comparing two sites on gold in the Philippines is better served by the one whose mistakes are visible and dated than by the one whose record is spotless because it was never kept. The log is not marketing and is not written to be read as reassurance.

How Each Correction Is Recorded and Dated

Every correction gets a dated entry that names the page, the sentence that changed, the old wording and the new wording. The date recorded is the date the fix went live on the page, not the date a reader wrote in and not the date we started looking. Where a reader prompted it, the entry says so without naming them. The entry stays attached to that page permanently, so the record and the page never drift apart.

The entry also records what the correction was checked against. For anything touching gold, that means the source of the lot size of 100 oz, the pip definition of 0.01, the reference price near 4275.0, or the leverage cap that applies to the entity serving the Philippines. Naming the source is what separates a correction from an opinion, and it lets the next person verify the fix without redoing the whole investigation.

Dates are written in full, with day, month and year, and no relative wording like recently or last week is used anywhere in the log. A relative date becomes false the moment time passes, which would make the log itself contain errors. The log is ordered by date so a reader scrolling it sees the newest entries first and can follow the sequence of what changed on this page and when.

How to report one

Send the page address, the sentence or figure, and what you believe the correct version is to [email protected]. A source helps, especially the broker's own document with the date you read it, but you do not need one to flag something that looks wrong.

We check the report against the source we used and against the broker's current documents. We do not promise a response time, but every report that identifies a real error leads to a dated correction on the page.

FAQ

Common questions

How do I report a mistake on a Manila Floor page?

Send the page address and the exact sentence through the contact form, and say what you believe the correct version is. The desk checks the claim against its source before changing anything. Reports that quote the sentence are handled faster, because the passage can be located without guesswork.

What happens after the desk confirms an error?

The sentence is rewritten to match the source, and the correction is noted on the corrections page so readers can see what changed. If the error affected a worked figure, the example is recalculated. The desk does not quietly delete a wrong statement, because a reader who relied on it deserves to see the fix.

Will you correct a page if the broker changes its terms?

Yes, when the change is one the desk can verify from the broker's own published material. Costs, leverage caps and platform support can change, and a page that states an old position would mislead. The desk updates the passage and records the change, and readers who spot a mismatch are asked to report it.

Do you publish corrections for small wording changes?

No. The corrections page records substantive fixes, meaning anything that changed a fact, a figure, a formula or a risk statement. Rewording for clarity, fixing a typo or tightening a sentence is not logged. The test is simple: if a reader could have made a different decision because of the old text, it belongs on the corrections page.

How long does a correction take once it is confirmed?

There is no fixed timeline, and the desk will not promise one. Confirmed factual errors are treated as the highest priority and are fixed before routine updates. Anything that depends on a source the desk cannot verify is not changed on a reader's word alone, so include a reference if you have one.