Stefan's comments

CONTRIBUTING.txt

@@ -56,15 +56,21 @@ For a more detailed discussion, read these :doc:`detailed documents
 
 4. Review process:
 
-    * Reviewers will write inline and/or general comments to improve the
-      implementation and the documentation. This step makes the quality of
-      scikit-image and ensures an homogeneous style as well as the best
-      performances.
+    * Reviewers (the other developers and interested community members) will
+      write inline and/or general comments on your Pull Request (PR) to improve
+      the implementation and the documentation. Everyone has their code reviewed
+      in the same manner, it should not discourage you to contribute and it is
+      actually a chance to improve your coding skills. Code review ensures high
+      quality code, homogeneous style and optimal performance.
 
-    * Modify the code and commit locally.
+    * To update your pull request, make your changes on your local repository
+      and commit. As soon as those changes are pushed up to the same branch as
+      before, the pull request will be automatically updated.
 
-    * Push your changes on GitHub as before. Your pull request will be
-      automatically updated.
+    * `Travis-CI <http://travis-ci.org/>`__, a continuous integration service
+      is triggered after each Pull Request update, to build the code, run the
+      unittests, measure the code coverage and check the coding style (PEP8) of
+      your branch.
 
 .. note::