...
"The purpose of a code review is for someone other than the programmer to critically go through the code of a module to ensure that it meets the functional and design specifications, is wellwritten well-written and robust. An incidental benefit is that the reviewer may learn some new programming techniques, and more people in the team become familiar with the module. The reviewer should not try to fix any bugs or improve the code. S/he should merely inform the programmer about potential bugs and possible improvements. The responsibility for actually making the changes and testing them lies with the programmer. " file:///Users/jeshiver/Downloads/Code-Review-Principles-Process-and-Tools.pdf
...