added most requested changes for the EESSI as a module part

docs/using_eessi/setting_up_environment.md

@@ -8,7 +8,7 @@ There are a few different scenarios where you may want to set up the EESSI envir
 
    !!! note "Why do we recommend to unset `MODULEPATH`?"
 
-   Unsetting the `$MODULEPATH` environment variable, which tells Lmod in which directories environment module files are available, may be necessary. The underlying reason for this recommendation is that EESSI and your system are most likely based on two different operating system distributions. EESSI uses a [compatibility layer](../compatibility_layer.md), while your system almost certainly uses another Linux distribution. If you can find a way to ensure that the _software stacks_ from your site and EESSI do not mix (especially when someone is building new software), then this should be sufficient.
+      Unsetting the `$MODULEPATH` environment variable, which tells Lmod in which directories environment module files are available, may be necessary. The underlying reason for this recommendation is that EESSI and your system are most likely based on two different operating system distributions. EESSI uses a [compatibility layer](../compatibility_layer.md), while your system almost certainly uses another Linux distribution. If you can find a way to ensure that the _software stacks_ from your site and EESSI do not mix (especially when someone is building new software), then this should be sufficient.
 
 1.  You are already using Lmod with version >= 8.6