lttng-concepts(7): add missing "commands" word

Signed-off-by: Philippe Proulx <eeppeliteloop@gmail.com>
Signed-off-by: Jérémie Galarneau <jeremie.galarneau@efficios.com>
Change-Id: Ib555c944c37b983a40f963ea3597bafeba6c4da2

diff --git a/doc/man/lttng-concepts.7.txt b/doc/man/lttng-concepts.7.txt
index 9ea1f246a03b33e268c3ba996f2e5ee68f8c112e..54718afd2d67eee93ed8dab4b41f885aac251f59 100644 (file)
--- 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