docs: fix cron scheduling README doc

README.Cron

@@ -5,13 +5,13 @@ WARNING: FusionInventory Agent would better be installed as systemd service and
 this is the recommanded way of doing.
 
 FusionInventory agent is expected to run its tasks on a regular basis and is better
-installed as service. Its memory and load footprints are low enough for this mode.
+installed as service. Its memory and load footprints are low enough for modern desktop computers.
 
-To know better about the FusionInventory agent execution modes, you should be read
-the our online Agent usage page:
+To know better about the FusionInventory agent execution modes, you should read
+the online Agent usage page:
 http://fusioninventory.org/documentation/agent/usage.html
 
-Cron mode could be used if you don't want a fusioninventory-agent process to be running
+You should use cron if you don't want a fusioninventory-agent process to be running
 all the time and if you don't need to trigger it remotely (from the server
 or manually, locally contacting the `http://localhost:62354/` page).
 
@@ -32,16 +32,17 @@ to do the following as root:
    # time before really run its work
    00 */4 * * * /usr/bin/fusioninventory-agent --wait=1800 >/var/lib/fusioninventory-agent/cron.log 2>&1
 
-For large companies, be aware, if you don't enable lazy option in cron mode and you schedule
-many computer to make inventory at the same cron time, you can flood your GLPI server at the
-scheduled time, even more if you forget to use `--wait` option. To avoid such missconfiguration,
-you would prefer leave the agent started as systemd service and define a peaceful delay
-on server. You may adjust scheduled time and wait command line only option to your needs.
-
-As a reminder, cron mode disables the httpd daemon listening feature permitting server
-to manually and remotely trigger fusioninventory-agent to run its tasks.
+For large companies, be aware you can lead to concurrent execution issues
+if you don't enable agent `lazy` option with cron scheduling and even more if you forget to
+use `--wait` option. To avoid such missconfiguration, you would prefer leave the agent
+started as systemd service and define a peaceful delay on server. You may adjust scheduled
+time and wait command line only option to your needs.
 
+As a reminder, when launched without the daemonize configuration directive
+as usually done from cron, the agent is a short-lived process, without
+the ability to listen on the network for out-of-schedule activation requests
+from the server.
 ===
 
-Review our mandatory agent cron mode page:
+Review our mandatory 'schedule agent with cron' page:
 http://fusioninventory.org/documentation/agent/cron.html