building-from-source: minor fixes

[lttng-docs.git] / contents / understanding-lttng / plumbing / lttng-sessiond.md

diff --git a/contents/understanding-lttng/plumbing/lttng-sessiond.md b/contents/understanding-lttng/plumbing/lttng-sessiond.md
index 6e298e47e6e178e5f426249e44b4063cd4100264..4469902f89f7363b3bd6ec2cd8f4c23faabf9a43 100644 (file)
--- a/contents/understanding-lttng/plumbing/lttng-sessiond.md
+++ b/contents/understanding-lttng/plumbing/lttng-sessiond.md
@@ -7,8 +7,8 @@ by its command name, `lttng-sessiond`.
 
 The session daemon is responsible for managing tracing sessions and
 what they logically contain (channel properties, enabled/disabled
-events, etc.). By communicating locally with instrumented applications
-(using LTTng-UST) and with the LTTng Linux kernel modules
+events, and the rest). By communicating locally with instrumented
+applications (using LTTng-UST) and with the LTTng Linux kernel modules
 (LTTng-modules), it oversees all tracing activities.
 
 One of the many things that `lttng-sessiond` does is to keep
@@ -24,7 +24,7 @@ and user space tracers, the session daemon can send channel information
 so that they are initialized, enable/disable specific probes based on
 enabled/disabled events by the user, send event filters information to
 LTTng tracers so that filtering actually happens at the tracer site,
-start/stop tracing a specific application or the Linux kernel, etc.
+start/stop tracing a specific application or the Linux kernel, and more.
 
 The session daemon is not useful without some user controlling it,
 because it's only a sophisticated control interchange and thus
@@ -78,5 +78,5 @@ pkill lttng-sessiond
 The default `SIGTERM` signal terminates it cleanly.
 
 Several other options are available and described in
-<a href="/man/8/lttng-sessiond" class="ext"><code>lttng-sessiond</code>'s manpage</a>
-or by running `lttng-sessiond --help`.
+<a href="/man/8/lttng-sessiond" class="ext"><code>lttng-sessiond</code>'s
+man page</a> or by running `lttng-sessiond --help`.