X-Git-Url: https://git.lttng.org/?p=lttng-tools.git;a=blobdiff_plain;f=doc%2Fman%2Flttng-concepts.7.txt;fp=doc%2Fman%2Flttng-concepts.7.txt;h=54718afd2d67eee93ed8dab4b41f885aac251f59;hp=9ea1f246a03b33e268c3ba996f2e5ee68f8c112e;hb=7013e16714631ec4798f8700866e206239d83eb8;hpb=baa2c8a47d9aad824dd5c78e66ea11c8661efb83

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 <<channel,{sect-channel}>> section
 below) in the Linux kernel and user space tracing domains. The other