It is bit hard to correctly interpret your question, so I am taking liberty to choose the one that's likely. Let me know if I am way off. I assume the question to be "How does the book explain the procedure to apply a design pattern and not "procedure to apply design patterns ".
"Design Patterns - A domain agnostic approach" attempts to give the reader a solid understanding of the pattern. To do this it first defines exactly the terms it uses. For example what does "behaviour" mean exactly? This is so that both the author and reader start on the same level of understanding. It avoids explanations like "Decouple an abstraction from its implementation so that the two can vary independently" (used commonly for bridge pattern) which first learners would struggle to comprehend. Then with a series of relevant questions and answers a way to solve the problem at hand is developed, that's essentially the pattern. The discussion then ends with 10/15 core steps to implement the pattern. So it explains the procedure to implement a design pattern in few steps. It does not give procedure to apply design patterns, that's different. Having said that, the assumption is, if the understanding is solid; the reader can well command the ability to twist, turn and mix different patterns to suit the problem at hand, hence find "way to apply design patterns" inadvertently perhaps creating a concoction !
Also, "help of examples w.r.t IT industry", this is a point I strongly contest, my hypothesis is that repeated/classic examples taken to describe pattern mostly hinders the understanding and often leaves the reader clueless on how to apply the pattern for the problem at hand which mostly is very different from the example used for explanation. So this book does without any examples, only one of its kind! It attempts to give the idea behind the pattern in its purest form.
Finally, this attempt to precisely convey the thoughts, as much as possible, also serves as an example of the treatment adopted within the book. Thanks for the question.