diff --git a/README.html b/README.html
index 7a2a80ef1c5cd536120cc3108d8681b9b29a2b93..a7ef1a6bfadc290793a1b1e729b7f1349472d8e1 100644
--- a/README.html
+++ b/README.html
@@ -159,7 +159,7 @@
 </ul>
 <h3 id="reproducing-the-measurements">Reproducing the Measurements</h3>
 <p><strong><span style="color:red">Please Note: Reproducing the graphs as presented in the paper and supplied here takes a very long time depending on the utilized hardware. It is strongly suggested running the benchmark with a smaller maximum problem size, fewer repetitions, and a shorter timeout.</span></strong> Most results of the benchmark are observable with more restricted setup as well. In the following, we will provide a suggested way to run the benchmark in different sizes. Note that running the benchmark requires a significant amount of disk space (up to 10GB when running the full benchmark).</p>
-<p>To reproduce the measurements, there are several options. We provide a prepared Docker image that can be run directly. Alternatively, it is, on course, also possible to simply run the provided gradle build scripts. However, since there are some software requirements imposed by the benchmark, particularly for creating the diagrams using R. We strongly suggest running the Docker variant.</p>
+<p>To reproduce the measurements, there are several options. We provide a prepared Docker image that can be run directly. Alternatively, it is, of course, also possible to simply run the provided gradle build scripts. However, since there are some software requirements imposed by the benchmark, particularly for creating the diagrams using R. We strongly suggest running the Docker variant.</p>
 <h4 id="running-the-benchmark-with-docker">Running the Benchmark with Docker</h4>
 <h5 id="loading-the-docker-image">Loading the Docker Image</h5>
 <ul>
diff --git a/README.md b/README.md
index 104d52e2531609eeb36df0379729a34ee99852ff..52008ac51f6d76a0913d48fd5d63375d0e304237 100644
--- a/README.md
+++ b/README.md
@@ -143,7 +143,7 @@ These are the important directories:
 **<span style="color:red">Please Note: Reproducing the graphs as presented in the paper and supplied here takes a very long time depending on the utilized hardware. It is strongly suggested running the benchmark with a smaller maximum problem size, fewer repetitions, and a shorter timeout.</span>** Most results of the benchmark are observable with more restricted setup as well. In the following, we will provide a suggested way to run the benchmark in different sizes. Note that running the benchmark requires a significant amount of disk space (up to 10GB when running the full benchmark).
 
 To reproduce the measurements, there are several options. We provide a prepared Docker image that can be run directly.
-Alternatively, it is, on course, also possible to simply run the provided gradle build scripts.
+Alternatively, it is, of course, also possible to simply run the provided gradle build scripts.
 However, since there are some software requirements imposed by the benchmark, particularly for creating the diagrams using R. We strongly suggest running the Docker variant.
 
 #### Running the Benchmark with Docker
diff --git a/README.txt b/README.txt
index 104d52e2531609eeb36df0379729a34ee99852ff..52008ac51f6d76a0913d48fd5d63375d0e304237 100644
--- a/README.txt
+++ b/README.txt
@@ -143,7 +143,7 @@ These are the important directories:
 **<span style="color:red">Please Note: Reproducing the graphs as presented in the paper and supplied here takes a very long time depending on the utilized hardware. It is strongly suggested running the benchmark with a smaller maximum problem size, fewer repetitions, and a shorter timeout.</span>** Most results of the benchmark are observable with more restricted setup as well. In the following, we will provide a suggested way to run the benchmark in different sizes. Note that running the benchmark requires a significant amount of disk space (up to 10GB when running the full benchmark).
 
 To reproduce the measurements, there are several options. We provide a prepared Docker image that can be run directly.
-Alternatively, it is, on course, also possible to simply run the provided gradle build scripts.
+Alternatively, it is, of course, also possible to simply run the provided gradle build scripts.
 However, since there are some software requirements imposed by the benchmark, particularly for creating the diagrams using R. We strongly suggest running the Docker variant.
 
 #### Running the Benchmark with Docker