X-Git-Url: http://git.lttng.org./?a=blobdiff_plain;f=contents%2Funderstanding-lttng%2Fcore-concepts%2Ftracing-session.md;h=96c0071b75d7bda5685c3684eb3b7d4b457ca608;hb=85ccb28b9a18a29b9515e2d445185f8d0241c5f2;hp=3b0e40a52711b19696401ad4f26f9cb2a64234be;hpb=5e0cbfb01373c18e521217342fd8a9159cc186b1;p=lttng-docs.git

diff --git a/contents/understanding-lttng/core-concepts/tracing-session.md b/contents/understanding-lttng/core-concepts/tracing-session.md
index 3b0e40a..96c0071 100644
--- a/contents/understanding-lttng/core-concepts/tracing-session.md
+++ b/contents/understanding-lttng/core-concepts/tracing-session.md
@@ -23,25 +23,34 @@ which are described in the following sections):
     * a name
     * the channel state (enabled or disabled)
     * its parameters (event loss mode, sub-buffers size and count,
-      timer periods, output type, trace files size and count, etc.)
+      timer periods, output type, trace files size and count, and the rest)
     * a list of added context information
     * a list of [events](#doc-event)
   * for each event:
     * its state (enabled or disabled)
     * a list of instrumentation points (tracepoints, system calls,
-      dynamic probes, etc.)
+      dynamic probes, other types of probes)
     * associated log levels
     * a filter expression
 
 All this information is completely isolated between tracing sessions.
+As you can see in the list above, even the tracing state
+is a per-tracing session attribute, so that you may trace your target
+system/application in a given tracing session with a specific
+configuration while another one stays inactive.
+
+<div class="img img-100">
+<img src="/images/docs26/concepts.png" alt="LTTng concepts">
+</div>
 
 Conceptually, a tracing session is a per-user object; the
 [Plumbing](#doc-plumbing) section shows how this is actually
 implemented. Any user may create as many concurrent tracing sessions
-as desired. As you can see in the list above, even the tracing state
-is a per-tracing session attribute, so that you may trace your target
-system/application in a given tracing session with a specific
-configuration while another one stays inactive.
+as desired.
+
+<div class="img img-100">
+<img src="/images/docs26/many-sessions.png" alt="Tracing sessions per user">
+</div>
 
 The trace data generated in a tracing session may be either saved
 to disk, sent over the network or not saved at all (in which case