If I want to make one disk image smaller and another bigger (so the total still equals my plan's limit), I have to wait around for the first reduction to complete before I can even queue up the second enlargement. Otherwise Linode complains that the enlargement exceeds my plan's limit.

Linode should just let me enter a larger number for the second disk (even though it makes my total greater than my plan limit) and queue it up, and then have it fail on execution if the total would be too great by the time it executes (which it shouldn't be as long as the reduction of the first disk executed first).

That would also let me queue up a boot command as well, so it seems the removal of one JavaScript validation alert could really save a lot of waiting.