From fcf93d4db5368d691ddcf301e7666ec54d63b792 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Pavel=20Jir=C3=A1sek?= <pavel.jirasek@vsb.cz>
Date: Fri, 27 Jan 2017 10:10:46 +0100
Subject: [PATCH] Fix ml instead confusing module and Fix missing -

---
 docs.it4i/software/lmod.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs.it4i/software/lmod.md b/docs.it4i/software/lmod.md
index 850e50b70..c1deaeff2 100644
--- a/docs.it4i/software/lmod.md
+++ b/docs.it4i/software/lmod.md
@@ -234,11 +234,11 @@ Currently Loaded Modules:
 
 For example, once you have loaded one or more modules that were installed with the intel/2017.00 toolchain, all other modules that you load should have been installed with the same toolchain.
 
-In addition, only **one single version** of each software package can be loaded at a particular time. For example, once you have the Python/3.5.2-intel-2017.00 module loaded, you can not load a different version of Python in the same session/job script; neither directly, nor indirectly as a dependency of another module you want to load.
+In addition, only **one single version** of each software package can be loaded at a particular time. For example, once you have the Python/3.5.2-intel-2017.00 module loaded, you can not load a different version of Python in the same session/job script, neither directly, nor indirectly as a dependency of another module you want to load.
 
-Unloading modules: ml modname(s) (module unload modname(s))
+Unloading modules: ml -modname(s) 
 
-To revert the changes to the environment that were made by a particular module, you can use module unload or ml -<modname>.
+To revert the changes to the environment that were made by a particular module, you can use ml -<modname>.
 For example:
 
 ```bash
-- 
GitLab