The Problem With Repeatable Reads

You don't read a value that's rolled back, right? Or about to roll back. Even if it's committed, you don't trust it. That's called dirty reads. The second problem is called repeatable reads. So I read it first and then I read it again. It's changed in the same transaction. But why say, who cares? And then, yeah, so what? It changed. Back to the second concept, consistency. My reads are non-repeatable. So this is a problem.