From a5f17bf9c8a06716db8b4aab09066b40cdd5f7dd Mon Sep 17 00:00:00 2001
From: Philippe Proulx <eeppeliteloop@gmail.com>
Date: Fri, 4 Sep 2015 00:13:01 -0400
Subject: [PATCH] tracing-the-linux-kernel: minor fixes

Signed-off-by: Philippe Proulx <eeppeliteloop@gmail.com>
---
 contents/getting-started/tracing-the-linux-kernel.md | 11 ++++-------
 1 file changed, 4 insertions(+), 7 deletions(-)

diff --git a/contents/getting-started/tracing-the-linux-kernel.md b/contents/getting-started/tracing-the-linux-kernel.md
index c7522e2..659aa47 100644
--- a/contents/getting-started/tracing-the-linux-kernel.md
+++ b/contents/getting-started/tracing-the-linux-kernel.md
@@ -16,28 +16,25 @@ lttng list --kernel
 Before tracing, you need to create a session:
 
 <pre class="term">
-sudo lttng create my-session
+sudo lttng create
 </pre>
 
 <div class="tip">
 <p>
     <span class="t">Tip:</span>You can avoid using <code>sudo</code> in
     the previous and following commands if your user is a member of the
-    <a href="/docs/#doc-lttng-sessiond" class="int"><code>tracing</code>
+    <a href="#doc-lttng-sessiond" class="int"><code>tracing</code>
     group</a>.
 </p>
 </div>
 
-`my-session` is the tracing session name and could be anything you
-like. `auto` is used if omitted.
-
 Let's now enable some events for this session:
 
 <pre class="term">
 sudo lttng enable-event --kernel sched_switch,sched_process_fork
 </pre>
 
-or you might want to simply enable all available kernel events (beware
+Or you might want to simply enable all available kernel events (beware
 that trace files grow rapidly when doing this):
 
 <pre class="term">
@@ -62,7 +59,7 @@ sudo lttng destroy
 </pre>
 
 Although `destroy` looks scary here, it doesn't actually destroy the
-outputted trace files: it only destroys the tracing session.
+written trace files: it only destroys the tracing session.
 
 What's next? Have a look at
 [Viewing and analyzing your traces](#doc-viewing-and-analyzing-your-traces)
-- 
2.34.1