Corrections and how to report one

Errors are fixed in place

When a factual error is confirmed, the page is corrected in place and a dated note records what was changed. The original wording is not silently deleted and the page is not quietly rewritten to look as though it was always right. A reader who checks the same page later can see that a correction happened.

This matters most for figures that carry weight, such as a leverage cap, a margin example or the entity that serves South Africa. FxPro is licensed by the FCA (UK) and CySEC, and an FxPro entity holds an FSCA licence in South Africa — check which entity your own account is opened with. If we described that wrongly, the note says so.

The Difference Between a Correction and an Update on This Page

A correction fixes something that was wrong when it was published; an update changes something that was right when it was published but is no longer current. If the page said one pip is 0.1 for gold and that was always wrong, fixing it is a correction. If the page said the reference price was approximately 4275.0 and that was accurate on the date shown, changing it to a new reference price is an update. The distinction is about whether the original statement was true at the time, not whether it is true now.

Updates are dated and logged too, but they are marked as updates, not corrections. An update might add a new platform name to the list of FxPro platforms, or change the reference price to a new approximate level. It does not carry an apology or a note about reader reports unless a reader report prompted it. A correction carries a note that the previous text was wrong. A clarification is a third mark: it says the original text was not wrong but could be read in a way that misled, and it rewrites the sentence without calling it an error.

The practical difference for a reader is what they can rely on. A correction means the page previously gave a figure that should not have been used in a calculation. An update means the page is being kept current, and the old figure was valid on its date. If you used a figure from this page in a trade and later see a correction, the correction tells you the figure was wrong at the time you used it. If you see an update, the figure was right then and has moved. That is why the marks are separate.

The page does not use the word correction for a change that is merely stylistic. Rewording a sentence for clarity without changing its meaning is not logged at all. Changing a heading to match its content is not logged. The log is for changes that affect what a reader would do or believe about gold (XAU/USD) specifications, margin, leverage, funding methods or the regulator caveat. A change to the rand symbol on an amount is logged only if the amount itself changes. This keeps the log short enough to be read.

How to report one

Report an error by writing to editor@egolibarsza.com with the page address, the sentence or figure in question, and the source that shows the correct position. A link to the broker's own document is the most useful thing you can send, because it lets the desk compare like with like and check the date it was published.

We do not promise a response time in hours or days, but every report is read. If the report is right, the page is corrected and the note is dated. If the report is wrong or the source does not support it, the page stays as it is and we will explain why if you ask.

How Error, Update and Clarification Are Marked in the Log

Each log entry carries one of three marks: error, update or clarification. An error mark means the previous text was wrong and has been corrected. An update mark means the previous text was right on its date and has been changed to stay current. A clarification mark means the previous text was not wrong but could be misread, and has been rewritten. The mark is the first word of the entry, so a reader scanning the log can see the kind of change without reading the whole note. The marks are used consistently across every page.

The error mark is used for wrong instrument specifications, wrong formulas, wrong regulator wording and any number that was stated without being given. For example, if the page had stated a specific spread for FxPro, removing it would be marked as an error because no spread number was ever given. If the page had stated a leverage ratio other than up to 1:200 for retail or up to 1:500 for eligible or professional clients, correcting it would be marked as an error. The mark does not distinguish between small and large errors; both are errors.

The update mark is used when the reference price is refreshed, when a platform list changes, or when a funding method note is reworded to match the current list of local cards, bank transfers in ZAR and e-wallets. The clarification mark is used when a sentence about margin is rewritten so that the 0.10-lot example at about $85.50 is not read as a minimum deposit. The three marks are not ranked. A clarification is not a lesser correction; it is a different kind of change. The log shows the mark and the date, and the page shows the current text.

A single log entry carries only one mark. If a change both corrects an error and updates a figure, it is split into two entries with two dates if the changes are published at different times, or one entry marked error if the correction is the reason for the change. The page does not use colour or icons to mark changes; the word is the mark. This keeps the log readable in plain text and in any feed. A reader who wants only errors can filter by the word error. The marks are part of the public record.

Who Decides on a Correction and Within What Time Frame

The decision on whether a reported issue is an error rests with the person who maintains the page, not with the reporter and not with a marketing team. That person checks the report against the fixed facts the page is built on: the gold contract size of 100 oz, the pip of 0.01, the reference price of approximately 4275.0, the leverage caps of up to 1:200 for retail and up to 1:500 for eligible or professional clients, and the exact FxPro entity and regulator caveat. If the page departs from those facts, it is an error. If it does not, it is not.

The time frame is the next working day for a decision, and the same day for a clear factual error such as a wrong pip value or a wrong lot size. A report that requires checking a source, such as whether a platform list is current, may take longer, but the reader is told that it is being checked. The page does not promise an instant fix for every report. It promises that every report gets a decision, and that a decision to correct is published with a date. Reports that arrive after hours are handled the next working day.

The decision is not made by the broker and not by an affiliate. FxPro does not approve the page's corrections, and the page does not ask FxPro to confirm a spread or a commission, because those are not stated as numbers. The regulator caveat is checked against the given wording: FxPro is licensed by the FCA (UK) and CySEC, and an FxPro entity holds an FSCA licence in South Africa, and readers are told to check which entity their own account is opened with. Any change to that wording is an error correction, not an update.

If the maintainer is unsure whether a statement is an error, the default is to treat it as one and correct it, because a wrong figure on a YMYL page is worse than a missing one. The log entry then says the previous text was removed because it could not be supported by the page's facts. This is marked as an error. The decision and the date are public. A reader who disagrees can report the correction, and that report is handled in the same time frame. The maintainer's name is not published; the decision is what is public.

How a Correction Is Recorded and Dated in the Public Log

A correction is recorded as a dated entry in the public log that names the page, the sentence or figure that was wrong, the corrected text, and the date the correction went live. The date is the date the corrected page is published, not the date the report arrived. Each entry carries a short reference number so a reader can point to it. The entry does not include the reporter's name unless they ask to be credited, and it does not include an estimate of how many readers saw the error.

The log entry is written in plain English and states what the page said before and what it says now. For a wrong pip value, the entry would say the page previously stated one pip as 0.1 and now states 0.01, with the date. For a wrong regulator caveat, it would quote the old wording and the new wording. The entry does not argue with the reporter or explain internal workflow. It is a record, not a defence. Rand amounts, if any, are shown with the R symbol and the date they were checked.

Dating is by calendar date in South African standard time. If a correction is made on a Friday afternoon, it is dated that Friday, not the following Monday. If a correction is made in stages, each stage gets its own date. The log is ordered newest first, and each entry links to the page section it affects. A reader who wants to see the full history of a page can filter the log by page name. The log itself is not edited after publication; a later correction to the same page is a new entry.

The record is kept even if the page is later rewritten. If a page is retired, the log entry remains and the page link points to an archived note saying the page is no longer live. This means a reader who bookmarked a correction can still find it. The log does not show drafts or internal notes. It shows only corrections that were published. The date is the anchor: a reader can see whether a figure was corrected before or after a market event, which is often the reason they are checking.

Why the Correction Log Stays Public and Who Can Read It

The log stays public because a reader who uses a page to size a gold position or check a leverage cap needs to know whether the page has been wrong before. A private log would let the page present itself as always correct. A public log shows the dates and the nature of every correction, so a reader can judge whether a figure they are relying on has been stable. The log is readable without an account, without a login and without payment. It is linked from the page it affects.

Public logging also keeps the page honest about the limits of its facts. The page is built on a fixed set of facts: gold at 100 oz per lot, one pip at 0.01, a reference price of approximately 4275.0, leverage up to 1:200 for retail and up to 1:500 for eligible or professional clients, and the FxPro entity and regulator caveat. When a reader reports something outside those facts, the public log shows that the page did not invent a number. That protects both the reader and the page.

The log is not a marketing page. It does not list praise or testimonials. It does not show how many people visited. It shows only corrections, updates and clarifications, with dates. A reader in South Africa who checks the log before using a rand amount or an EFT funding note can see whether that note has changed. The log does not name individual readers unless they ask. It does not include email addresses or account details. It is a record of the page's changes, not of the people who read it.

Keeping the log public also means the page can be checked by anyone, including someone who disagrees with it. If a reader thinks a correction was wrong, they can report that, and the report is handled the same way. The log does not have a comments section, because comments would mix opinion with record. The record stands on its own. A reader who wants to discuss a correction can use the report route, and if the discussion changes the page, that change is logged. The public log is the single place where changes are visible.

A changed condition is a re-check

A condition that has merely changed since the check is a re-check, not an error. If a broker changes its leverage cap, its funding routes or the entity it places South African clients with, the earlier page was accurate when it was written. The fix is to re-read the source and update the page with a new date, not to treat the old sentence as a mistake.

The distinction protects the reader as much as the desk. It means a dated figure can be trusted for the date it carries, and it means the correction log stays about genuine mistakes rather than routine market and policy movement. Where a figure is likely to move, the page says what it depends on.

What Counts as an Error Worth Logging on a XAU/USD Page

An error worth logging is a factual statement on the page that is wrong in a way that could change a reader's trading decision or calculation. That includes a wrong instrument specification, such as stating a gold pip as 0.1 instead of 0.01, or a wrong lot size such as 10 oz instead of 100 oz. It also includes a wrong reference price that is presented as current when it is not, or a regulator caveat that misstates which entity serves South African clients. A typo that does not affect meaning is not logged as an error; it is fixed quietly.

An error is also worth logging when the page states a number it was not given, such as a specific spread, commission, swap or minimum deposit for FxPro. Because those figures depend on the account and the market, any stated number is an error by definition. The same applies to leverage: the page may state up to 1:200 for retail and up to 1:500 for eligible or professional clients, but any other ratio is an error. A missing rand symbol on a ZAR amount is not an error; a wrong rand amount is.

A reader report is not automatically an error. It becomes one when the page text can be checked against the source facts and found wanting. If the page says a 0.10-lot gold position needs about $85.50 margin at 1:200 and a reader says it needs $171, the page is checked against the stated leverage cap and the 100 oz lot size. If the page is right, no error is logged and the reader is told why. If the page is wrong, it is logged and corrected in place.

An error worth logging must be specific enough to point to. 'The page is confusing' is feedback, not an error. 'The page says one pip is 0.01 but the example uses 0.1' is an error. The distinction matters because the log is public and dated, and it should contain only claims that can be verified against the facts the page is built on. Vague dissatisfaction is answered by email but does not enter the log. This keeps the log useful to readers who want to see what changed and why.