The biggest change was making many of the refactorings in the book less class-centric. In Java, of course, everything has to be a class, everything has to be an object. So as a result, all the refactorings are expressed in that mindset, in the context of classes.
Of course, that's not necessary to refactoring at all. It's just an accident of when it was written. Now it's more about using classes as one of your structuring options, not necessarily the primary one. That goes beyond renaming extract methods into extract function. Obviously that is necessary, but it goes beyond that.
Is that part of moving from object-orientation towards a more functional style?
And, in fact, that's why you still need classes, because classes are designed to structure mutable data. And so it is more functional to some extent, in that there's more use of class functions than there was in Java.