small modification to readme and dockerfile

Dockerfile

@@ -29,10 +29,11 @@ RUN Rscript /trainbenchmark/trainbenchmark-reporting/install.R
 WORKDIR /trainbenchmark
 
 COPY trainbenchmark/ /trainbenchmark/
-RUN chown -R user:user /trainbenchmark
 COPY docker /trainbenchmark/docker
-RUN chown -R user:user /trainbenchmark/docker
 COPY docker/bashrc /home/user/.bashrc
+RUN chown -R user:user /trainbenchmark
+RUN chown -R user:user /home/user/.bashrc
+USER user
 
 RUN ./gradlew --no-daemon preprocess
 RUN ./gradlew --no-daemon build shadowJar -x test

README.md

@@ -108,8 +108,8 @@ There are some naming conventions:
 - Model serialization-related modules start with `trainbenchmark-generator`.
 - All other modules are core modules of the bechmark.
 
-Since the JastAdd-based solutions use a preprocessor to generate Java files, for the presented variant, it is even more compolicated.
-Each JastAdd configuraration must be presented to the benchmark as a separate tool. Thus there are two directories for each variant, one for the bacht processing mode and one for the incremental mode.
+The JastAdd-based solutions use a preprocessor to generate Java files, for the presented variant.
+Each JastAdd configuraration must be presented to the benchmark as a separate tool. Thus there are two directories for each variant, one for the batch processing mode and one for the incremental mode.
 Because these two modes share almost all the source code, a third directory is used to store this shared code.
 Finally, there is a directory for code shared between all JastAdd variants.
 These are the important directories:
@@ -150,7 +150,6 @@ However, since there are some software requirements imposed by the benchmark, pa
     - Steps:
         - Unpack the provided archive and open a terminal in the extracted directory
         - `docker build -t trainbenchmark .`
-        - `docker run -it trainbenchmark`
 
 ##### Running the Docker Image