Remove "etc."

[lttng-docs.git] / contents / using-lttng / controlling-tracing / saving-loading-tracing-session.md

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 5f8e928e68f2a69d2c5b1dce42214abdd37e0812..08b2f3f2a32a46f3fcd396548320ea36e68534e9 100644 (file)
--- a/contents/using-lttng/controlling-tracing/saving-loading-tracing-session.md
+++ b/contents/using-lttng/controlling-tracing/saving-loading-tracing-session.md
@@ -4,8 +4,9 @@ id: saving-loading-tracing-session
 
 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
@@ -43,5 +44,5 @@ or, if you used a custom path:
 lttng load --input-path /path/to/my-session.lttng
 </pre>
 
-Your saved tracing session will be restored as if you just configured
+Your saved tracing session is restored as if you just configured
 it manually.