review README.md

README.md

@@ -16,7 +16,7 @@ It is launched usually like this : `ansible-playbook site.yml`
 
 Hosts should be accessible via SSH as the root user (else, add the usual
 `remote_user`/`become` instructions in ansible.cfg) and with the Python
-prerequisite of Ansible (usually 
+prerequisite of Ansible (usually `python-minimal`).
 
 Only tested on Debian 10 amd64 so far, with Ansible 2.7.7.
 
@@ -36,10 +36,14 @@ with :
 - `roles/common/`, `roles/fooapp/` : the roles with their tree `tasks/main.yml`, `files/`, `handlers/main.yml`, ...
 - `group_vars/group1.yml` and `host_vars/hostname1.yml` : variables dedicated to a group or a host respectively.
 
-Note : contrary to some recommendations, I prefer to set the maximum of variables in the inventory instead of `host_vars` and `group_vars`. For a small playbook like this one, it seems acceptable.
+Note : contrary to some recommendations, I prefer to set some variables in
+the inventory instead of `host_vars` and `group_vars`. For a small playbook
+like this one, it seems acceptable and it makes it easier to look where to
+adapt.
 
 ## TODO
 
 - stop execution if host is running an untested system ?
 - use jenkins-cli to maintain credentials.xml ? It's not really easy to manipulate in Ansible at the moment...
 - update plugins, or at least display a warning when they are not up to date.
+- configure NginX