Improve README

Author: AndreuCodina

README.md

@@ -32,4 +32,4 @@ So, we'll use this rules to store settings:
 - A `.env.{environment}` file for each environment.
 - If a setting is in both `.env` and `.env.{environment}`, the one in `.env.{environment}` takes precedence.
 
-Regarding the location of those files, the typical is to save `.env` files in the root of the project, but due to some popular tools and packages (Jupyter, FastAPI, Docker Compose...) load automatically and exclusively the file `.env`, ignoring the environments and the priority order defined by the API (e.g., `.env.{environment}` has priority over `.env` because it's the current environment), then we need to store the `.env` files in another location (in this case, in the `api` folder) and give the backend the responsibility of loading them, taking into account the environment name.
+Regarding the location of those files, the typical is to save `.env` files in the root of the project, but due to some popular tools and packages (Jupyter, FastAPI, Docker Compose...) load automatically and exclusively the file `.env`, ignoring the environments and the priority order defined by the API (e.g., `.env.{environment}` has priority over `.env` because it's the current environment), then we need to store the `.env` files in another location (in this case, in the `api` folder) and give the API the responsibility of loading them, taking into account the environment name.