X-Git-Url: https://git.lttng.org/?a=blobdiff_plain;f=doc%2Fman%2Flttng-concepts.7.txt;h=f00eef2a769e19f8afdda73f18dcc1993e24b7e2;hb=101b92daa8a82c039c608e52ed8b1d4b88c36dfa;hp=9ea1f246a03b33e268c3ba996f2e5ee68f8c112e;hpb=4fc37e3e3bd41eb78cf322525bca3cced7f9f0ed;p=lttng-tools.git

diff --git a/doc/man/lttng-concepts.7.txt b/doc/man/lttng-concepts.7.txt
index 9ea1f246a..f00eef2a7 100644
--- a/doc/man/lttng-concepts.7.txt
+++ b/doc/man/lttng-concepts.7.txt
@@ -58,7 +58,7 @@ help understand the journey from an instrumentation point to the
 execution of actions.
 
 The actual creation of an event can be costly because LTTng needs to
-evalute the arguments of the instrumentation point.
+evaluate the arguments of the instrumentation point.
 
 In practice, LTTng implements various optimizations for the Linux kernel
 and user space tracing domains (see the <<domain,{sect-domain}>> section
@@ -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