lttng-concepts(7): remove reference to the section it's in

[lttng-tools.git] / doc / man / lttng-concepts.7.txt

diff --git a/doc/man/lttng-concepts.7.txt b/doc/man/lttng-concepts.7.txt
index e88f529f039561f70c88647824d28e1b3231d589..893f27bcf8aa60b4087f7dce65ef4c5486faeeed 100644 (file)
--- 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
 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
 
 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
 |===
 
 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
 
 You can create channels (see the <<channel,{sect-channel}>> section
 below) in the Linux kernel and user space tracing domains. The other


@@ -895,7 +895,6 @@ man:lttng-enable-channel(1) command.
 
 Monitor timer::
     When this timer expires, the consumer daemon samples some channel
 
 Monitor timer::
     When this timer expires, the consumer daemon samples some channel

-    (see the <<channel,{sect-channel}>> section above)

     statistics to evaluate the following trigger conditions:
 +
 --
     statistics to evaluate the following trigger conditions:
 +
 --


@@ -975,7 +974,7 @@ redundant when both are enabled:
 [role="term"]
 ----
 $ lttng enable-event --userspace hello:world
 [role="term"]
 ----
 $ lttng enable-event --userspace hello:world

-$ lttng enable-event --userspace hello:world --loglevel=TRACE_INFO
+$ lttng enable-event --userspace hello:world --loglevel=INFO

 ----
 
 List the recording event rules of a specific tracing session
 ----
 
 List the recording event rules of a specific tracing session