>Only 3 steps to verify a proof
>step 1, verify the proof
This mistake is amusing because one of the main goals of the article is to explain why the statement is different from the proof of the statement, and why this distinction is important.
The statement is a formal description of the thing you're trying to prove; the proof is the step-by-step reasoning that shows why it's true. Usually the first is much smaller than the second, which is good because it's the thing that you (or some entity you trust) needs to check manually. Checking that the proof proves the statement is what Lean compilation does for you automatically.
Loosely, the statement is like an interface definition (e.g., an abstract base class); the proof is like an implementation of that interface. For sufficiently simple contracts, even regular compiled languages like Java or C++ can check an implementation for "correctness", e.g., that all methods declared in the base class have been defined, that each of them either returns a value of the type declared in its signature or throws, etc. Lean is similar but allows a lot more conditions to be expressed.
No. Verify the statement not the proof (usually the statement is <<1% the lines of the proof, e.g. in the case of Fermat's Last Theorem it's approximately 0.00001%).