X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/7b2fc8bedc387827d08ba51bab95468c2a1f14e3..aad6b6c4c7b1454dd284f822ba6f52e790f42c6e:/doc/doxygen/module-index.doc

diff --git a/doc/doxygen/module-index.doc b/doc/doxygen/module-index.doc
index 0f252d6d61..3e0c376145 100644
--- a/doc/doxygen/module-index.doc
+++ b/doc/doxygen/module-index.doc
@@ -8,15 +8,15 @@
 @brief Gather data about your simulation for later analysis
 
 SimGrid can trace the resource (of hosts and links) utilization using
-any of its programming interfaces (MSG, SimDAG and SMPI). This means
+any of its programming interfaces (S4U, SimDAG and SMPI). This means
 that the tracing will register how much power is used for each host
 and how much bandwidth is used for each link of the platform.
 
 The idea of the tracing facilities is to give SimGrid users to
-possibility to classify MSG and SimDAG tasks by category, tracing the
+possibility to classify S4U and SimDAG tasks by category, tracing the
 platform utilization (hosts and links) for each of the categories.
 The API enables the declaration of categories and a function to
-associate them to the tasks (MSG and SD). The tasks that are not
+associate them to the tasks (S4U and SD). The tasks that are not
 classified according to a category are not traced. If no categories
 are specified, simulations can still be traced using a special
 parameter in the command line (see @ref outcomes_vizu for details).