From b80ba3062f71ca7dd34abc956e5cfe9d84d90f35 Mon Sep 17 00:00:00 2001
From: Philippe Proulx <eeppeliteloop@gmail.com>
Date: Mon, 13 Oct 2014 22:04:45 -0400
Subject: [PATCH] Use long options in command line examples

Signed-off-by: Philippe Proulx <eeppeliteloop@gmail.com>
---
 contents/getting-started/viewing-and-analyzing.md             | 2 +-
 .../controlling-tracing/enabling-disabling-events.md          | 2 +-
 contents/using-lttng/controlling-tracing/lttng-live.md        | 4 ++--
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/contents/getting-started/viewing-and-analyzing.md b/contents/getting-started/viewing-and-analyzing.md
index 6181624..4b970cd 100644
--- a/contents/getting-started/viewing-and-analyzing.md
+++ b/contents/getting-started/viewing-and-analyzing.md
@@ -55,7 +55,7 @@ babeltrace ~/lttng-traces/my-kernel-session | grep sys_
 Counting events is also straightforward:
 
 <pre class="term">
-babeltrace ~/lttng-traces/my-kernel-session | grep sys_read | wc -l
+babeltrace ~/lttng-traces/my-kernel-session | grep sys_read | wc --lines
 </pre>
 
 The text output of `babeltrace` is useful for isolating events by simple
diff --git a/contents/using-lttng/controlling-tracing/enabling-disabling-events.md b/contents/using-lttng/controlling-tracing/enabling-disabling-events.md
index ac4d137..fd6a5cd 100644
--- a/contents/using-lttng/controlling-tracing/enabling-disabling-events.md
+++ b/contents/using-lttng/controlling-tracing/enabling-disabling-events.md
@@ -111,7 +111,7 @@ Disabling an event is simpler: you only need to provide the event
 name to the `disable-event` command:
 
 <pre class="term">
-lttng disable-event -u my_app:hello_you
+lttng disable-event --userspace my_app:hello_you
 </pre>
 
 This name has to match a name previously given to `enable-event` (it
diff --git a/contents/using-lttng/controlling-tracing/lttng-live.md b/contents/using-lttng/controlling-tracing/lttng-live.md
index 9d64620..26b11c1 100644
--- a/contents/using-lttng/controlling-tracing/lttng-live.md
+++ b/contents/using-lttng/controlling-tracing/lttng-live.md
@@ -69,12 +69,12 @@ list active tracing sessions by doing the following (assuming the relay
 daemon to connect to runs on the same host):
 
 <pre class="term">
-babeltrace -i lttng-live net://localhost
+babeltrace --input-format lttng-live net://localhost
 </pre>
 
 Then, choose a tracing session and start viewing events as they arrive
 using LTTng live, e.g.:
 
 <pre class="term">
-babeltrace -i lttng-live net://localhost/host/hostname/my-session
+babeltrace --input-format lttng-live net://localhost/host/hostname/my-session
 </pre>
-- 
2.34.1