Fixing Fossilized Errors: The Top 10 to Unlearn | Korean Grammar

By the time you can hold a conversation in Korean, some of your errors have gone quiet. They no longer trip you up, no one corrects them, and you no longer notice them — which is exactly why they survive. A fossilized error is a mistake that still communicates: your listener understands you, fills in the intended meaning, and moves on, so nothing ever forces the correction. This roadmap collects the ten errors English speakers most reliably fossilize, ordered by how early each takes root, and links every one to its Common Mistakes page so you can drill it directly.

💡

Why fossilized errors need special treatment: they resist more input. You have already heard thousands of correct sentences and kept the wrong habit anyway, because comprehension never depended on the fix. The cure is not more listening — it is targeted contrast drilling: put your wrong form next to the right one, understand precisely why they differ, and rehearse the pair until the correct one is automatic. That is what each item below is built for.

Be realistic: unlearning is harder than learning, because you are competing with a habit, not filling a blank. Pick two or three of these at a time, drill them deliberately for a couple of weeks, and let the rest wait. Trying to fix all ten at once fixes none.

1. 은/는 vs 이/가

The oldest and deepest error: reaching for the topic particle 은/는 where the subject particle 이/가 is required for new information or focus, and vice versa. As a rough anchor — new or focused information that answers "who/what?" takes 이/가; something already established that you are commenting about takes 은/는. Drill it on 은/는 vs 이/가 mistakes, choosing 은/는 vs 이/가, and topic vs subject.

❌ (누가 왔어요? 에 대한 답으로) 친구는 왔어요.

Incorrect — answering 'who came?' focuses new info, which needs 가, not 는.

✅ 친구가 왔어요.

chinguga wasseoyo

A friend came. — new-information subject takes 가.

2. Native vs Sino-Korean numbers

Korean has two number systems, and picking the wrong one is a lifelong tell. Native numbers (하나, 둘, 셋…) count objects, people, and hours; Sino numbers (일, 이, 삼…) do money, dates, minutes, and most measurements. The classic fossil is Sino counting of objects (✗삼 개) or the wrong system for money. Drill it on native vs Sino numbers, which system per counter, and reading prices in 원.

❌ 사과 삼 개 주세요.

Incorrect — counting objects with 개 needs a native number, not Sino 삼.

✅ 사과 세 개 주세요.

sagwa se gae juseyo

Three apples, please. — native 세 before the counter 개.

3. Honoring yourself with -(으)시-

-(으)시- raises the subject of the sentence. When the subject is you, adding it is accidental self-flattery — one of the most common intermediate slips. Drill it on self-honorification and -(으)시- is not for yourself.

❌ 저는 지금 가세요.

Incorrect — -(으)세요 honors the subject, and the subject here is you.

✅ 저는 지금 가요.

jeoneun jigeum gayo

I'm leaving now. — plain 해요체 on your own action.

4. 있다: possession vs location, and the particle

있다 does double duty — "have" and "be located" — and the case marking differs. For possession, the possessed thing takes 이/가 (저는 차가 있어요, "I have a car"); for location, the located thing takes 이/가 and the place takes 에 (차가 집에 있어요, "the car is at home"). Learners fossilize 를 on 있다 by analogy with English "have." Drill it on there-is vs it-is, existential 있다/없다, and have: 가지고 있다.

❌ 저는 차를 있어요.

Incorrect — 있다 is not transitive; the possessed noun takes 가, not 를.

✅ 저는 차가 있어요.

jeoneun chaga isseoyo

I have a car. — possession marks the thing with 가.

5. -아서/어서 vs -(으)니까

Both mean "because," but -아서/어서 cannot host a past-tense cause and cannot precede an imperative or proposal. When the main clause is a command, a suggestion, or you need the cause tensed, -(으)니까 is mandatory. Drill it on choosing -아서 vs -(으)니까, -아서 vs -니까, and -(으)니까 cause.

❌ 비가 와서 우산을 가져가세요.

Incorrect — -아서 can't precede an imperative; use -(으)니까.

✅ 비가 오니까 우산을 가져가세요.

biga onikka usaneul gajeogaseyo

It's raining, so take an umbrella. — -(으)니까 before a command.

6. 좋다 vs 좋아하다

좋다 is a descriptive verb ("is good/pleasing") whose experiencer's liked thing takes 이/가; 좋아하다 is a transitive verb ("likes") whose object takes 을/를. English "I like X" maps cleanly onto neither, so learners cross the wires. Drill it on descriptive-verb object particles, choosing 좋아하다 vs 좋다, and 좋다 vs 좋아하다.

❌ 저는 커피가 좋아해요.

Incorrect — 좋아하다 is transitive; its object takes 를, not 가.

✅ 저는 커피를 좋아해요.

jeoneun keopireul joahaeyo

I like coffee. — transitive 좋아하다 + object 를.

7. 안 vs 못

안 negates by choice ("don't / not"); 못 negates by inability ("can't"). English "not" covers both, so learners default to 안 even when the meaning is inability. Drill it on choosing 안 vs 못, 안 vs 못 contrast, and 못 (inability).

❌ 다리를 다쳐서 안 걸어요.

Incorrect — this is inability, not choice, so 못 is required.

✅ 다리를 다쳐서 못 걸어요.

darireul dacheoseo mot georeoyo

I hurt my leg, so I can't walk. — 못 marks inability.

8. The object particle 을/를

Two opposite fossils here: dropping 을/를 where the sentence needs it, and — the reverse — marking a noun with 을/를 when the Korean verb actually takes a different particle. The textbook case is 만나다 ("meet"), which is transitive in Korean (친구를 만나다), unlike its English dative feel. Drill it on object-particle dropping, the object particle 을/를, and 만나다 takes the object, not the dative.

❌ 어제 친구에게 만났어요.

Incorrect — 만나다 is transitive; the person met takes 를, not 에게.

✅ 어제 친구를 만났어요.

eoje chingureul mannasseoyo

I met a friend yesterday. — 만나다 + object 를.

9. 되다 vs 하다

하다 is "do/make" (the light verb behind thousands of compounds); 되다 is "become / turn out / work." Learners blur them, especially in ability and completion contexts. Drill it on 하다 vs 되다, 하다/되다 valency, and the spelling trap on 되다 vs 돼요.

❌ 저는 요리를 잘 돼요.

Incorrect — 'do something well' is 하다; 되다 means 'become/work out'.

✅ 저는 요리를 잘해요.

jeoneun yorireul jalhaeyo

I cook well. — 하다 for performing an activity.

10. Adjectives conjugated like English adjectives

The deepest structural fossil: treating Korean adjectives as English-style adjectives that need a copula (✗예쁘이에요). Korean adjectives are descriptive verbs — they conjugate exactly like action verbs, taking endings directly (예쁘다 → 예뻐요), and never a copula. Drill it on adjectives as English adjectives, adjectives are verbs, and action vs descriptive verbs.

❌ 그 가방 예쁘이에요.

Incorrect — 예쁘다 is a descriptive verb; it conjugates, it doesn't take 이에요.

✅ 그 가방 예뻐요.

geu gabang yeppeoyo

That bag is pretty. — 예쁘다 conjugates to 예뻐요 directly.

Where to go from here

These ten are the reliable offenders, but the same "still communicates, so never corrected" logic hides others worth auditing yourself for: present-perfect transfer, -고 있다 with states, inconsistently dropping 요, over-using the possessive 의, pronoun overuse where Korean drops the subject, honorific verb direction, and irregular over- and under-application. When you have retrained these, move on to the TOPIK 3–4 intermediate path.

Key takeaways

Fossilized errors survive because they still communicate — so contrast drilling, not more input, is the fix.
The earliest and deepest fossils are particle choices (은/는 vs 이/가, 을/를, descriptive-verb 이/가) and treating adjectives like English adjectives.
Honorific self-application, 안/못, 하다/되다, and 아서/니까 are the mid-list habits worth isolating and drilling in pairs.
Fix two or three at a time; unlearning one habit deliberately beats nudging all ten vaguely.

Now practice Korean

Reading grammar gets you part of the way. The exercises are where it sticks — free, no signup needed.

Start learning Korean→