Before you can read a learning curve, you must be able to read every mark on it. This page builds the whole alphabet from nothing. Nothing here assumes you have seen a formula before. We collect the pieces in order — each one leans on the one before it.
In the figure, follow the flow left to right: the input x enters as the labelled arrow on the left (a house size). The black box is the rule h.The red dial inside the box is θ — turning that one red dial changes the guess that leaves on the right arrow. So the picture is literally the symbols: arrow-in =x, box =h, red dial =θ, arrow-out =hθ(x). Learning means finding the red-dial position that makes the output arrow least wrong.
Why does the topic need this? Because a learning curve is a story about one model being retrained on more and more data. If you don't picture hθ as an adjustable machine, the rest is meaningless.
See Model Complexity for what makes a model "simple" or "complicated" — that idea returns in Section 6.
In the figure, the black line is the model (y^=hθ(x) for every x). Each black dot is one true answery(i). The red vertical stick from a dot up to the line is that example's errory(i)−y^(i) — its length is exactly what L squares.
Why this tool and not just "count the wrong ones"? For predicting a number (like price), there is no simple right/wrong — you are always a little off. Loss measures how much off, on a smooth scale, so the model can tell whether a knob-turn helped a little or a lot.
We have a loss for each example. To score the model overall, we average all of them. That average is the costJ.
Why divide by m? So the number stays comparable no matter how many examples you have. A total of 200 across 100 houses is not worse than 100 across 40 houses — the average (2 vs 2.5) is the fair comparison. This matters enormously here because the whole point of a learning curve is to change m and watch J.
In the figure, the left black box holds the m training dots the model practices on; the right red box holds the mval validation dots it is quizzed on but never studies. The two boxes never share a dot — that separation is the whole point. See Train-Test Split and Cross-Validation for how this split is done reliably.
Why two costs and not one? Because the difference between "how well you do on studied material" and "how well you do on the quiz" is the entire diagnosis. A model can ace the practice sheet and flunk the exam — that gap is overfitting.
In the figure, the horizontal axis is m and the black curve is a cost J(m); as you move right (more data) it flattens toward the dashed red line, which marks the limit — the height it never crosses. The whole diagnosis in the parent note ("both errors plateau high" vs "gap persists") is a statement about what these limits are and how far apart they sit.
Why do we need limits? Because a learning curve is only a few dots, but the question — "would even more data help?" — is about behaviour far to the right, past the data you have. The limit is the mathematical way to reason about "off the edge of the chart."
The parent note splits total error into named ingredients. Here is what each is, in plain words.
Now the parent note's two key approximations, with the why spelled out and the noise handled correctly:
Both extra terms shrink via the same "divide by m" move you met in Section 4 — bigger m makes them small. What they cannot remove is ϵbias (fixed by model choice) or σ2 (fixed by the data's own noise).
Tools that change these ingredients: Regularization and Feature Engineering lower variance or bias; more data mainly attacks the mk gap term.