From a540e9753c0df5118ac0b3dd838743ecf75c1630 Mon Sep 17 00:00:00 2001
From: Lukas Barragan Torres <lukas.barragantorres@ugent.be>
Date: Fri, 19 Jul 2024 15:12:50 +0200
Subject: [PATCH] remove confusing empty variable example

---
 mkdocs/docs/HPC/linux-tutorial/common_pitfalls.md | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/mkdocs/docs/HPC/linux-tutorial/common_pitfalls.md b/mkdocs/docs/HPC/linux-tutorial/common_pitfalls.md
index 4f10fafb0c4..2ad2ea1ab93 100644
--- a/mkdocs/docs/HPC/linux-tutorial/common_pitfalls.md
+++ b/mkdocs/docs/HPC/linux-tutorial/common_pitfalls.md
@@ -54,14 +54,6 @@ A common pitfall is the (accidental) use of non-defined variables.
 Contrary to what you may expect, this does *not* result in error
 messages, but the variable is considered to be *empty* instead.
 
-This may lead to surprising results, for example:
-<pre><code>$ <b>export WORKDIR=/tmp/test</b>
-$ <b>pwd</b>
-/user/home/gent/vsc400/vsc40000
-$ <b>echo $HOME</b>
-/user/home/gent/vsc400/vsc40000
-</code></pre>
-
 !!! tip
     For job scripts, use `set -e -u` to avoid using empty variables accidentally.