controlling-tracing: minor fixes

Signed-off-by: Philippe Proulx <eeppeliteloop@gmail.com>

diff --git a/contents/using-lttng/controlling-tracing/intro.md b/contents/using-lttng/controlling-tracing/intro.md
index a8f4d715b248199d48dabb9623712fdbef4db30a..7d42c528f4c1c6e27e2942701282e50558ebda79 100644 (file)
--- a/contents/using-lttng/controlling-tracing/intro.md
+++ b/contents/using-lttng/controlling-tracing/intro.md
@@ -5,16 +5,17 @@ id: controlling-tracing
 Once you're in possession of a software that is properly
 [instrumented](#doc-instrumenting) for LTTng tracing, be it thanks to
 the built-in LTTng probes for the Linux kernel, a custom user
-application or a custom Linux kernel, all that is left is actually
-tracing it. As a user, you control LTTng tracing using a single command
-line interface: the `lttng` tool. This tool uses `liblttng-ctl` behind
-the scene to connect to and communicate with session daemons. LTTng
-session daemons may either be started manually (`lttng-sessiond`) or
-automatically by the `lttng` command when needed. Trace data may
-be forwarded to the network and used elsewhere using an LTTng relay
-daemon (`lttng-relayd`).
+application, or a custom Linux kernel, all that is left is actually
+tracing it.
 
-The man pages of `lttng`, `lttng-sessiond` and `lttng-relayd` are pretty
+You control LTTng tracing using a single command
+line tool: `lttng`. LTTng [session daemons](#doc-lttng-sessiond) may
+either be started manually (`lttng-sessiond`) or automatically by the
+`lttng` command when a sessions is created. Trace data may be forwarded
+to the network and used elsewhere using an LTTng
+[relay daemon](#doc-lttng-relayd) (`lttng-relayd`).
+
+The man pages of `lttng`, `lttng-sessiond`, and `lttng-relayd` are pretty
 complete, thus this section is not an online copy of the latter (we
 leave this contents for the
 [Online LTTng man pages](#doc-online-lttng-manpages) section).