Iterations are normal in LXD. The aim is always to minimise these iterations. Some are necessary, such as further input from subject matter experts and clients, then there’s useful input from users. Some, however, will cause friction. These tend to be small, avoidable errors, such as spelling, punctuation and grammar. For some reason, people reviewing learning experiences are particularly sensitive n this issue. They will happily make mistakes in print but god forbid that you may make a spelling mistake on the screen. A particular source of such errors is on graphics, where someone whose background is not in writing, types in text. I used to demand that graphic artists never typed in text, that they only ever cut and paste. May seem harsh, but it saved a lot of potential aggro. Similarly with glitches on graphics, audio and bugs. Try to eliminate as many obviously avoidable error was possible. A good rule is get it right first time. You should feel responsible for quality control and not see others, like the project manager, QA folk or client as picking up the slack.