This is a good idea, thanks!

I think we should explain:

- Who will review the code (the other developers + interested community members)
- Where does this happen (on a PR)

Rephrase: "This step makes..." -- "Code review ensures high quality code, homogeneous style and optimal performance."

Also, mention that everyone has their code reviewed, and that contributors should not be discouraged if it takes a couple of iterations.  Explain how Travis-CI helps, and that it includes the output of unit tests, coverage and style checking.

When describing how to update the PR, mention it explicitly:

* 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.