From 7013e16714631ec4798f8700866e206239d83eb8 Mon Sep 17 00:00:00 2001 From: Philippe Proulx Date: Tue, 18 May 2021 10:18:41 -0400 Subject: [PATCH] lttng-concepts(7): add missing "commands" word MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit Signed-off-by: Philippe Proulx Signed-off-by: Jérémie Galarneau Change-Id: Ib555c944c37b983a40f963ea3597bafeba6c4da2 --- doc/man/lttng-concepts.7.txt | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/man/lttng-concepts.7.txt b/doc/man/lttng-concepts.7.txt index 9ea1f246a..54718afd2 100644 --- a/doc/man/lttng-concepts.7.txt +++ b/doc/man/lttng-concepts.7.txt @@ -543,12 +543,12 @@ There are currently five available tracing domains: |=== You must specify a tracing domain to target a type of LTTng tracer when -using some man:lttng(1) to avoid ambiguity. For example, because the -Linux kernel and user space tracing domains support named tracepoints as -instrumentation points (see the <<"event-rule","{sect-event-rule}">> section -above), you need to specify a tracing domain when you create an event -rule because both tracing domains could have tracepoints sharing the -same name. +using some man:lttng(1) commands to avoid ambiguity. For example, +because the Linux kernel and user space tracing domains support named +tracepoints as instrumentation points (see the +<<"event-rule","{sect-event-rule}">> section above), you need to specify +a tracing domain when you create an event rule because both tracing +domains could have tracepoints sharing the same name. You can create channels (see the <> section below) in the Linux kernel and user space tracing domains. The other -- 2.34.1