From efc2ba1b0587c02689f9733caf5a0d929d38ddb1 Mon Sep 17 00:00:00 2001
From: Bienchen <stefan.bienert@unibas.ch>
Date: Tue, 4 Oct 2022 08:16:09 +0000
Subject: [PATCH] Update README.md

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index f42db33..4282253 100644
--- a/README.md
+++ b/README.md
@@ -62,7 +62,7 @@ $ DOCKER_BUILDKIT=1 docker build -t registry.scicore.unibas.ch/schwede/ma-wilkin
 
 `DOCKER_BUILDKIT=1` is only needed for some older versions of Docker.
 
-<a name="builduserid"></a>The Dockerfile knows two build time arguments (`--build-arg`), `MMCIF_USER_ID` and `ADD_DEV`. The latter is only used for developing the app. `MMCIF_USER_ID` sets the ID of the user running the translation script inside the Docker container. So files written by the Docker container belong to the user ID of the internal user. When you run into file permission issues with the produced ModelCIF files, build the Docker container using your own user ID:
+<a name="builduserid"></a>The Dockerfile knows two [build time arguments](https://docs.docker.com/engine/reference/commandline/build/#set-build-time-variables---build-arg) (`--build-arg`), `MMCIF_USER_ID` and `ADD_DEV`. The latter is only used for developing the app. `MMCIF_USER_ID` sets the ID of the user running the translation script inside the Docker container. So files written by the Docker container belong to the user ID of the internal user. When you run into file permission issues with the produced ModelCIF files, build the Docker container using your own user ID:
 
 ```terminal
 $ DOCKER_BUILDKIT=1 docker build --build-arg MMCIF_USER_ID=<YOUR USER ID> -t registry.scicore.unibas.ch/schwede/ma-wilkins-import/converter:latest .
@@ -118,7 +118,7 @@ To actually run the conversion, we assume the ColabFold projects are separated i
 
 There can be more models for the same combination of the two UniProtKB ACs in a directory, the above example just shows the minimum required files.
 
-Since the Docker container does not see the file system of the computer it is running on, the top level directory of the projects needs to be mounted when running. This happens with the `-v` option and gets absolute paths to the project directory and the mount point inside the Docker container, e.g. `-v /path/to/projects:/data` makes the directory `/path/to/projects` on your computer, available as `/data` to the Docker container.
+Since the Docker container does not see the file system of the computer it is running on, the top level directory of the projects needs to be mounted when running. This happens with the `-v` option and gets absolute paths to the projects directory and the mount point inside the Docker container, e.g. `-v /path/to/projects:/data` makes the directory `/path/to/projects` on your computer, available as `/data` to the Docker container.
 
 Running the converter app to write the ModelCIF file back into the project directory for model of rank 1 looks like this:
 
-- 
GitLab