This page assumes nothing. If you have never seen "MHz", "64-bit bus", "ns", or "×106", start here and read top to bottom. Every symbol used in the parent topic is built below, in the order you need them.
Why the topic needs w: bandwidth is "how many bytes per second". Wider bus = more bytes per single transfer. To turn bits into bytes we divide by 8, which is why you will always see 8w in the formulas.
Why the topic needs ns: the parent note keeps quoting "the array access time is ~15 ns". That is the time the slow charge-buckets take to hand over their data. Holding this number lets you see how slow the core really is compared to the interface.
A clock is a square wave — it rises to "high", stays, falls to "low", stays, and repeats. This shape has two special moments per cycle: the rising edge (going up) and the falling edge (going down). Remember these two edges — the entire DDR ("Double Data Rate") trick lives on them.
Why the topic needs it: every bandwidth number is millions or billions. When the parent writes 100×106×8=800 MB/s, it is just (100 million transfers) × (8 bytes each) = 800 million bytes per second.
Why the topic splits "clock" from "transfers": for old SDR memory there is exactly one transfer per clock cycle, so transfers/sec =fclk. But DDR fires on both edges, giving two transfers per cycle. So transfers/sec =2×fclk. The label "DDR-400" is 400 MT/s, meaning the clock is only 400/2=200 MHz.
Why the topic needs n: the master relationship of the whole page is
fI/O data rate=≈constantfcore×prefetch.
The core clock stays put; the prefetch and I/O clock multiply the data rate up.
Read it as: bits and clocks at the top feed into transfers and bandwidth; the slow-array fact feeds the prefetch idea; together they explain the DDR evolution in the parent topic.