Corrections Record

This page logs the places we've changed. Fix what's wrong, and put the change in the open—that's what we think a content site should look like.

01Why we log corrections openly

Nobody can promise never to be wrong, especially writing about fees and policy—things that change constantly. What sets sites apart is what they do afterward. Our approach: when we find a problem, we fix it, and once fixed, we note "what it said before, what it says now" on this page.

There are two reasons. One is accountability to readers—you have a right to know the version you saw earlier may have been off. The other is that putting corrections in plain sight is itself a constraint, pushing us to be more careful before writing and to check seriously after feedback. Below are the corrections from the site's early run.

02Correction entries

2026-05-22 · How a fee was stated

Before: an account-opening article wrote a hard number for a monthly account fee.
Now: changed to "go by the official page at the time," with a note of roughly when we checked the fee. The reason is that platforms adjust these charges, a hard number dates quickly and can mislead, and pointing readers to where to verify is steadier.

2026-05-30 · Wording on HK/Macau permit endorsements

Before: one spot described the validity of a HK/Macau permit endorsement too absolutely, reading as if every case were the same.
Now: rephrased more cautiously, noting that endorsement types and validity vary from person to person, that the immigration authority's rules govern, and asking readers to confirm against their own document.

2026-06-08 · Consistent referral-code wording

Before: in a few early articles, the wording for the referral code wasn't quite consistent—some said "use our code," with slight variations elsewhere.
Now: standardized site-wide to "through our referral code," consistent in wording and less open to misreading. The code itself (Binance BNTIKTOK) hasn't changed.

03Spot an error? Tell us

If you read something that seems off—a figure out of date, a flow changed, an ambiguous claim—you're welcome to write. Include the article link and what you're going on, and once we've checked, we'll correct it; the important changes go into this page too. Address: [email protected].

Note

This page logs only content-level corrections (fees, flows, claims and the like), not typos or minor layout tweaks—so the corrections that matter don't get buried.