docs: update assertions documentation

Author: AayushSabharwal

docs/src/basics/Debugging.md

@@ -42,15 +42,31 @@ Suppose we also want to validate that `u1 + u2 >= 2.0`. We can do this via the a
 ```
 
 The assertions must be an iterable of pairs, where the first element is the symbolic condition and
-the second is the message to be logged when the condition fails.
+the second is a message to be logged when the condition fails. All assertions are added to the
+generated code and will cause the solver to reject steps that fail the assertions. For systems such
+as the above where the assertion is guaranteed to eventually fail, the solver will likely exit
+with a `dtmin` failure..
+
+```@example debug
+prob = ODEProblem(sys, [], (0.0, 10.0))
+sol = solve(prob, Tsit5())
+```
+
+We can use `debug_system` to log the failing assertions in each call to the RHS function.
 
 ```@repl debug
 dsys = debug_system(sys; functions = []);
 dprob = ODEProblem(dsys, [], (0.0, 10.0));
 dsol = solve(dprob, Tsit5());
 ```
 
-Note the messages containing the failed assertion and corresponding message.
+Note the logs containing the failed assertion and corresponding message. To temporarily disable
+logging in a system returned from `debug_system`, use `ModelingToolkit.ASSERTION_LOG_VARIABLE`.
+
+```@repl debug
+dprob[ModelingToolkit.ASSERTION_LOG_VARIABLE] = false;
+solve(drob, Tsit5());
+```
 
 ```@docs
 debug_system