Corrections policy

How an error is fixed

An error is corrected on the page where it appeared, and a dated note is added next to the corrected passage saying what the earlier wording said. The page is never quietly rewritten and presented as if the mistake had not happened.

The dated note stays visible. A reader who returns to a page after a correction can see the earlier version, the corrected version and the date the change was made.

How to report one

Report an error by writing to editor@thikasignupke.com and naming the page, the sentence and, where possible, the broker document that shows the correct figure. A report with a source is checked fastest.

A report is checked against the broker's own document before anything is changed. If the page is right and the report is mistaken, the reader is told why rather than being ignored.

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

A broker's terms, platform list or funding route can change after a page was checked, and that is a re-check rather than an error. The original page was accurate on the date it was read, and the date is printed on it for exactly this reason.

When a reader points to a condition that has since changed, the page is re-checked against the current broker document and updated with a new date. The earlier reading is not rewritten as a mistake.

What Counts as a Loggable Error on a Gold Price or Margin Figure

A loggable error is a statement on the page that is factually wrong against the source we cited or against the arithmetic we published, not a statement a reader merely disagrees with. For gold (XAU/USD), that means a pip value, lot size, margin formula or worked figure that does not reconcile: if we say 1 lot = 100 oz and one pip = 0.01, then any example that contradicts those constants is an error. A wrong KSh amount, a mislabelled regulator, or a leverage cap attributed to the wrong entity also qualifies because each is checkable against the facts we hold.

A loggable error must be specific enough to point at, because vague discomfort cannot be corrected or dated. If a paragraph says a 0.10-lot gold position needs about $85.50 margin at the applicable cap, a reader can check that against the cap and the contract size; if the arithmetic fails, we log it. By contrast, a reader who feels the risk warning is too strong, or who prefers a different funding route to M-Pesa, is raising an editorial preference. That is noted but it is not an error, and it does not enter the correction log.

Typos that change meaning count, while typos that do not change meaning are fixed quietly and still noted. If a sentence says a pip is 0.1 instead of 0.01, the number is wrong and the correction is logged because a reader could size a trade from it. If a word is misspelled but the instrument code, the lot size and the margin figure are intact, we correct the text and record it as a minor fix rather than an error. The test is always whether a reader acting on the sentence would be misled about gold, margin, leverage or the regulator.

How Each Correction Is Recorded and Dated So the Old Wording Remains Traceable

Every correction is recorded as a dated entry that names the page, the exact wording that was wrong, the corrected wording, and the source or arithmetic that settled it. The date is the date the correction goes live, not the date a reader first wrote in, because the page was still wrong until the fix was published. For a gold margin example, the entry would quote the old figure and the new figure alongside the contract size and the leverage cap used, so a later reader can redo the sum without asking us.

The entry is dated to the day and kept in the same sequence as every other entry, so the log reads as a timeline rather than a set of scattered notes. We do not backdate an entry to make a page look as if it was always right, and we do not merge two corrections into one entry if they were published on different days. Where a correction touches a KSh amount or a M-Pesa funding reference, the entry states the old and new wording in full so the change is visible without opening an earlier version of the page.

Dating also fixes the boundary between what a reader saw and what we now say. If you read the page on a given date and acted on a figure that we later corrected, the dated entry lets you see precisely what the page said when you read it. That matters for a YMYL page about gold because a margin figure or a leverage cap misread can affect a real position. A correction without a date would blur that boundary, so the date is part of the correction, not an optional label added afterwards.

Correction Versus Update: One Fixes a Wrong Statement, the Other Changes a Right One

A correction fixes a statement that was wrong when it was published; an update changes a statement that was right when it was published but is no longer current. If we wrote that a 0.10-lot gold position needs about $85.50 margin at the applicable cap and the arithmetic was wrong, that is a correction. If the applicable cap itself changes and the same example now needs a different margin, the old sentence was accurate for its date and the new sentence is an update. The two are marked differently because they answer different reader questions.

The distinction matters because a correction admits a mistake while an update records a change in the world. Mixing them lets a page quietly rewrite its own history: a wrong figure could be presented as merely out of date, which is softer than the truth. On this page an error is labelled as an error even when the underlying cause was a source that moved, because the reader still saw a wrong number. An update is labelled as an update only when the earlier statement matched the facts available on its publication date.

Both are dated and both stay visible, but only the correction carries the old and new wording side by side as a matter of course. An update may simply state the new position with the date it took effect, because there is no wrong wording to preserve. For gold, an update might concern a change in the entity serving Kenya or a change in the leverage cap; a correction would concern a misstated pip value, a wrong lot size or a margin example that did not reconcile with the cap we had already published.

Why the Correction Log Stays Public Instead of Being Kept Internally

The log stays public because a reader cannot judge a page about gold margin and leverage without seeing what the page used to say and when it changed. Trading is high-risk and the numbers are checkable, so a private log would ask readers to trust a claim they cannot inspect. A public log lets you compare the current wording with the earlier wording and decide for yourself whether the correction was adequate. That is the same standard we apply to the facts themselves: show the working, not just the conclusion.

A public log also keeps the correction honest, because an entry written for readers is harder to soften than an internal note. When the entry must quote the old wording and the new wording, the size of the mistake is visible and cannot be described away as a minor edit. For a page that names a regulator and a leverage cap, that visibility matters: a reader in Kenya can see whether a caveat was always present or was added later. The log is therefore part of the page's evidence, not an appendix.

Keeping the log public does not mean publishing every reader message, and it does not mean naming individuals. It means publishing the correction entries themselves, dated and in sequence, with the old and new wording where the change is a correction. Reader correspondence stays private unless the reader agrees otherwise, and we do not publish an author name or a personal detail to make an entry look authoritative. The public part is the record of what changed, when, and on what basis, which is what a reader needs to check the page.

How Error, Update and Clarification Are Marked Differently in the Log

Each entry carries one of three labels, and the label is chosen by what changed rather than by how serious the change feels. An error means the earlier statement was wrong against the source or the arithmetic; an update means the earlier statement was right for its date but the underlying fact has moved; a clarification means the earlier statement was accurate but a reader could reasonably have read it in a way we did not intend. The label is the first thing in the entry, so a reader scanning the log can tell the three apart without reading the full text.

An error entry quotes the old wording and the new wording and states the basis for the change, such as a recalculation using 1 lot = 100 oz and one pip = 0.01. An update entry states the new position and the date it took effect, and it does not pretend the earlier wording was a mistake. A clarification entry keeps the original wording and adds the sentence that removes the ambiguity, so a reader can see both the original and the added explanation. The three marks are not interchangeable, and an entry is never relabelled later to look better.

The marking matters most where a number is involved. If a margin example using a 0.10-lot gold position is restated, the label tells you whether the earlier figure was wrong or whether the cap it depended on had changed. If a sentence about the regulator is expanded, the label tells you whether the original was inaccurate or merely open to misreading. Because the label is fixed at the time of the entry, the log preserves the difference between a mistake, a change in the world and a wording that needed sharpening.

Who Decides Whether an Entry Is an Error, an Update or a Clarification, and Within What Time

The decision is made by the person who maintains the page, using the source or arithmetic that the entry will cite, and it is made before the change goes live rather than after. That person checks the old wording against the facts we hold, such as 1 lot = 100 oz, one pip = 0.01, and the leverage cap that applies to the entity serving Kenya, and then assigns the label. The decision is not put to a vote and it is not settled by the reader who wrote in, because the basis has to be checkable rather than popular.

The time we set is that a reported error is assessed and, where it is upheld, corrected and logged on the same working day it is confirmed. A report that needs a source check may take longer to confirm, but it is not left open indefinitely, and the log entry is dated to the day the correction is published rather than the day the report arrived. A clarification follows the same timing because it changes what a reader takes from the page. An update is published when the underlying change is confirmed, with the effective date stated.

The decision and the timing are recorded together so a reader can see both what was decided and when. If a report is not upheld, that outcome is noted in our internal record but it does not enter the public log, because the public log records changes to the page rather than every message received. What a reader can always see is the dated entry for anything that did change, including the label, the old wording where relevant, and the new wording. That is the accountability the timing is meant to support.

What We Do When a Source Changes Silently and the Page Has Not Yet Caught Up

When a source changes without notice, the page is treated as suspect from the moment we learn of it, and the first step is to stop relying on the affected sentence until it is re-checked. A silent change is the hardest case because no one told us, so the page may have been carrying a stale figure for a period we cannot pin down. For gold, that could mean a margin example built on a leverage cap that has moved, or a regulator description that no longer matches the entity serving Kenya. The correction is logged as an error if the page stated something wrong.

The entry records that the source moved silently, states the date we became aware, and does not invent a date for when the source changed if we do not know it. That honesty is the point: a reader can see that the page was stale for an unknown period rather than being told a tidy story. Where the earlier statement was accurate when published and the source later changed, the entry is marked as an update; where the page misstated the position even against the old source, it is marked as an error. The two are kept distinct.

We also state what the page now depends on, so a reader can judge the residual risk. If a figure depends on the cap that applies to the entity serving this country, the entry says so and points to the cap rather than presenting the new number as permanent. If a KSh amount or an M-Pesa reference was affected, the entry says which part changed. The aim is not to promise that silent changes will never happen, but to make each one visible once it is known, dated, labelled and tied to the fact it depends on.

Why Nothing Is Deleted From the Page or the Log, Even When the Old Wording Was Wrong

Nothing is deleted because a deleted sentence cannot be checked, and a page about gold margin and leverage has to remain checkable after the fact. If a wrong pip value or a wrong margin example were removed without trace, a reader who acted on it would have no way to show what the page said. Keeping the old wording in the log, with the correction dated beside it, preserves the evidence. The current page carries the corrected text; the log carries the history that explains why the text changed.

Deletion would also make the log useless as a sequence, because each entry depends on the one before it. If an earlier entry were removed, a later update would appear to come from nowhere, and a reader could not tell whether a figure had been corrected once or several times. For a page that names a regulator and a leverage cap, that sequence is part of the meaning: it shows whether a caveat was present from the start or added later. Removing an entry would break that chain and hide the very thing the log exists to show.

Keeping everything does not mean keeping errors on the live page. The live page shows the corrected wording, and the log shows what it replaced. The two are separated so a reader is not misled by an old figure while still being able to inspect it. Nothing is deleted from either, and nothing is rewritten to look as if the earlier version never existed. That rule applies equally to a small clarification and to a correction of a margin figure, because the value of the log comes from its completeness rather than from how flattering it is.

How a Reader Can Check the History of a Page Without Asking Us

A reader can check the history by opening the correction log and reading the dated entries for the page in sequence, from the earliest to the latest. Each entry names the page, the label, the old wording where the change is a correction, the new wording, and the basis for the change. For a gold example, the basis will show the constants used, such as 1 lot = 100 oz and one pip = 0.01, so the arithmetic can be repeated. The log is public precisely so this check does not depend on writing to us.

The check is a comparison rather than a request. You compare the current page with the most recent entry, then compare that entry with the one before it, and you can see whether a figure was corrected once or updated several times. If an entry cites the leverage cap that applies to the entity serving Kenya, you can see whether the cap is the same one the current page relies on. If an entry concerns a KSh amount or an M-Pesa reference, the old and new wording are both present, so the change is visible without a support ticket.

Where the log and the live page appear to disagree, the dated entry is the record of what changed and the live page is the current statement, and the disagreement itself is worth reporting. A reader who finds a mismatch can point to the entry date and the sentence, and that report follows the same assessment and timing as any other. The history is therefore not a archive kept for appearance; it is the working record a reader can use to verify the page, repeat the arithmetic, and see exactly when and why the wording moved.