index fbd3f66..8c43606 100644
@@ -12,7 +12,7 @@ naming a thing gives you power over it. language shapes what you can think, what
there's a difference between experiencing a pattern and naming it. i'd been [[zooming-out|zooming out]] for years before i called it that. but once it had a name, it became a tool i could deploy deliberately instead of a thing that sometimes happened by accident.
-this is true across every domain i've worked in. in debugging: the moment you can name a bug pattern — "this is a [[debugging/assumptions-kill|hidden assumption]] bug" or "this is a state management race condition" — you've compressed hours of future debugging into a recognition event. instead of reasoning from scratch, you pattern-match.
+this is true across every domain i've worked in. in debugging: the moment you can name a bug pattern — "this is a [[assumptions-kill|hidden assumption]] bug" or "this is a state management race condition" — you've compressed hours of future debugging into a recognition event. instead of reasoning from scratch, you pattern-match.
in life: "[[resyncing]]" is a thing i do all the time. but naming it made it conscious. now when i feel off-track, the word surfaces automatically: "i need to resync." the name is a handle that makes the concept graspable.