X-Git-Url: http://git.lttng.org./?a=blobdiff_plain;f=contents%2Fusing-lttng%2Fcontrolling-tracing%2Fsaving-loading-tracing-session.md;h=02ff9b1d2723c22322c5fba425e3efbf67ee3a53;hb=b06ddade479078b5634f2465d4e4eaeef1865edc;hp=e6a67146e2950d2fa08ef22c49de709b85ef04d3;hpb=47bfcb757a0192864b56d12d775f65dc8b180aaf;p=lttng-docs.git

diff --git a/contents/using-lttng/controlling-tracing/saving-loading-tracing-session.md b/contents/using-lttng/controlling-tracing/saving-loading-tracing-session.md
index e6a6714..02ff9b1 100644
--- a/contents/using-lttng/controlling-tracing/saving-loading-tracing-session.md
+++ b/contents/using-lttng/controlling-tracing/saving-loading-tracing-session.md
@@ -1,11 +1,13 @@
 ---
 id: saving-loading-tracing-session
+since: 2.5
 ---
 
 Configuring a tracing session may be long: creating and enabling
 channels with specific parameters, enabling kernel and user space
-domain events with specific log levels and filters, adding context
-to some channels, etc. If you're going to use LTTng to solve real
+domain events with specific log levels and filters, and adding context
+to some channels are just a few of the many possible operations using
+the `lttng` command line tool. If you're going to use LTTng to solve real
 world problems, chances are you're going to have to record events using
 the same tracing session setup over and over, modifying a few variables
 each time in your instrumented program or environment. To avoid