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
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