Hacker News Reader

Just changing the word isn't going to change the practice. You're supposed to take breaks between sprints. There needs to be planning and alignment to an easily-obtained goal, which requires time. But most people don't know how to do Scrum and hand-waive the goal, the planning, the retro. The end result is unsustainable work with no specific goal in mind that exceeds the sprint cycle. Or 20 epics all in progress at once. Or business goals that shift and put unobtainable expectations on teams.

What's a break period? Where is that described?

It's not explicitly described. "The break" (imo) is giving enough time to planning at the beginning, and actually dealing with the review & retro items. The length of the sprint can be shortened so that there is more learning and planning. Sprints are cancelled if the goal becomes obsolete.

Cycle

Cycle or stint. I like "stint" more.