Abstract and public have nothing to do with each other.
Every method in every interface is implicitly public and abstract. They can be declared that way or not, but if they are, it's redundant. Some programmers might choose to explicitly declare them public and/or abstract to make it obvious, but it's not necessary and it has no effect.
Ah, perhaps I misinterpreted it.
On first reading, it looked like he was saying something along the lines of "why is the method declared abstract, if it's already declared public?" as if having those two together (rather than having either or both of them on an interface method) were redundant.