corrected link to writingGoodReadmes.md

HowToCodeReview.md

@@ -25,7 +25,7 @@ If you (the author of code) want your code to be reviewed, please try to make li
   * you may want to review the code by yourself first. Ask yourself the question: will someone else be able to understand what you want to do in every line of code?
   * programming languages can be written in a specific *style*. Use a good *style guide* for your language ([Python](https://www.python.org/dev/peps/pep-0008/), [R](http://adv-r.had.co.nz/Style.html), (google for *"programming language" style guide*)) and adhere to it.
   * make sure your code does not depend on very specific requirements that are only met on your PC.
-  * write a readme-file. Read [this guide](readme.md) on what should be included in a readme-file.
+  * write a readme-file. Read [this guide](writingGoodReadmes.md) on what should be included in a readme-file.
   * use [Git](https://git-scm.com). This allows us to do incremental code reviews. It also shows you what the reviewer changed.
   * use Git and [Github](https://github.molgen.mpg.de/) for bigger projects to allow incremental code reviews with the tools of Github.