Corrections and re-checks

How an error is fixed

An error is fixed in place and marked with a dated note saying what changed. The page is not deleted and the old wording is not quietly removed, because a reader who relied on the earlier version should be able to see what moved and when. The note sits with the corrected text, not in a separate archive.

Corrections are made for factual errors: a wrong figure, a misread document, a regulator status stated incorrectly, or a funding route attributed to a broker that does not list it. Where a page has been corrected, the date of the correction is shown next to the note so the reader can judge how current the text is.

The Three Change Types and the Mark Each One Carries

Every change is marked as one of three types: Error, Update or Clarification. An Error mark means the previous text was wrong and should not be used; the log shows the old and new wording and the date fixed. An Update mark means the previous text was correct when published but the underlying fact changed; the log shows the old and new values and the date of the change. A Clarification mark means the previous text was accurate but could be misread; the log shows the added or reworded sentence and the date.

The marks appear in two places: as a label in the log entry and as a superscript-free plain-text tag at the end of the affected paragraph, such as [Clarification, 14 March 2025]. The tag is plain text, not a symbol, so it survives copying and screen readers. A paragraph can carry more than one tag if it has been changed more than once, and the tags appear in date order. The tag tells a reader that the paragraph has a history and points them to the log for the detail.

The three types are not interchangeable. Marking an error as a clarification would understate the problem, and marking an update as an error would wrongly suggest the original text was false. For a UAE reader, the difference matters when the change touches leverage or funding: an Error on a leverage figure means the old figure was wrong, while an Update means the cap itself moved. The log uses the exact words Error, Update and Clarification, and the page tags match those words.

Correction Versus Update: How the Two Differ in Practice

A correction fixes something that was wrong when it was published; an update changes something that was right when published but is no longer current. For example, if the page said gold pip value is 0.10 and it is actually 0.01, that is a correction because the original statement was false. If the page said the maximum leverage available in the UAE is up to 1:500 and that figure is later revised by the regulator, changing it is an update because the original was accurate at the time. The log marks the two differently.

Updates are dated from the moment the underlying fact changes, not from the moment the page is edited, and the log notes the source of the change, such as a regulator notice or a broker announcement. Corrections are dated from the moment the page is fixed, because the error had no valid start date other than publication. A reader comparing the two can see whether the page was wrong or simply behind. Both are logged publicly, but only a correction implies the earlier text should not be relied on.

The distinction matters for trust: an update says the world moved, a correction says we misstated it. For a UAE trader using the $85.50 margin example for a 0.10-lot gold position, an update would be a change to the leverage cap that alters the margin, while a correction would be a wrong multiplication in the original example. The log uses the words 'Correction' and 'Update' as labels, not synonyms, so the reader is never left guessing which happened.

How Each Correction Is Recorded and Dated on the Page

A correction is recorded as a dated entry in the public log at the foot of the page, showing the date the fix went live, the section heading, the old wording, the new wording, and the category (error, update or clarification). The date is the publication date of the corrected page, not the date a reader reported it. For a UAE reader checking a margin example such as the $85.50 needed for a 0.10-lot gold position at 1:500, the log shows when that figure was last confirmed and what it replaced.

The date format is day, month, year in English, for example 14 March 2025, so there is no ambiguity between UAE and international readers. Each entry carries a short reference number, and the same number appears in the page's version note, so a reader can match a paragraph to its correction. If a correction changes a number, the old number stays visible in the log with a strikethrough-free plain-text note saying it was replaced, so the history remains readable without formatting tricks.

Corrections are dated even when the error was found within minutes of publication, because the log is a record of what changed, not a measure of how long the error existed. If a correction is itself corrected, a new dated entry is added rather than editing the old one, so the sequence is preserved. The log does not use relative dates such as 'last week' because those go stale; every entry carries an absolute date that remains true when read later from the UAE or anywhere else.

Why the Correction Log Stays Public and Permanent

The log stays public because a trading page that hides its mistakes gives a UAE reader no way to judge whether the current text is reliable. If a page can silently change a margin figure or a regulator caveat, a reader cannot tell whether the number they relied on last week was ever correct. A public log makes the page auditable: every change is visible, dated, and attributable to a category, so trust is based on evidence rather than on a claim of accuracy.

Public logging also protects against the slow drift that affects financial pages, where small edits accumulate until the page no longer matches its original facts. By requiring every change to appear in the log, the page makes drift visible and costly to hide. For example, if the reference price of 4275.0 is updated, the log shows the old and new values, so a reader can see the page is maintained rather than static. The log is not a marketing feature; it is the record that makes the rest of the page checkable.

The log is permanent because deleting an entry would break the chain of dates that gives the record its value. A reader who cited a figure on a given date needs to be able to return later and see what the page said then. If entries could be removed, the log would only show the version the publisher prefers, which is the opposite of a record. Permanence applies to the log entries themselves, not to the page text, which is corrected in place while the history remains.

Who Decides a Change Is Needed, and Within What Time

The decision to log a change is made by the page's editor, who is the only person authorised to publish a correction, update or clarification. A reader report, an internal check or a source notice can trigger a review, but the editor decides the category and the wording. The editor aims to decide within two working days of a report reaching the review queue, and to publish the change and its log entry within five working days, unless the change depends on a source that has not yet confirmed the new fact.

The time limit is measured in working days because a UAE reader may report an issue at the start of the local week, and the review follows the publisher's calendar, not the reader's. If a change is urgent because it affects a risk warning or a regulator caveat, the editor aims to publish within one working day, with the log entry published at the same time as the fix. The editor does not publish a change without a log entry, because an unlogged change would break the public record.

The editor's decision is recorded in the log with the category and the date, but not with a personal name, because the log is about the page's history, not about individuals. If a reader disagrees with a decision, the disagreement does not itself change the log; a new report can trigger a new review, and if the editor reverses a previous decision, the reversal is logged as a new entry rather than an edit to the old one. This keeps the decision trail visible without attributing it to a named person.

How to report one

Report a correction to editor@liwastrikesae.com, naming the page and quoting the sentence you believe is wrong. If you have the broker document that shows the correct position, attach it or paste the relevant lines and the date you read them. A report with a source is checked against that source; a report without one is checked against the broker's own documents.

The desk does not promise a response time in hours or days, and it does not pay for corrections. What it does commit to is a check: if the document supports the reader, the page is corrected and dated; if it does not, the reader is told why the text stands.

How a Correction Is Recorded and Dated in the Public Log

A correction is recorded as a dated line in the public log on the same page, written at the moment the fix goes live, not when it was first noticed. The entry carries the date the corrected text was published, the section it touched, and a short plain description of what was wrong and what it now says. The date is the publication date of the fix, because that is the point at which a reader could have seen the accurate version.

Each entry is written so it stands alone without the old text. It names the claim that changed, for example a leverage figure that did not match up to 1:500 on standard forex accounts, within DFSA/SCA-compliant limits, and states the corrected version. Where the error affected a worked example, such as the margin figure for a 0.10-lot gold position, the corrected arithmetic is shown so a reader can recheck it. Entries are not edited after publication; a later change gets its own new dated line.

Dating is deliberately conservative. If a fix is published on one day and verified the next, the log shows the publication date, and any follow-up appears as a separate entry rather than a backdated edit. This means the log can be read as a sequence a reader can audit, with each date tied to a visible version of the page. It also means no entry ever claims a date earlier than the moment the corrected wording actually appeared to the public.

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

A condition that has merely changed since the page was checked is a re-check, not an error. If a broker alters its leverage cap, its funding list or its entity for UAE clients after the date on the page, the earlier text was accurate when written. The fix is a fresh read of the documents and a new date, not a correction note.

This distinction matters for costs, which move constantly. A spread, commission or swap quoted as a number would be out of date almost immediately, which is why those are described by what they depend on rather than as fixed figures. Where a page does carry a number, it is dated, and a reader should confirm it with the broker before acting.

What Qualifies as a Loggable Error on This Page

A loggable error is any statement that misstates a verifiable fact, such as the wrong instrument code, lot size, pip value, reference price, regulator name, or funding method, or that presents a cost as fixed when it depends on conditions. For gold (XAU/USD), writing that 1 lot equals 10 oz instead of 100 oz, or that one pip is 0.10 instead of 0.01, is a loggable error because it is checkable against the stated facts. A typo that changes no meaning is not logged.

Errors also include omissions that change a reader's decision, such as failing to state that leverage of up to 1:500 is a cap and not a target, or leaving out the regulator caveat that FxPro is licensed by the FCA (UK), CySEC and FSCA. A missing risk warning on a YMYL trading page is a loggable error because it can lead a UAE reader to overestimate safety. A style preference, a different opinion on emphasis, or a wording choice that remains accurate is not an error and is not logged.

A claim that a spread, commission, swap or minimum deposit is a specific number is a loggable error because those figures are not in the approved facts and vary by account and market. For example, stating that gold spreads are 20 cents per lot when no such number is given is loggable. So is naming a funding method not on the approved list, such as a method not among cards, bank transfer or e-wallets. The test is whether the statement can be checked against the facts and found wrong or unsupported.

Why Nothing on This Page Is Ever Deleted From the Record

Nothing is deleted because a removed entry destroys the only evidence a reader has that the page changed, and a corrections page that hides its own history is worth less than no page at all. Old entries stay visible even after the wording they describe is long gone. A reader who quoted an earlier figure, or acted on it, can still find it in the log and see what replaced it and when. Deletion would erase that trail.

This matters most where money is involved. If an earlier version of this page misstated the UAE leverage cap, or attributed the licence incorrectly, a reader may have sized a gold position on that basis. Keeping the entry visible lets them trace the change and re-check their own assumptions. The log therefore holds superseded text as history, clearly marked as superseded, rather than removing it. The current page shows the corrected wording; the log shows what it replaced.

The rule extends to entries that later look unimportant. A clarification logged months ago stays even if the wording it addressed has since been rewritten entirely. Pruning old entries would make the log a curated summary rather than a record, and a reader could no longer tell whether a gap meant nothing happened or something was quietly removed. Permanence is the point: the log is only useful if a reader can trust that what is absent never existed.

What Counts as an Error Worth Logging on a Gold Page

An error worth logging is a statement on this page that the underlying source contradicts, not a statement you would have phrased differently. If a figure, a lot size, a pip value, a leverage cap or a regulator name is wrong against the source we relied on, it is an error. If a sentence is merely awkward, or a section order feels off, it is not an error and does not enter the log. The test is factual contradiction, checked against the source, not preference.

For gold (XAU/USD) the bar is arithmetic and citation. One standard lot equals 100 oz and one pip equals 0.01, so any worked example that produces a different pip value than the formula allows is a loggable error. Likewise, quoting the UAE leverage cap as anything other than up to 1:500 on standard forex accounts, within DFSA/SCA-compliant limits, is an error. Naming a funding method we do not list, or attributing a licence to the wrong entity, also qualifies because it misleads a reader acting on it.

Numbers we were never given cannot be wrong by omission, so their absence is not an error. If the page does not state a spread, a commission, a swap rate or a minimum deposit as a figure, that is deliberate, not a gap to log. A reader who wants those numbers should treat them as broker-dependent and confirm them with FxPro directly. Logging is reserved for claims that are demonstrably false against a named source, which keeps the record short and trustworthy.