X-Git-Url: http://git.lttng.org./?a=blobdiff_plain;f=contents%2Funderstanding-lttng%2Fplumbing%2Flttng-sessiond.md;h=6e298e47e6e178e5f426249e44b4063cd4100264;hb=4d46e8c0be2957758addfa997ba7cece5a5aada6;hp=a1bb7f2ed8f64396285977932945221a3875937a;hpb=47bfcb757a0192864b56d12d775f65dc8b180aaf;p=lttng-docs.git

diff --git a/contents/understanding-lttng/plumbing/lttng-sessiond.md b/contents/understanding-lttng/plumbing/lttng-sessiond.md
index a1bb7f2..6e298e4 100644
--- a/contents/understanding-lttng/plumbing/lttng-sessiond.md
+++ b/contents/understanding-lttng/plumbing/lttng-sessiond.md
@@ -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.