All I am trying to do is to establish to what lenghts should descriptions go to avoid this kind of problems. If the above suggestion would be considered as necessary to address, many other kata which rely on the fact that one second is 1000 milliseconds, or that one minute is 60 seconds, or that one hour is 60 minutes, would have to be updated as well. I am just trying to figure out if that's what has to be done.

Me sorry for bad Englisch, I'm not Englisch. Hope u understand what I ask.

I have a honest question: what could even be some another example, where one second would be something else than 1000ms?

Examples should not help you understand a problem. Specifications should do that.

"Remove spaces" really should not need examples, unless you are hell-bent on reverse engineering the examples to avoid reading the specifications. I see a lot of that ( people insisting on examples ), and I think it's an awful habit to have.

Conversely, a problem specified by examples only very quickly becomes "just read my mind."

If you read the specifications, can't figure out the task, and then resort to reverse engineering the examples to figure out what an author apparently, probably, meant to be the task, it's entirely possible the specs were written badly, but it's also entirely possible you are refusing to read the specs.

Do not refuse to read the specs.

( If the description is written badly, raise an Issue. But really, how bad can "remove spaces" be? Which of those words do you need defined? )

( This advice worth what you paid for it. Other opinions may be available - but they might be wrong. )

Is it better now?

What more do you need? An example? It's pretty self-explanatory imo.