Explain why pipx, but allow pip too

As suggested by Lecrapouille and cgestes
in your-tools#332, your-tools#366, your-tools#343.

README.md

@@ -17,13 +17,16 @@ repositories.
 
 It can be [seen in action on asciinema.org](https://asciinema.org/a/131625).
 
+## Requirements
+
+
+Python **3.7** or later
+
 ## Installation
 
-The recommended way to install `tsrc` is to use [pipx](https://pipxproject.github.io/pipx/).
+Use `pipx` (recommended) or `pip` (ok, if you know what you're doing) to install.
 
-* Make sure to have Python **3.7** or later installed.
-* Install `pipx`
-* Run `pipx install tsrc`.
+Please see the [installation docs](https://your-tools.github.io/tsrc/getting-started/#installing_tsrc) for more info.
 
 ## Usage Example
 

docs/getting-started.md

@@ -1,14 +1,24 @@
 # Getting started
 
+## Requirements
+
+Python 3.7 or later
+
 ## Installing tsrc
 
-The recommended way to install `tsrc` is to use [pipx](https://pypa.github.io/pipx/)
+The recommended way to install `tsrc` is to use [pipx](https://pypa.github.io/pipx/). This is because `pipx` automatically creates isolated environment for each app, so you won't get into dependencies versions conflicts and won't have to deal with manual virtualenvs management. 
 
-* Make sure to have Python 3.7 or later installed.
-* Install pipx
-* Run `pipx install tsrc`
+`pip` will also work, but it will not give you these benefits.
 
-You can also install `tsrc` with `pip` if you know what you are doing :)
+Recommended:
+```shell
+pipx install tsrc
+```
+
+Acceptable, if you know what you are doing:
+```shell
+pip install tsrc
+```
 
 ## Checking tsrc installation