Program Structure & Sequence: Right Steps, Wrong Order
Every line here does something correct. Read top to bottom before deciding the whole program is correct.
The Program Structure & Sequence set's whole point is that a program does exactly what you wrote, in the order you wrote it -- not the order that would make sense if you explained the steps out loud. The most common way to fail one of these challenges is to write every step the task actually needs, correctly, and just show one of them before it has the value it's supposed to show.
Press Run to see what your code does.
That prints 5, not 20 -- SHOW ran before the CHANGE line ever executed, so it reported the value total held at that moment, which was true and also not the answer the challenge wants. Nothing above is a syntax error; every line is valid pseudocode doing exactly what it says. The fix is purely about order: move SHOW total to the last line, after every change that needs to happen has happened. When a challenge like this fails, read your program as a sequence of moments rather than a finished description -- ask what each variable's value actually is at the specific line where you read it, not what it eventually becomes.
Everything above runs in this page, on your own machine. There is more of it on the practice pages.