Minor fixes

Author: Marc-Andrieu

README.md

@@ -243,7 +243,7 @@ Check this file to know what can and should be set using these two files.
 
 ### The `.env` file
 
-The `.env` contains environment variables which need to be accessed by the OS or by other services, such as the database.
+The `.env` contains environment variables which can to be accessed by the OS or by other services, such as the database.
 
 #### With SQLite
 
@@ -324,7 +324,7 @@ There are at least 5 distinct ways to do so outside the use of factories, ranked
 
 > [!IMPORTANT]
 > Using factories is the recommended way.
-> All others methods are legacy and kept here for historical reasons.
+> All others methods are legacy and kept here for historical reasons (excepted using Titan, which is the way users create their account in production).
 > Feel free to create other users other ways for learning purposes.
 
 Note that registration and activation are distinct steps when calling calls to the API, so for fun you may register one way and activate your account another way (if you create your user directly in database, this distinction is not relevant).

config.template.yaml

@@ -99,7 +99,6 @@ AUTH_CLIENTS:
 SQLITE_DB: app.db # If set, the application use a SQLite database instead of PostgreSQL, for testing or development purposes (if possible PostgreSQL should be used instead)
 DATABASE_DEBUG: False # If True, will print all SQL queries in the console
 LOG_DEBUG_MESSAGES: False
-NB_WORKERS: 6 # Not yet used...
 
 #############
 # Factories #