How-to-prepare-the-code-for-a-release.md

 Here is the checklist to run before releasing a new version for mbtrack2:
 
 1. Create a new local branch from the merge develop (with all the feature branch intended to be included in the new version).
-2. Update readthedocs documentation
+2. Update .rst for the readthedocs documentation
 3. Book a new zenodo DOI and update readme.md and __init__.py
 4. Update the pyproject.toml file with version number, new dependencies and so on.
 5. Update README.md
@@ -24,3 +24,4 @@ Here is the checklist to run before releasing a new version for mbtrack2:
    * `poetry config http-basic.pypi __token__ api_token`
    * `poetry publish`
 10. Add zip archive of stable to zenodo
+11. Rebuild docs on the https://app.readthedocs.org/ website
\ No newline at end of file