Update actions.qmd

Author: rich-iannone

docs/user-guide/actions.qmd

@@ -70,7 +70,7 @@ considered optional. Put another way, you can set various thresholds and various
 and the interrogation phase will determine whether all the requirements are met for executing
 an action.
 
-## Ways to Express Actions: Text or Custom Functions
+## Expressing Actions with a String
 
 There are a few options in how to define the actions:
 
@@ -99,7 +99,6 @@ Here's an example where we prepare a console message with a number of value plac
 (`action_str`) and use it globally at `Actions(critical=)`:
 
 ```{python}
-
 action_str = "[{LEVEL}: {TYPE}]: Step {step} has failed validation. ({time})"
 
 validation_2 = (
@@ -123,15 +122,18 @@ resulting text is capitalized (e.g., `"CRITICAL"`, `"COL_VALS_GT"`, etc.) and th
 capitalized the placeholder text itself. Have a look at the documentation article of
 [`Actions`](https://posit-dev.github.io/pointblank/reference/Actions.html) for more details on this.
 
+## Making Actions with Callables
+
 Aside from strings, any callable can be used as an action value. Here's an example where we use a
 custom function as part of an action:
 
 ```{python}
-def dq_issue():
+def duration_issue():
     from datetime import datetime
 
     print(f"Data quality issue found ({datetime.now()}).")
 
+
 validation_3 = (
     pb.Validate(
         data=pb.load_dataset(dataset="game_revenue", tbl_type="duckdb"),
@@ -142,7 +144,7 @@ validation_3 = (
     .col_vals_gt(
         columns="session_duration",
         value=15,
-        actions=pb.Actions(warning=dq_issue),
+        actions=pb.Actions(warning=duration_issue),
     )
     .interrogate()
 )