From 5fd92acd46e868982725be9b2c54b0b207b6f80d 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:03:07 +0100
Subject: [PATCH] Fix ml instead confusing module
---
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 e43df08b9..850e50b70 100644
--- a/docs.it4i/software/lmod.md
+++ b/docs.it4i/software/lmod.md
@@ -168,7 +168,7 @@ Use "module keyword key1 key2 ..." to search for all possible modules matching a
## Inspecting a Module
-To see how a module would change the environment, use ml show or ml show:
+To see how a module would change the environment, use ml show:
```bash
$ ml show Python/3.5.2
@@ -199,11 +199,11 @@ setenv("EBEXTSLISTPYTHON","setuptools-20.1.1,pip-8.0.2,nose-1.3.7")
!!! tip
Note that both the direct changes to the environment as well as other modules that will be loaded are shown.
-If you're not sure what all of this means: don't worry, you don't have to know; just try loading the module as try using the software.
+If you're not sure what all of this means: don't worry, you don't have to know, just try loading the module as try using the software.
## Loading Modules
-The effectively apply the changes to the environment that are specified by a module, use module load or ml and specify the name of the module.
+The effectively apply the changes to the environment that are specified by a module, use ml and specify the name of the module.
For example, to set up your environment to use intel:
```bash
--
GitLab