tracing-your-own-user-application: lttng view before destroy

Signed-off-by: Philippe Proulx <eeppeliteloop@gmail.com>

diff --git a/contents/getting-started/tracing-your-own-user-application.md b/contents/getting-started/tracing-your-own-user-application.md
index 064e3c263c764955866a551db64382d8891dd1c9..f899e7da9e54ce459b016b8f1f16ec43e0440e66 100644 (file)
--- a/contents/getting-started/tracing-your-own-user-application.md
+++ b/contents/getting-started/tracing-your-own-user-application.md
@@ -184,11 +184,10 @@ lttng start
 Go back to the running `hello` application and press Enter. All `tracepoint()`
 calls will be executed and the program will finally exit.
 
-Stop tracing and destroy the tracing session:
+Stop tracing:
 
 <pre class="term">
 lttng stop
-lttng destroy my-userspace-session
 </pre>
 
 Done! You may use `lttng view` to list the recorded events. This command
@@ -211,5 +210,13 @@ should output something like:
 [18:10:27.684357978] (+0.000014460) hostname hello_world:my_first_tracepoint: { cpu_id = 0 }, { my_string_field = "x^2", my_integer_field = 16 }
 ~~~
 
+When you're done, you may destroy the tracing session, which does _not_
+destroy the generated trace files, leaving them available for further
+analysis:
+
+<pre class="term">
+lttng destroy my-userspace-session
+</pre>
+
 The next section presents other alternatives to view and analyze your
 LTTng traces.