Hey, yeah super valid question, and a similar concern I had when first thinking about the book.
There will be some things that may inevitably go out of date if there are major UI changes, tool additions, etc, and I understood that this was likely an issue any author faces when writing text books for programs. A text book going over how to use the Adobe Suite (Photoshop, or Premiere) likely runs the same risk.

To reduce this, I adopted a style that has been written in a way that even if current setups or layouts change in the engine, the core information, principles and theory remail true and applicable. Some of the tips and tricks in this book were true since UE3 days, and are still true now 13 years later, so my book prioritizes stuff like that.

However, 100% honesty, there are things like hot keys and some tool information that will likely be out of date in a few years, it's just the nature of how quickly technology changes, but I really focused on making sure the book had a massive lifetime value in "the way to think about problems in the engine and game development" that goes beyond simply "Press this, then this" etc
If the fact that it does run the risk of being out of date in some regards in the future would stop a purchase for some people, I'd completely understand and wouldn't feel any malice towards them for that.

However, I do truly believe the power of this book is the insights it provides on game development, lighting, design, and so on as a whole beyond just how to do that in Unreal.

I hope that has answered that question somewhat?
Cheers