Before you can read the parent note, you need every symbol it throws at you to feel obvious. This page builds them one at a time, from nothing. If you have never seen a bold arrow-letter like v before, start here and do not skip.
Everything happens in ordinary 3-D space, like a room. To talk about where the lander is, we pin three number-lines (axes) to the ground: x (east), y (north), z (up). Any point is then three numbers: how far east, how far north, how far up.
Figure 1 — The three axes with x horizontal and z pointing up. The lander (amber square) sits above the pad; its motion arrow points down, so its z-component is negative. Gravity g (white arrow) also points down for exactly the same reason. Use this picture to fix why "down = negative" throughout the topic.
Why fix this now? On the parent page you saw vz→−vtd and g=(0,0,−g) — both are negative for the same reason: they point down, and down is the negative z direction. Get the convention wrong and every answer flips sign.
The parent note writes things like r, v, a, T, g in bold. Bold means the thing is a vector: not one number, but an arrow carrying both a direction and a length.
Figure 2 — One velocity arrow v (amber) split into its horizontal part vx and vertical part vz (cyan). The two components meet at a right angle, and the arrow is the diagonal — that is why the length formula below is just the Pythagorean theorem. Read this figure whenever "components" feels abstract: they are literally the two sides of the box the arrow spans.
r → position vector: the arrow from the pad to the lander. Its length is distance-to-go.
v → velocity vector: the arrow showing which way, and how fast, the lander is moving right now.
a → acceleration vector: how the velocity arrow is changing right now.
T → thrust vector: the push the engine makes, pointing out the bottom of the vehicle.
g → gravity vector: the constant downward pull, g=(0,0,−g).
The parent writes r˙ and r¨. A dot on top is shorthand for "rate of change per second" — it comes from calculus, but you can read it purely as a picture.
r¨=acmd+g
reads in plain words: the lander's acceleration equals the push the engine commands, plus the constant downward pull of gravity.
The parent uses arctan(vh/vtd) and θ. To read those, you need one small triangle — and first, the symbol vh.
Figure 3 — The touchdown velocity as a right triangle: the downward leg vtd and the sideways leg vh (cyan), with the velocity arrow as the hypotenuse (amber). The amber arc marks the angle from vertical, whose tangent is vh/vtd. When vh=0 the arrow lies flat along the downward leg and the angle is 0∘ — a perfectly vertical touchdown.
θ → tilt angle: how far the vehicle's thrust axis leans away from straight-up.
θtip → the tilt at which the center of mass falls outside the legs and the lander tips.
ω → angular rate: how fast the body is rotating (spinning), in degrees or radians per second.
Plain reading: "The push I command = (how far off my position is) scaled by how little time is left, minus (a blend of my current and target velocity) scaled by time left, minus gravity so it's already cancelled." Each piece is an arrow; you add arrows tip-to-tail to get the final commanded push.
These feed forward into the deeper machinery: the command acmd becomes a thrust order handled by Attitude Control & Inner Loop, the two-point boundary idea generalizes into Powered Descent Guidance (PDG) and Convex Optimization Landing (lossless convexification), and the "chase a target" instinct connects to Proportional Navigation.