domain: add Python domain to list

[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 f96462294dc95b1b543d569e69254b6142c230f5..70ac4cdcce9bde0cad40d3ff9c995a0c3fa35884 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
@@ -44,7 +44,7 @@ Session daemons run on a per-user basis. Knowing this, multiple
 instances of `lttng-sessiond` may run simultaneously, each belonging
 to a different user and each operating independently of the others.
 Only `root`'s session daemon, however, may control LTTng kernel modules
-(i.e. the kernel tracer). With that in mind, if a user has no root
+(that is, the kernel tracer). With that in mind, if a user has no root
 access on the target system, he cannot trace the system's kernel, but
 should still be able to trace its own instrumented applications.
 
@@ -61,7 +61,7 @@ session daemon. `lttng-sessiond` may also be started manually:
 lttng-sessiond
 </pre>
 
-This will start the session daemon in foreground. Use
+This starts the session daemon in foreground. Use
 
 <pre class="term">
 lttng-sessiond --daemonize
@@ -75,8 +75,8 @@ To kill the current user's session daemon, `pkill` may be used:
 pkill lttng-sessiond
 </pre>
 
-The default `SIGTERM` signal will terminate it cleanly.
+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/v2.7" class="ext"><code>lttng-sessiond</code>'s
+man page</a> or by running `lttng-sessiond --help`.