Corrections Policy

How we fix errors

If we publish a factual error, we correct the text on the same page and add a short note with the date of the correction. We never silently edit a page to remove a mistake, because readers deserve to know what changed.

The note is placed at the end of the section where the error appeared, and it states what was wrong and what the correct information is. We do not rewrite history.

How to report an error

Email editor@practiceounce.com with the page URL, the sentence you believe is wrong, and why you think it is wrong. If you have a source document, please mention it, because we check against primary sources.

We review every report, but we may not reply immediately. If we agree that an error was made, we will correct it and add a dated note. If we disagree, we will explain our reasoning if time allows.

Changed conditions are not errors

Brokers change spreads, commissions, and leverage caps regularly. If a figure we published was correct on the date we read it but has since changed, that is not an error on our part; it is a re-check.

When we learn of a change, we update the page and add a note with the new date. We do not treat a broker's update as our mistake, but we do try to keep our pages current.

What Counts as an Error Worth Logging

We log an error when a stated fact about gold trading on Practice Ounce is objectively wrong and could mislead a reader making a trading decision. This includes incorrect instrument specifications such as lot size, pip value, or reference price; a wrong leverage cap for UAE accounts; a funding method listed that is not actually available through FxPro Global Markets MENA Ltd.; or a regulator caveat that misstates FxPro’s licensing. A subjective judgment like whether a spread is attractive is not logged as an error because it is not a checkable fact.

We also log an error when a number we have been given changes in the source data and the old figure remains on a page without a date or update note. For example, if the reference gold price near 4275.0 moves and a worked margin example still uses the old price without saying it is illustrative, that is a factual inconsistency worth logging. A missing risk warning on a page that discusses leverage is logged as an error because it could understate the danger of trading gold with borrowed money.

We do not log every typo or style issue. A broken link, a spelling mistake, or a clumsy phrase does not go into the correction log unless it changes the meaning of a financial fact. The test is simple: could a reasonable reader in the UAE act on the wrong information and lose money or break a rule? If yes, it belongs in the log. If it is cosmetic, we fix it silently and do not burden the public record with noise.

How a Correction Is Recorded and Dated

Every logged correction gets a dated entry that shows the exact text before and after the change, so readers can see what was wrong and what is now true. The entry uses the publication date of the correction, not the original article date, and it includes a short plain-English reason for the change. We do not hide behind vague wording like “updated for accuracy”; we say precisely which fact was wrong, such as a pip value or a leverage ratio.

The correction is applied to the live page immediately, and the log entry links to the affected section. If the error appeared in a worked example, we recalculate the example with the corrected input and show the new result. For instance, if a margin figure for a 0.10-lot gold position was wrong, we replace it with the correct AED amount based on the stated reference price and leverage cap, and we keep the old figure in the log for transparency.

We date the correction using the UAE time zone and format it as day month year, so local readers see a familiar calendar. The log is ordered newest first, and each entry carries a unique reference number that can be cited in an email to our support team. This makes the record auditable and prevents a correction from being silently overwritten later. A reader who saw the error yesterday can prove today that we fixed it.

The Difference Between a Correction and an Update

A correction fixes a factual mistake that was wrong at the time of publication, while an update adds new information that was not known or not relevant before. If we originally wrote that FxPro is licensed by the FCA, CySEC and FSCA, and that statement was true then and remains true now, no correction is needed. But if we add that FxPro Global Markets MENA Ltd. serves the UAE, that is an update because it is new context, not a fix of an error.

We keep corrections and updates separate in the log because they serve different reader needs. A correction tells you that something you may have relied on was false and is now corrected; an update tells you that something changed or became clearer, such as a funding method being added or a regulatory note being expanded. Mixing them would make it hard to judge whether past advice was wrong or simply incomplete.

For gold trading content, market conditions like the reference price near 4275.0 are inherently time-sensitive and are always framed as illustrative. A change in that price is not a correction because the old number was never presented as a permanent fact. However, if a page failed to label the price as illustrative and a reader could treat it as current for weeks, that mislabeling is a correction, while the price change itself is an update.

Why the Correction Log Stays Public

We keep the correction log public because UAE readers who trade gold are making high-risk decisions with their own money, and they deserve a complete record of what we got wrong and when we fixed it. If we hid our corrections, a reader who acted on a wrong margin example might never discover the error and could repeat it. Public logging is a basic honesty mechanism for financial content.

A public log also builds trust through accountability. Anyone can see that we do not quietly edit pages to look better; every substantive change is dated and explained. For a beginner learning about XAU/USD, this matters more than for an expert, because a beginner is less likely to spot an error on their own. The log is our promise that we will not let a mistake stand without a visible correction.

In the UAE, where trading gold with leverage up to 1:500 is available within DFSA/SCA-compliant limits, the stakes are high. A wrong pip value or lot size can change position sizing and risk. By keeping the log open, we give readers the tool to verify our trustworthiness before following any advice. It is not a legal requirement in most cases, but it is the right thing to do for a financial education site.

How Corrections Affect Existing Worked Examples

When a correction changes an input used in a worked example, we recalculate the entire example and show the corrected result in place of the old one. For instance, if we had used a wrong leverage cap for a gold margin calculation, we redo the math using the stated cap of up to 1:500 on standard forex accounts within DFSA/SCA-compliant limits. The old example is not left on the page; it is moved to the correction log with a clear before-and-after.

We also check every other page that references the corrected fact. If the pip value for gold was wrong on one page, we search the site for that same wrong number and fix it everywhere, logging each location. This prevents a reader from seeing a correct figure on one page and a stale wrong figure on another. For a site about one instrument, consistency is non-negotiable.

A corrected worked example keeps the same structure but uses the right numbers, so readers can compare the old and new outputs. We never delete an example just because it was wrong; we fix it and explain the change. That way, a beginner who saw the old example can understand exactly what was wrong and why the new result is different, without having to recalculate the position themselves.

What goes into the correction log at Practice Ounce

An error is worth logging when it changes a fact a UAE reader could reasonably rely on for a trading decision, such as a wrong gold contract size, a wrong pip value, or a regulator caveat that misstates FxPro’s licensing. We log a wrong XAU/USD price reference if it is materially off from the market, but we do not log a price that moved a few cents after publication; markets move constantly and that is not an error. We also log any instruction that could cause a reader to miscalculate margin, such as a wrong worked example at the maximum leverage available in the UAE, because that number is a cap and not a target.

A factual mistake in our local funding guidance is logged when it names a method we do not support, such as a cheque or a local payment app not in the list of cards, bank transfer, or e-wallets. We do not log a funding method that works but is slower, because speed is not a factual error. If we wrote that a UAE bank transfer settles instantly when it does not, that is logged, because a reader may plan around the wrong timing. We also log an error in our currency handling if we state a cost in USD without the AED equivalent when the context requires it, since readers in the UAE think in AED.

We log an error when a definition is wrong, because this site exists to make trading clear for beginners. If we define a pip as 0.0001 for gold, that is logged immediately; for XAU/USD one pip is 0.01 and one lot is 100 oz. We also log a mistake in the regulator caveat if we add or remove a regulator, because FxPro is licensed by the FCA (UK), CySEC and FSCA, and that exact list matters to a UAE reader choosing a broker. We do not log a difference of opinion, a style choice, or a simplification that is still accurate.

How a correction is recorded and dated on this page

Every correction is recorded as a public entry on this page with the date it was made, not the date the error was found, because the date of the fix is what tells a reader how current the information is. We write the entry in plain English, with the section name, the old wording, the new wording, and a short reason. For example, if a worked example used a wrong margin at the maximum leverage available in the UAE, we state that the old figure was corrected to about $85.50 margin for a 0.10-lot gold position at the cap, and we explain that the cap is not a setting to aim at.

The date format is day, month, and year, with the UAE time zone, so a reader in Dubai or Abu Dhabi can see exactly when the change went live. We do not backdate a correction to make it look earlier, and we do not hide an old date behind a new one. If a correction is made to a page that has a worked example, we update the example and note in the log that the example was corrected, so a reader who saw the old version knows it was wrong. We also record a correction even if only one sentence changed, because a small error can have a large effect on a trading decision.

We date the correction log entry with the same date as the change on the live page, and we do not use a range of dates or a vague 'recently'. If the error was live for three days, we state that it was live for three days, because a reader who acted on it in that window needs to know. We also keep a visible link to the log from the page footer, so a reader can always find the latest corrections without searching. This record is permanent; we do not delete old entries, we only add new ones.

The difference between a correction and an update at Practice Ounce

A correction fixes a factual mistake that was wrong when it was published, while an update changes a fact that was right when it was published but became outdated later, such as a change in FxPro’s regulator list or a new local funding method. We do not call an update a correction, because that would mislead a reader into thinking the original text was faulty. For example, if the maximum leverage available in the UAE changes from the current cap on standard forex accounts, that is an update, not a correction, because the old number was correct at the time of writing.

We apply updates without adding an entry to the correction log, because the log is only for errors. An update is noted on the page itself, usually with a 'last updated' date, but it does not carry the same weight as a correction. If we add a new e-wallet to the list of local funding methods, that is an update, because the old list was complete when it was published. If we remove a method that never worked, that is a correction. The distinction matters because a reader who sees a correction log entry knows that the previous text was wrong, and they should disregard any notes they took from it.

A correction can also be an update if the same change fixes an error and reflects a new fact, but we log it as a correction with a note that the new fact was also added. For example, if we had stated a wrong pip value for gold and at the same time the reference price changed, we correct the pip value and update the price, and we log the correction with both changes explained. We never use the word 'update' to hide a correction, and we never use 'correction' to describe a simple refresh, because a beginner reader in the UAE may not be able to tell the difference without a clear label.

Why the correction log stays public for UAE readers

The correction log stays public because trading gold with leverage is high risk, and a reader who acted on a wrong number could have lost money. If we wrote a wrong margin requirement at the maximum leverage available in the UAE, and a reader opened a position based on that, they could have been stopped out. The log lets them see that the number was wrong and when it was fixed, so they can review their own trades. We do not hide corrections because transparency is the only way a beginner reader can trust that the page they are reading now is correct.

A public log also protects readers from old screenshots or cached versions of a page. If a reader saved a page that said the pip value for gold was 0.0001, and later we corrected it to 0.01, the log tells them that the old version was wrong and the new version is right. Without the log, they might keep using the wrong number. We also keep the log public because FxPro is licensed by the FCA (UK), CySEC and FSCA, and a reader in the UAE may want to verify that our regulator caveat has not been silently changed.

Finally, the log is public because this site is for beginners, and beginners need to see that errors happen and are fixed openly. A hidden correction would be a second error: it would leave a reader believing a false number. We log every correction, even a small one, and we keep the log in plain English with no jargon, so a reader can understand exactly what changed and why. This is not a legal requirement for a trading education site, but it is the only way to write about high-risk instruments like gold without misleading the people who read us.