opensuse: new section

[lttng-docs.git] / contents / getting-started / tracing-the-linux-kernel.md

diff --git a/contents/getting-started/tracing-the-linux-kernel.md b/contents/getting-started/tracing-the-linux-kernel.md
index 70d0f4bc54eac48dccae7a71205f70dc042fe502..659aa477f311a8e6cb93da8b66034f4397379a64 100644 (file)
--- a/contents/getting-started/tracing-the-linux-kernel.md
+++ b/contents/getting-started/tracing-the-linux-kernel.md
@@ -7,7 +7,7 @@ Make sure LTTng-tools and LTTng-modules packages
 
 Since you're about to trace the Linux kernel itself, let's look at the
 available kernel events using the `lttng` tool, which has a
-Git like command line structure:
+Git-like command line structure:
 
 <pre class="term">
 lttng list --kernel
@@ -16,29 +16,26 @@ 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 part of the
-    <a href="/docs/#doc-lttng-sessiond" class="int"><code>tracing</code>
+    the previous and following commands if your user is a member of the
+    <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` will be 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
-that trace files will grow rapidly when doing this):
+Or you might want to simply enable all available kernel events (beware
+that trace files grow rapidly when doing this):
 
 <pre class="term">
 sudo lttng enable-event --kernel --all
@@ -62,7 +59,7 @@ sudo lttng destroy
 </pre>
 
 Although `destroy` looks scary here, it doesn't actually destroy the
-outputted traces: 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)