fixup! doc

erts/doc/guides/match_spec.md

@@ -204,7 +204,9 @@ The functions allowed only for tracing work as follows:
   process as a binary. Takes no arguments and is only allowed in the `MatchBody`
   part when tracing.
 
-- **`enable_trace`** - With one parameter this function turns on tracing like
+- **`enable_trace`** - Enable a trace flag for a process.
+
+  With one parameter this function turns on tracing like
   the Erlang call [`trace:process(S, self(), true, [P2])`](`trace:process/4`),
   where `S` is the current trace session and `P2` is the parameter to
   `enable_trace`.
@@ -223,7 +225,9 @@ The functions allowed only for tracing work as follows:
   its trace messages sent to the same tracer as the process executing the
   statement uses.
 
-- **`disable_trace`** - With one parameter this function disables tracing like
+- **`disable_trace`** - Disable a trace flag for a process.
+
+  With one parameter this function disables tracing like
   the Erlang call [`trace:process(S, self(), false, [P2])`](`trace:process/4`),
   where `S` is the current trace session and `P2` is the parameter to
   `disable_trace`.
@@ -236,7 +240,9 @@ The functions allowed only for tracing work as follows:
 
   Returns `true` and can only be used in the `MatchBody` part when tracing.
 
-- **`trace`** - With two parameters this function takes a list of trace flags to
+- **`trace`** - Enable and/or disable trace flags for a process.
+
+  With two parameters this function takes a list of trace flags to
   disable as first parameter and a list of trace flags to enable as second
   parameter. Logically, the disable list is applied first, but effectively all
   changes are applied atomically. The trace flags are the same as for