basicly you get it right I think (never tested it).
But as the author claims there are two differences from a castsequence:
here are only two missing behaviors of /castsequence: reset on target change (impossible to do with current state headers) and holding position if an action fails (something many people don't like about /castsequence anyway).
..so basicly the last part means: you can't spam it (but this would be the same with the <Toggle>-solution in HKN).