Doesn't look that way from the table of contents. As far as I remember, Uncle Bob's book "Agile Software Development - Principles, Patterns, Practices" has a chapter on Pair Programming, though.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
It is well know that code review is very effective in reducing bugs and improving code quality. Be it agile, when two developer are working over the same code, where review is happening while it is being coded, or when it is done by peer once a developer has finished with. Both has positive effect on the code.
But there are other trick issues involved with it some organizations.
Originally posted by Adeel Ansari: Is there any emphasis on continuous inspection in the book. I mean how we should practice this. Or may be best practices or something?
Indeed there is. The idea is simple. We should constantly and continuously improve our code. The book talks about the "Boy Scout Rule" which is that we should always check our code in just a bit cleaner than when we checked it out.