This page builds every symbol and word the parent note uses, starting from "what is a dot and a line". If the parent note said "node" or "edge" or wrote n−1 without showing you the picture — we fix that here, from zero.
Before any tree, we need two things you can literally draw.
Figure s01 (below)defines node and edge visually: it shows two labelled circles (A, B) joined by one orange line, with the dot and the line each arrow-labelled so you can attach the word to the picture before reading on.
WHY start here? Every later word — parent, child, root, leaf — is defined by which dots connect to which. If "node" and "edge" aren't concrete pictures first, none of the later words can be.
A plain line just says "connected". A tree needs a direction: one dot is above, the other below.
WHY the topic needs it: words like ancestor ("dots above you") and descendant ("dots below you") are meaningless without an agreed up/down. Parent/child is that agreement.
Figure s02 (below)defines the root visually and pins down "up" versus "down": the red circle R at the top has only downward lines, and green/blue arrows label the two directions we will measure with (up toward the root, down toward the branches).
WHY exactly one? A tree is a single hierarchy — one boss. If two dots had no parent, you'd have two separate trees, not one. The root is the anchor from which "up" is measured.
Now that "child" exists (Symbol 1), we can name the dots that have none.
WHY the topic needs it: the parent's height definition and the sentence "leaf has height 0" are meaningless until "leaf" is a defined word. We define it before height uses it.
Figure s03 (below) contrasts a valid loop-free tree (green, left) against a forbidden shape with a cycle (red, right), where dot D can be reached from R two different ways. Compare the two panels: the loop is the only difference.
WHY the topic needs it: the rule "no one can be their own ancestor" is exactly "no cycles". It is the property that separates a tree from a general graph.
WHY n−1, shown from the picture: every dot except the root has exactly one line going up to its parent (Symbol 1 + Symbol 2). That is one edge per non-root dot. There are n dots total and 1 root, so n−1 non-root dots, hence n−1 edges. The root adds none — it has no parent line. This is counted, not memorised.
Every "how far" measurement in this topic counts edges along a path, never dots.
With "path length = edges" fixed, the two measurements the parent uses become precise:
WHY the topic needs both: the parent's recursive formula (next section) computes height(v), and its count bound uses the tree's height h=height(root). Neither is meaningful until these two words are pinned to path length.
WHY the topic needs it: the parent writes "degree ≤d" in its count formula. That d is precisely this tree-wide maximum, so the count bound is a guaranteed ceiling, not just a typical case.
WHY the topic needs it: the recursive height formula treats each child as the root of its own subtree and asks for that subtree's height. Without "subtree" the recursion has nothing to recurse on.
Read the map below bottom-up: node and edge (top boxes) are the raw dots and lines. Adding a direction gives parent/child, which lets us name the root (childless-above) and leaf (childless-below). "No cycles" plus the root gives the n−1 edge count. Counting in edges gives depth and height; the set of children plus max gives the recursive height formula (grounded by the leaf base case). Degree per node, maxed into the tree degree d, plus powers, gives the geometric-series bound. All arrows converge on the Tree Terminology topic.