From 9471ae9a74fdd7bcd4c32a3097311f1c9bbbb3c8 Mon Sep 17 00:00:00 2001 From: Sverker Eriksson Date: Wed, 28 Aug 2024 17:07:22 +0200 Subject: [PATCH] fixup! doc --- erts/doc/guides/match_spec.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/erts/doc/guides/match_spec.md b/erts/doc/guides/match_spec.md index a212d2266a4a..123a6a660e50 100644 --- a/erts/doc/guides/match_spec.md +++ b/erts/doc/guides/match_spec.md @@ -246,13 +246,13 @@ The functions allowed only for tracing work as follows: identifier or the registered name of a process to set trace flags on, the second is the disable list, and the third is the enable list. - When used by the new `m:trace` API, trace flag `tracer` is not allowed and the + When used via the new `m:trace` API, trace flag `tracer` is not allowed and the receiving tracer is always the tracer of the current session. - When used by the legacy function `erlang:trace_pattern/3`, trace flag `tracer` + When used via the legacy function `erlang:trace_pattern/3`, trace flag `tracer` is allowed. If no tracer is specified, the same tracer as the process executing the match specification is used (not the meta tracer). If that - process doesn't have tracer either, then trace flags are ignored. + process doesn't have a tracer either, then trace flags are ignored. When using a [tracer module](`m:erl_tracer`), the module must be loaded before the match specification is executed. If it is not loaded, the match fails.