another thing that SMPI cannot do yet

[simgrid.git] / docs / source / app_s4u.rst

diff --git a/docs/source/app_s4u.rst b/docs/source/app_s4u.rst
index a3c853cf792b3aa70b0b01b16124dd0ea484df95..7fb666447049bb99f4fd7b3746b42ea3d8ea5124 100644 (file)
--- a/docs/source/app_s4u.rst
+++ b/docs/source/app_s4u.rst
@@ -20,7 +20,7 @@ with the full power of C++. This is the preferred interface to describe
 abstract algorithms in the domains of Cloud, P2P, HPC, IoT, and similar
 settings.
 
-Currently (v3.21), S4U is definitely the way to go for long-term
+Since v3.20 (June 2018), S4U is definitely the way to go for long-term
 projects. It is feature complete, but may still evolve slightly in the
 future releases. It can already be used to do everything that can be
 done in SimGrid, but you may have to adapt your code in future
@@ -359,6 +359,13 @@ Here is a little example:
 API Reference
 *************
 
+.. _API_s4u_this_actor:
+
+=========================
+namespace s4u::this_actor
+=========================
+
+.. doxygennamespace:: simgrid::s4u::this_actor
 .. _API_s4u_Activity:
 
 =============
@@ -555,11 +562,3 @@ s4u::VirtualMachine
    :protected-members:
    :undoc-members:
 
-.. _API_s4u_this_actor:
-
-=========================
-namespace s4u::this_actor
-=========================
-
-
-.. doxygennamespace:: simgrid::s4u::this_actor