diff --git a/content/applications/user_software/using_anaconda_package_manager.md b/content/applications/user_software/using_anaconda_package_manager.md
index 13cbb732599e7d8fc693599ac61282e269ffdf55..f61c2a7b68ca8062ca82073cbbd7b14dc87d854e 100644
--- a/content/applications/user_software/using_anaconda_package_manager.md
+++ b/content/applications/user_software/using_anaconda_package_manager.md
@@ -253,7 +253,8 @@ Some conda packages available on `conda-forge` and `bioconda` support MPI (via `
 
 In order to be able to correctly use these MPI packages with the MPI libraries installed on our clusters, two steps need to be performed. 
 
-First, at install time, besides the package, the package `openmpi=4.1.*=external_*` or `mpich=4.0.*=external_*` needs to be installed for `openmpi` or `mpich` respectively. 
+First, at install time, besides the package, the "dummy" package `openmpi=4.1.*=external_*` or `mpich=4.0.*=external_*` needs to be installed for `openmpi` or `mpich` respectively. 
+These "dummy" packages are empty, but allow the solver to create correct environments and use the system-wide modules when the environment is activated.
 
 Secondly, when activating the conda environment and using the package, the system-wide `openmpi/4.1` or `mpich/4.0` module needs to be loaded depending on the MPI library used.