Obviously, calling sprints "sprints" would be one option, but even though that is well known and might convey an image of working really hard and getting a lot done, it also might imply "moving as fast as you can without regard to fatigue". And even though people directly involved in the sprints can be expected to understand this, managers not directly involved in the sprints might think that sprints involve, well, sprinting.
I believe that when the original term was coined it was in the context of performing consulting for clients at an hourly rate, which might be part of the motivation for naming it a sprint. Sort of an "at $200/hour you had better be sprinting" kind of thing. But in this case, clients buy the software, not the time, so they don't really care if we are sprinting or not.
So what's a good name for a sprint that won't tempt people to think it means working as hard as we can without pause until we drop?
And, before anyone points it out in an answer, there are lots of great ways to educate people on a good agile process, but this question isn't about that. This is about naming sprints in a way that helps as much as possible to educate people about a good agile process by means of the name alone.