From 08060fc12ce22fb45f524be657d2c408162aafdf Mon Sep 17 00:00:00 2001
From: =?utf8?q?S=C3=A9bastien=20Boisvert?= <boisvert@anl.gov>
Date: Sun, 19 Oct 2014 13:22:01 -0500
Subject: [PATCH] tracing-the-linux-kernel: minor fixes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf8
Content-Transfer-Encoding: 8bit

Signed-off-by: Sébastien Boisvert <boisvert@anl.gov>
---
 contents/getting-started/tracing-the-linux-kernel.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/contents/getting-started/tracing-the-linux-kernel.md b/contents/getting-started/tracing-the-linux-kernel.md
index 70d0f4b..2a5eb74 100644
--- 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
@@ -22,7 +22,7 @@ sudo lttng create my-session
 <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
+    the previous and following commands if your user is a member of the
     <a href="/docs/#doc-lttng-sessiond" class="int"><code>tracing</code>
     group</a>.
 </p>
@@ -62,7 +62,7 @@ sudo lttng destroy
 </pre>
 
 Although `destroy` looks scary here, it doesn't actually destroy the
-outputted traces: it only destroys the tracing session.
+outputted 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