Add new entry in Release_Notes.

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

diff --git a/docs/source/Modeling_howtos.rst b/docs/source/Modeling_howtos.rst
index f6589f7..0840cee 100644 (file)
--- a/docs/source/Modeling_howtos.rst
+++ b/docs/source/Modeling_howtos.rst
@@ -93,6 +93,10 @@ Another possibility is to use the
 functions take a profile, that can be a fixed profile exhaustively
 listing the events, or something else if you wish.
 
+For further reading, you could turn to :ref:`this example <s4u_ex_comm_failure>`
+on how to react to communication failures, or  :ref:`this one <s4u_ex_platform_state_profile>`
+on how to attach a state profile to hosts and react to execution failures.
+
 .. _howto_multicore:
 
 Modeling multicore machines
@@ -152,9 +156,9 @@ programs actually die and restart during a reboot. Since there are many
 ways to model it, SimGrid does not do any modeling choice for you but
 the most obvious ones.
 
-Any actor running on a host that is shut down will be killed and all 
-its activities will be automatically canceled. If the actor killed was 
-marked as auto-restartable (with :cpp:func:`simgrid::s4u::Actor::set_auto_restart`), 
+Any actor running on a host that is shut down will be killed and all
+its activities will be automatically canceled. If the actor killed was
+marked as auto-restartable (with :cpp:func:`simgrid::s4u::Actor::set_auto_restart`),
 it will start anew with the same parameters when the host boots back up.
 
 By default, shutdowns and boots are instantaneous. If you want to