fix doc users

docs/user/user_categories.md

@@ -57,8 +57,9 @@ There are 6 types of behaviors for replay users :
 
 Most of theses users will have a demande response window. It's in this window that they will apply their suffiency behavior.
 In the exmaples, the window will be between `3000` and `10 000`.
-Each of these users is given a workload to reproduce and a json file in parameter. This file gives the broker the information required.
-All of the outputs for the different users will be given the same json file.
+
+Each of these users is given a workload to reproduce and a json file in parameter. This file gives batmen the information required for the simulation.
+All of the outputs for the different users will be given in the same json file.
 ### replay_user_rigid
 Parameters required : name of the user, category of the user (here replay_user_rigid) and a json input.
 
@@ -132,8 +133,11 @@ Here is a gantt chart of the expected results :
 
 ![image](images/dm_renounce.png)
 
-Here we can see that session 2 and session 3 have been renounced. Indeed, each job is renounced as soon as it is subimmted. However the think-time (2000) is preserved. Here's the timeline of this small example.
-The sessions 2 is submitted at 4000 but since it's in the demande respoonse window, it is renounced. After the think-time, at 6000 session 3 is submitted and renounced. Then at 8000 sessions 4 is also submitted and renounced. Sessions 4 is submittted outside of the window therefore we can see it on the gantt chart.
+Here we can see that session 2 and session 3 have been renounced. Indeed, each job is renounced as soon as it is subimmted. However the think-time (2000) is preserved. Here's the timeline of this small example :
+* The session 2 is submitted at 4000 but since it's in the demande respoonse window, it is renounced.
+* After the think-time, at 6000 session 3 is submitted and renounced.
+* Then at 8000 session 4 is also submitted and renounced.
+* Session 4 is submittted outside of the window therefore we can see it on the gantt chart.
 
 ### dm_user_delay
 Parameters required : name of the user, category of the user (here dm_user_delay) and a json input.