Update doc for archive job

Author: FOLIOT Kevin

docs/40-DeveloperGuide/30-WorkerService/50-ArchiveJob.md

@@ -5,15 +5,13 @@ sidebar_position: 1
 # Archive Job (Worker Feature)
 The archive job is a recurred task created to archive entities from database into flat text on a target directory and then delete them from database.
 
-## How it works
-Following descriptions will use defaults values of the archive job set in the BIA Framework.  
-
-1. Archive job is launched from Hangfire throught the Worker Service each day at 04:00 AM (GMT+1).
-2. Each injected implementation of `IArchiveService` related to a specific archivable entity (`IEntityArchivable` that inherits from `IEntityFixable`) of the dabatase will be runned one per one
+## How it works 
+1. Archive job is launched from Hangfire Server throught the Worker Service each day at 04:00 AM (GMT+1).
+2. Each injected implementation of `IArchiveService` related to a specific archivable entity (`IEntityArchivable`) of the dabatase will be runned one per one
 3. The items to archive will be selected according to following rules from the related `ITGenericArchiveRepository` of the archive service :
    - Entity is fixed
    - Entity has not been already archived **OR** entity has already been archived and last fixed date has been updated since the last 24 hours
-4. The selected items are saved into compressed archive file to the target directory one per one (one file per item, overwritten). Each copy to the target directory is verified by an integrity comparison of checksum.
+4. The selected items are saved into compressed archive file to the target directory one per one : unique file per item, overwritten. Each copy to the target directory is verified by an integrity comparison of checksum.
 5. If enable, the items to delete from database will be only those archived more than last past year
 
 ## Configuration