This chapter is about words. Specifically, the words you use when you talk about the market — out loud, in your journal, and most importantly, in your own head while you’re watching a chart.
That might sound like a strange thing to dedicate a full chapter to. You might be thinking: does it really matter how I phrase things, as long as I understand what I mean?
It does. More than you’d expect. Because the words you use don’t just describe your thinking — they shape it. The language you reach for when you’re reading a chart determines what you look for, what you expect, and how you react when reality doesn’t match the picture in your head. And most of the language that traders use — the language you probably learned alongside everything else about Forex — quietly smuggles in assumptions that have no mechanical basis.
Let’s start with a list. These are phrases that show up constantly in trading communities, on YouTube, in courses, in chat rooms. You’ve probably used most of them yourself.
- Price is testing support.
- The market is hunting stops.
- Price wants to fill that gap.
- Sellers are defending this level.
- Price is respecting the trendline.
- The market is seeking liquidity.
- Price failed to break resistance.
Read through that list again. Every single phrase attributes something to price or “the market” that a mechanism cannot have: intent.
Testing implies purpose — a deliberate probe to check whether something holds. Hunting implies a predator with a target. Wanting implies desire. Defending implies a conscious decision to hold a position. Respecting implies acknowledgment of a rule. Seeking implies goal-directed behavior. Failing implies an attempt that fell short of an objective.
None of these things are true. Price is the output of a process. It has no awareness of levels, no desires, no targets, no objectives. It cannot test, hunt, want, defend, respect, seek, or fail. It can only be the number produced when aggression meets liquidity — and that number changes when the interaction changes.
Here’s why this matters practically, not just philosophically.
When you think “price is testing support,” you’re framing what you see as a deliberate act. The market is doing something purposeful. And purposeful acts carry an implied trajectory — if it’s testing, the test will produce a result, and that result will be meaningful. You’re already partway toward expecting a bounce. You’re watching for confirmation of something you’ve half-decided is coming.
When you think “sell aggression is arriving at an area with prior buy-side liquidity — I’m watching to see if the aggression gets absorbed,” you’re framing what you see as a question. You don’t know the answer yet. You’re watching for information, not confirmation. Your attention is on the actual behavior of the market, not on whether it’s behaving the way you expected.
The first framing makes you a worse observer. The second makes you a better one. And the only difference is the words.
The hardest one on that list is stop hunting.
“The market hunted my stop” is one of the most common things traders say after a losing trade. Price came down, hit exactly where their stop was, and then reversed. It feels deliberate. It feels like the market knew where the stop was and went there specifically to trigger it.
What actually happened — mechanically — is exactly what Chapter 7 described. An obvious level had a cluster of stops sitting at it. Price relocated into that area. The stops triggered, generating a wave of aggressive market orders. That wave either found deep opposing liquidity and got absorbed, causing the reversal, or it didn’t, and price continued through.
No hunting. No intent. No knowledge of where your stop was specifically. Just a concentration of conditional market orders at an obvious location, doing exactly what conditional market orders do when price reaches them.
The “hunting” story is emotionally satisfying — it gives you a villain and absolves you of having placed your stop at a predictably crowded location. The mechanical story is less satisfying emotionally but far more useful, because it points to something you can actually address: where you put your stops, and what you understand about what happens when price reaches obvious levels.
You can’t trade better by thinking the market hunts stops. You can trade better by understanding stop clustering and what it produces.
So what does the right language actually sound like?
It describes participants and orders — the things that are real and observable — rather than attributing behavior to price. Here are a few swaps.
Instead of “price is testing support” — try “sell aggression is arriving at an area with prior buy-side liquidity.”
Instead of “the market is hunting stops” — try “price has relocated into a cluster of likely stop orders.”
Instead of “sellers are defending this level” — try “sell-side liquidity at this area is absorbing buy aggression.”
Instead of “price respected the trendline” — try “buy aggression arrived at this area and was absorbed.”
Instead of “price wants to go higher” — try “buy aggression is currently overrunning available sell-side liquidity.”
These might feel clunky at first. That’s okay. Any new habit feels awkward before it becomes natural. What you’re building is a mental vocabulary that keeps you anchored to what’s actually observable rather than what makes a good story.
You don’t have to narrate every candle in perfect mechanical language out loud. But when you notice yourself thinking in terms of what price “wants” or “is trying to do,” that’s the moment to pause and translate. What is actually happening in terms of orders? What is the interaction I’m actually watching? What does this behavior tell me — as opposed to what story does it remind me of?
There’s one more thing worth saying about language, and it’s about confidence.
Intent-based language often gets used because it sounds more confident. “Price is going to bounce off this support” sounds decisive. “I’m watching to see whether sell aggression at this area gets absorbed by buy-side liquidity” sounds uncertain — like you don’t know what’s going to happen.
That’s because you don’t. And neither does anyone else.
The appearance of certainty that comes from intent-based language is borrowed certainty — it’s confidence that the story you’re telling will match what the market does. Sometimes it will. When it doesn’t, the mismatch is jarring, and traders often respond by doubling down on the story rather than questioning it. “Price should have bounced there” becomes the reaction, instead of “my read was wrong — what actually happened?”
Mechanical language is honest about what you don’t know. It makes explicit that you’re watching for information rather than expecting a specific outcome. That’s uncomfortable, but it’s accurate. And a trader who’s accurately calibrated about what they know and don’t know will consistently outperform one who’s confidently wrong.
Part II started with the chart as a record. It moved through levels, stops, and the mechanical reality underneath all of them. It ends here, with language — because language is the interface between what you see on the chart and what you do about it.
Get the language right and you see more clearly. You expect less and observe more. You stop being surprised by the market doing what mechanisms do, because you’re no longer telling yourself stories about what the market is choosing to do.
Price has no intent. It has no awareness of you, your stop, your analysis, or your expectations. It is the number produced when aggression meets liquidity. Every time. That’s it.
The sooner that stops being a frustrating limitation and starts being a useful and clarifying fact, the better off you’ll be.
Now — with the mechanics solid and the chart properly understood — we can start learning to actually read it.