From e5c02cfc2b364b0a2e40d28f877bb0ecd203d2a2 Mon Sep 17 00:00:00 2001
From: Mariusz Wzorek <mariusz.wzorek@liu.se>
Date: Mon, 2 Oct 2023 09:49:36 +0000
Subject: [PATCH] Update README.MD

---
 README.MD | 25 +++++++++++++------------
 1 file changed, 13 insertions(+), 12 deletions(-)

diff --git a/README.MD b/README.MD
index 9cc97ea..a31a400 100644
--- a/README.MD
+++ b/README.MD
@@ -14,7 +14,7 @@ A full open-source release of the HFKN knowledge framework, including ROS2 drive
 
 
 
-Run the docker
+Running the docker
 --------------
 
 To fetch a prebuild docker:
@@ -29,38 +29,39 @@ Then to run it:
 make run
 ```
 
-The detail of each benchmark is described in our paper. The following is documentation on how to run the benchmarks and interpret the resulting data. The benchmark results are created in a folder `results` accessible from outside of the container. The command for the benchmarks are:
+Details of each benchmark are described in the paper. The following is documentation on how to run the benchmarks and interpret the resulting data.
+The benchmark results are created in a folder `results` accessible from outside of the container. The commands for the benchmarks are:
 
 - `run_benchmark_triplestore`: benchmark the triple store with or without versioning (used in 4.1 Evaluation of the versioning overhead)"
   It outputs several csv files of the form `bts_[optype]_[has_vers]_[number]` where `optype`:
-  * `in_del` meaning triples are inserted and deleted for each revisions
-  * `only_in` meaning triples are inserted for each revisions
-  * `only_del` meaning triples are deleted for each revisions
+  * `in_del` meaning triples are inserted and deleted for each revision
+  * `only_in` meaning triples are inserted for each revision
+  * `only_del` meaning triples are deleted for each revision
   And `has_ver` indicate if versioning is enabled (`versioning`), disabled (`no_versioning`) and if versioning is enabled, but signing is disabled (`versioning_no_signing`)
   The benchmark is run 10 times, the `number` indicates the iteration.
 
   The columns in CSV:
 
   * `time` indicates the time it took to compute a revision
-  * `insertions_count` the number of inserted triple since start
+  * `insertions_count` the number of inserted triples since start
   * `insertions_time` the time it took to insert the triples
-  * `deletions_count` the number of removed triple since start
-  * `deletions_time` the time it took to deleteq the triples
+  * `deletions_count` the number of removed triples since start
+  * `deletions_time` the time it took to delete the triples
 
 - `run_benchmark_rebase_raw`: benchmark for the rebase algorithm (used in 4.3 Evaluation of the Rebase Algorithm)"
   It outputs `rebase_raw.cvs` with the following three columns:
-  * `changes`: number of changes per revisions (e.g. number of triples added or removed)
+  * `changes`: number of changes per revision (e.g. number of triples added or removed)
   * `revisions`: number of revisions to rebase
   * `average_time`: average time it took to compute the rebase
 
-- `run_many_benchmark_revision_throughput_limit` : benchmark the maximum amount of revision that can be created for many different agents and documents (used in 4.5 Evaluating the Maximum Revision Creation Rate)"
+- `run_many_benchmark_revision_throughput_limit` : benchmark the maximum amount of revisions that can be created for many different agents and documents (used in 4.5 Evaluating the Maximum Revision Creation Rate)"
   It outputs `throughput_limit.cvs` with the following columns:
   * `agents` the number of agents
   * `documents` the number of documents
-  * `triples` the number of triples added in each revisions
+  * `triples` the number of triples added in each revision
   * `average_time` the average time for creating revisions and merging
 
-Build the docker
+Building the docker
 ----------------
 
 In case you want to rebuild the docker:
-- 
GitLab