Corrections policy

Errors are fixed in place

When a page is wrong, the wrong text is corrected on the page and a dated note records what changed. We do not delete the page and republish it as if the error never existed, because a reader who relied on the old version deserves to see what moved.

A correction note is written in plain words: what the page said, what it says now and the date the change was made. The same rule applies to a figure, a heading or a sentence about which entity serves Ghana.

How to report one

Send the page address, the sentence you believe is wrong and, where you have it, the document that shows the correct position to editor@accrastationgh.com. A link to a broker's own terms or a regulator's page is the most useful thing you can include.

The desk checks the claim against the source before changing anything. If the claim holds, the page is corrected and the note is dated; if it does not, you will be told why the page stands.

The Difference Between a Correction and an Update

A correction fixes something that was wrong; an update changes something that was right when written but is no longer current. If a page said a 0.10-lot gold position needs about $85.50 margin and that figure was correct under the cap at the time, a later change to the cap makes the sentence outdated, not erroneous. We update it and say the condition changed. Calling that a correction would falsely suggest we published a mistake, which misleads readers about the page's reliability.

The distinction matters because the two are marked differently and read differently. A correction tells a reader that a prior statement should not be trusted and has been replaced. An update tells a reader that the statement was accurate for its date and the world has moved. For a Ghana audience, an update might note that the regulator caveat still requires confirming any broker on the SEC Ghana licensed operators list, even though the wording was refreshed. The underlying caution stands; only the presentation changed.

We keep the two apart in the log so the page's error history is not inflated by ordinary maintenance. A page with many updates is not a page with many mistakes. Conversely, a correction is never relabelled as an update to soften it. When a change is both, because an outdated sentence also contained a wrong figure, we log it as a correction and note the condition change in the same entry. One entry, two facts, clearly stated.

A changed condition is not an error

If a broker has changed its funding route, its entity or its terms since we read its documents, the page was not wrong when it was written. That is a re-check, and it is handled by updating the page and noting the date the new check was made.

The distinction matters because it tells a reader how much to trust a date on the page. A dated note means the desk has looked again; a correction means the desk got something wrong the first time.

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 and has been replaced; the log shows the old and new text and the confirmation date. An update mark means a condition changed, such as a cap or a funding detail, and the page now reflects the new condition; the log says what changed and when. A clarification mark means the original was accurate but ambiguous, and the wording has been made plainer without changing the meaning.

The marks appear in the page log, not as inline badges scattered through the text, so the reading experience stays clean. Each log line begins with the kind, then the date, then the affected section, then a short description. For example: clarification, 12 March 2025, margin example, reworded to state that the $85.50 figure is at the applicable cap and is not a target. That format lets a reader scan for the kind of change they care about without reading every entry.

We do not use a fourth category for cosmetic edits such as fixing a typo that does not change meaning. Those are made silently and are not logged, because logging them would bury the substantive changes. If a typo changes a number, a currency code or a regulator name, it is an error and is logged as one. The three marks are kept strict so that a reader can trust that an unmarked change did not alter any fact they might rely on.

What Counts as an Error Worth Logging

An error worth logging is a factual statement on a page that is wrong against the source we relied on at the time of writing, not a matter of taste or a later market move. If a page says a 0.10-lot gold position needs about $85.50 margin at the applicable cap and the arithmetic or the cap reference is wrong, that is a loggable error. A typo that changes a number, a regulator name, a currency code or a formula also qualifies. A sentence a reader merely dislikes does not.

Errors that affect a decision are logged first: wrong lot size, wrong pip value for gold (pip = 0.01), wrong margin figure, wrong funding route such as naming a method that is not MTN Mobile Money, or a regulator caveat that drops the SEC Ghana check. Presentation issues, such as a broken table on a phone, are fixed but not logged as errors. The test is simple: would a reader acting on this sentence make a different, worse decision? If yes, it is worth logging.

We do not log an error simply because a reader disagrees with the risk framing or because a price reference of ≈4275.0 later looks stale. A stale reference is handled as an update, not an error. We also do not log an error when the original statement was correct under the facts we had and a source later changed; that is the silent-source case handled separately. Logging is reserved for statements that were wrong when published or became wrong through our own edit.

How a Correction Is Recorded and Dated

A correction is recorded as a dated entry in the page's log, showing the date the error was confirmed, the sentence or figure that was wrong, the corrected wording, and the source used to confirm the fix. The date is the confirmation date, not the date a reader first mentioned it. If a reader reports a wrong margin figure on a Monday and we confirm it against the applicable cap on Tuesday, the log carries Tuesday. That keeps the record honest about when we actually knew.

Each entry is tied to the page and to the section it affects, so a reader can match the log line to the visible text. Where the fix changes a number, the old number and the new number both appear in the entry; we do not quietly replace one figure with another. For gold pages, that means the lot size, the pip definition (0.01) and any margin example such as the $85.50 figure are shown before and after. Dates are written in full, for example 12 March 2025, to avoid day-month confusion.

Corrections are dated in the site's own time record and are not backdated to make a page look cleaner. If a correction takes three days to confirm, the log shows the confirmation date and, where useful, the report date alongside it. We do not attach a time of day unless the change is time-sensitive, which for evergreen explainer pages it usually is not. The date is the anchor; the wording of the entry is kept short so the change is easy to audit.

Why the Log Stays Public

The log stays public because a reader cannot judge a page's reliability without seeing what changed and when. A trading explainer that quietly edits a margin example or a regulator caveat gives no way to tell whether the current text is the original or the fifth revision. A public log lets a reader in Accra check the date of the $85.50 margin example and decide whether it still reflects the cap that applies to the entity serving Ghana. That check is the point.

Public logging also keeps us honest about the difference between a correction and an update. If the log were private, an outdated figure could be refreshed and presented as if it had always been current. In public, the old and new wording sit side by side, and a reader can see that a condition changed rather than a mistake being hidden. For high-risk material such as leverage and margin, that visibility is not optional; it is part of treating the reader as an adult.

The log does not expose reader reports or personal details. A report from a reader using MTN Mobile Money to fund an account is acknowledged in the entry only as a reader report, with no name, number or account detail. The public record is about the page, not about the person who spotted the problem. That balance lets the log stay open without turning a correction process into a surveillance of the people who use the site.

Who Decides, and in What Time

The decision to log a change rests with the person who maintains the page, acting on a report or on their own check against the source. There is no committee and no author byline to appeal to; the standard is whether the statement matches the facts we are allowed to state. For a margin example, that means checking the lot size, the pip definition of 0.01 for gold, and the applicable cap before deciding whether the $85.50 figure is still correct. The decision is recorded with the entry.

Timing depends on what is being checked. A clear factual error, such as a wrong currency code or a missing SEC Ghana caveat, is confirmed and logged as soon as it is verified, typically within the same working day. A change that requires checking a source we cannot see immediately may take longer, and the log shows the confirmation date rather than the report date. We do not promise a fixed number of hours, because the honest answer is that it depends on the source.

No change is made to a page's substantive facts without a log entry created at the same time. That rule is what makes the timing meaningful: a reader never sees a corrected figure without a dated line explaining it. If a correction is urgent because a reader could act on a wrong margin figure, the page text is fixed first and the log entry follows immediately after, not days later. The two travel together.