From 857a4df7e6f8df14797972861ce6bf1ab51af3e5 Mon Sep 17 00:00:00 2001
From: Jan Frenzel <jan.frenzel@tu-dresden.de>
Date: Wed, 20 Oct 2021 12:45:03 +0200
Subject: [PATCH] Apply 1 suggestion(s) to 1 file(s)

---
 doc.zih.tu-dresden.de/docs/software/virtual_machines_tools.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc.zih.tu-dresden.de/docs/software/virtual_machines_tools.md b/doc.zih.tu-dresden.de/docs/software/virtual_machines_tools.md
index e38154336..1223e886f 100644
--- a/doc.zih.tu-dresden.de/docs/software/virtual_machines_tools.md
+++ b/doc.zih.tu-dresden.de/docs/software/virtual_machines_tools.md
@@ -128,7 +128,7 @@ As usual, more options can be shown by running `startInVM --help`, the most impo
 There are two special use cases for this script:
 
 1. Execute an arbitrary command inside the VM instead of getting a bash by appending the command to
-   the script. Example: `startInVM --arch=power9 singularity build \~/myContainer.sif  \~/myDefinition.de`
+   the script. Example: `startInVM --arch=power9 singularity build ~/myContainer.sif  ~/myDefinition.de`
 1. Use the script in a job manually allocated via srun/sbatch. This will work the same as when
    running outside a job but will **not** start a new job. This is useful for using it inside batch
    scripts, when you already have an allocation or need special arguments for the job system. Again
-- 
GitLab