diff --git a/cpp-tutorials/exercises/exercise02.cpp b/cpp-tutorials/exercises/exercise02.cpp
index cae5982..35bb6c8 100644
--- a/cpp-tutorials/exercises/exercise02.cpp
+++ b/cpp-tutorials/exercises/exercise02.cpp
@@ -57,6 +57,18 @@ int main()
     model.populations.set_difference_from_total({mio::AgeGroup(0), mio::osecir::InfectionState::Susceptible},
                                                 total_population);
     // Before running the simulation, we check if all initial values and parameters are within a valid range.
+    // MEmilio provides two related functions for this:
+    // - `check_constraints()` only checks the values. Every violated constraint is
+    // reported in the log, but nothing is changed. You have to fix the values yourself
+    // before simulating.
+    // - `apply_constraints()` checks and directly corrects the values (e.g., a
+    // negative compartment value is set to zero, a stay time that is too small
+    // is set to a minimal admissible value). Every correction is logged as a
+    // warning with the old and new value. Returns `True` if anything was
+    // corrected.
+    // Use `check_constraints()` when you need the simulation to use exactly the
+    // values you set. Use `apply_constraints()` when automatic correction to the
+    // closest valid values is acceptable.
     model.check_constraints();
 
     // *** Simulate flows. ***
diff --git a/cpp-tutorials/tutorial02.cpp b/cpp-tutorials/tutorial02.cpp
index c0b9ada..5429e61 100644
--- a/cpp-tutorials/tutorial02.cpp
+++ b/cpp-tutorials/tutorial02.cpp
@@ -57,6 +57,18 @@ int main()
                                                 total_population);
 
     // Before running the simulation, we check if all initial values and parameters are within a valid range.
+    // MEmilio provides two related functions for this:
+    // - `check_constraints()` only checks the values. Every violated constraint is
+    // reported in the log, but nothing is changed. You have to fix the values yourself
+    // before simulating.
+    // - `apply_constraints()` checks and directly corrects the values (e.g., a
+    // negative compartment value is set to zero, a stay time that is too small
+    // is set to a minimal admissible value). Every correction is logged as a
+    // warning with the old and new value. Returns `True` if anything was
+    // corrected.
+    // Use `check_constraints()` when you need the simulation to use exactly the
+    // values you set. Use `apply_constraints()` when automatic correction to the
+    // closest valid values is acceptable.
     model.check_constraints();
 
     // *** Simulate flows. ***
diff --git a/exercises/exercise02.py b/exercises/exercise02.py
index 2af0987..60a7753 100644
--- a/exercises/exercise02.py
+++ b/exercises/exercise02.py
@@ -94,6 +94,21 @@ def _(mo):
     mo.md(r"""
     Before running the simulation, we check if all initial values and parameters are within a valid range.
     *Note: MEmilio's `check_constraints()` returns `True` if a constraint is violated, and `False` if everything is fine.*
+    
+    MEmilio provides two related functions for this:
+
+    - `check_constraints()` only checks the values. Every violated constraint is
+    reported in the log, but nothing is changed. You have to fix the values yourself
+    before simulating.
+    - `apply_constraints()` checks and directly corrects the values (e.g., a
+    negative compartment value is set to zero, a stay time that is too small
+    is set to a minimal admissible value). Every correction is logged as a
+    warning with the old and new value. Returns `True` if anything was
+    corrected.
+
+    Use `check_constraints()` when you need the simulation to use exactly the
+    values you set. Use `apply_constraints()` when automatic correction to the
+    closest valid values is acceptable.
     """)
     return
 
diff --git a/tutorial02.py b/tutorial02.py
index 2dfbeba..055533b 100644
--- a/tutorial02.py
+++ b/tutorial02.py
@@ -94,6 +94,21 @@ def _(mo):
     mo.md(r"""
     Before running the simulation, we check if all initial values and parameters are within a valid range.
     *Note: MEmilio's `check_constraints()` returns `True` if a constraint is violated, and `False` if everything is fine.*
+
+    MEmilio provides two related functions for this:
+
+    - `check_constraints()` only checks the values. Every violated constraint is
+    reported in the log, but nothing is changed. You have to fix the values yourself
+    before simulating.
+    - `apply_constraints()` checks and directly corrects the values (e.g., a
+    negative compartment value is set to zero, a stay time that is too small
+    is set to a minimal admissible value). Every correction is logged as a
+    warning with the old and new value. Returns `True` if anything was
+    corrected.
+
+    Use `check_constraints()` when you need the simulation to use exactly the
+    values you set. Use `apply_constraints()` when automatic correction to the
+    closest valid values is acceptable.
     """)
     return