Before you can read the parent note, you must own every symbol it throws at you. We build them one at a time, each anchored to a picture, each earned before the next uses it. Nothing here assumes you have seen the notation before.
The parent writes x=(x1,…,xH). Let us un-pack every piece.
The picture. Think of a row of bars, one bar per number, its height equal to that number. That row is the vector.
Why the topic needs it. A neuron does not emit a single number — it emits a whole row of them, one per "unit". LayerNorm works on that entire row at once, so we need a name for the row (that is x) and a name for each individual bar (that is xi).
The picture. Count the bars in the previous figure. That count is H.
Why the topic needs it. LayerNorm averages across the features. To average, you must divide by how many things you added up — that count is H. Every formula that begins H1∑ is saying "add these up and divide by how many there are", i.e. take an average.
The formulas use i=1∑Hxi. This scares people; it should not.
The picture. Imagine sliding a bucket from the first bar to the last, tipping each bar's height into the bucket. The final level in the bucket is the sum.
Why the topic needs it. Every statistic in LayerNorm — the mean, the variance — is "add something over all features". The ∑ is that adding.
Now we can read the first real formula: μ=H1i=1∑Hxi.
The picture. Put the bars on a see-saw. The mean is the point where the see-saw balances. Numbers above the mean pull right; numbers below pull left; at μ the pulls cancel.
Why the topic needs it. LayerNorm's first job is to recentre the row so its balance point sits at zero. To move it to zero you must first know where it currently balances — that is μ.
The picture. Draw a horizontal line at height μ. Each deviation is the signed gap from that line up (or down) to the top of a bar.
Why the topic needs it. "Centring to zero" is replacing each xi with its deviation. A remarkable fact used later: the deviations always add to zero, because the amounts above the balance point exactly match the amounts below.
The picture. A narrow cluster of bars near the mean → small σ. A wide fan of bars → large σ.
Why the topic needs it. After centring, LayerNorm rescales the row so its spread becomes exactly 1. To shrink or stretch the spread to 1, you must first measure it — that is σ.
Why the topic needs it. This one formula is the heart of LayerNorm. Everything before it (vector, H, ∑, μ, deviation, σ) existed only so this line could be read and believed.
x ::: the whole row of numbers for one example
xi ::: the i-th single number in that row
H ::: how many numbers are in the row (the count of features)
∑i=1H ::: add up over all H features
μ ::: the mean — the balance point of the row
xi−μ ::: deviation — signed distance from the balance point
σ2 ::: variance — average of the squared deviations
σ2=σ ::: standard deviation — a typical distance from the mean
x^i ::: the standardized value (mean 0, variance 1)
ϵ ::: tiny number that prevents dividing by zero
γi,βi ::: learnable scale and shift applied after standardizing
Read top-to-bottom: the vector and its length give us the mean; the mean gives deviations; deviations give variance and spread; spread plus ϵ let us standardize; and the two knobs finish the job. Only once all of these are in hand does the parent topic Layer normalization make sense.
The same mean/variance machinery, but averaged down a column instead of across a row, is Batch normalization — its column-vs-row difference is the whole story.
The instability LayerNorm fights — shifting input distributions — is Internal covariate shift.
LayerNorm is the normalizer of choice inside Transformers, works alongside Residual connections, and has a leaner cousin RMSNorm that drops the mean-subtraction step.
The "tidy range" matters because the next stage is usually an activation function — see Activation functions.