While classifying changes, we noticed patterns in the meta-data (e.g.,bug-fixing tasks often had fewer changes than tasks implementing new functionality). We built a regression model on the technical influences of the review process to detect what could influence the number of changes made in reviews. We show that bug-fixing tasks lead indeed to fewer changes and that tasks with more altered files and a higher code churn have more changes on average. Interestingly, the reviewer has no impact on the number of changes. In interviews, developers confirmed our results match their intuition. Structure of the paper: Section 2 introduces a common nomenclature on code reviews and provides an overview of the related work. Section 3 details our methodology: It introduces our initial research questions, the subject systems and the steps we took to conduct our investigation; subsequently, it details another research question, which emerged from our manual classification, and the steps to answer it. Section 4 presents the results for our research questions. We discuss the findings in Section 5 and conclude in Section 6.