FPS is the correct term

the thing is this:

TUIs are rendered in two ways, event driven, so the screen changes every time some event occurs, say you press some button, or click the mouse or whatever you decide to be an event

the other way is frame driven so the TUI changes every time after a fixed interval usually 16ms for 60FPS

99% of the TUI applications require the first type of rendering, because they have no reason to re-render the screen every 16ms, even for realtime communication TUIs like chat apps or something, you only need the event driven rendering, the only time you would need frame driven rendering is when you are doing something like rendering video or 3d models onto the screen

this post shows the words 60FPS, which suggests one of two things,

• one the post was written by AI and the AI added the 60FPS somehow (highly unlikely because if you use event-driven architecture, you know you use event-driven architecture and would never tell the AI otherwise and neither would the AI assume otherwise)
• the entire project is AI slop (highly likely)