Merge branch 'fix_live' of https://github.com/PSRCode/lttng-docs

diff --combined 2.8/lttng-docs-2.8.txt
index 854921596883eb94f4124cef3ded00090b57e9d9,e38cafe2c6aa5d4534058788303269b4c659ec8b..35167a936675ad21811e55559bae9eda4a95125c
--- 1/2.8/lttng-docs-2.8.txt
--- 2/2.8/lttng-docs-2.8.txt
+++ b/2.8/lttng-docs-2.8.txt
@@@ -1,7 -1,7 +1,7 @@@
  The LTTng Documentation
  =======================
  Philippe Proulx <pproulx@efficios.com>
 -v2.8, 8 December 2016
 +v2.8, 20 February 2017
  
  
  include::../common/copyright.txt[]
@@@ -888,8 -888,8 +888,8 @@@ sudo lttng create my-kernel-session --o
  --
  [role="term"]
  ----
 -lttng list --kernel
 -lttng list --kernel --syscall
 +sudo lttng list --kernel
 +sudo lttng list --kernel --syscall
  ----
  --
  
@@@ -5723,7 -5723,7 +5723,7 @@@ To output LTTng traces to a non-defaul
  --
  [role="term"]
  ----
- lttng create --output=/tmp/some-directory my-session
+ lttng create my-session --output=/tmp/some-directory
  ----
  --
  
@@@ -6617,7 -6617,7 +6617,7 @@@ remote system. See man:lttng-create(1) 
  
  . On the target system, use the man:lttng(1) command-line tool as usual.
    When tracing is active, the target's consumer daemon sends sub-buffers
 -  to the relay daemon running on the remote system intead of flushing
 +  to the relay daemon running on the remote system instead of flushing
    them to the local file system. The relay daemon writes the received
    packets to the local file system.
  
@@@ -6654,7 -6654,7 +6654,7 @@@ To use LTTng live
  --
  [role="term"]
  ----
- lttng create --live my-session
+ lttng create my-session --live
  ----
  --
  +
@@@ -6721,7 -6721,7 +6721,7 @@@ To take a snapshot
  --
  [role="term"]
  ----
- lttng create --snapshot my-session
+ lttng create my-session --snapshot
  ----
  --
  +
@@@ -6864,7 -6864,7 +6864,7 @@@ trace data after a system crash
  --
  [role="term"]
  ----
- lttng create --shm-path=/path/to/shm
+ lttng create my-session --shm-path=/path/to/shm
  ----
  --
  

diff --combined 2.9/lttng-docs-2.9.txt
index 7086b0177c05f123e5cbae73cc45265e881ce4d5,533bae327e981b6515379acb7deefa03b3e8d412..97a9b5d718ec9bba4a7c8ba71bac28d9f1c2a0ca
--- 1/2.9/lttng-docs-2.9.txt
--- 2/2.9/lttng-docs-2.9.txt
+++ b/2.9/lttng-docs-2.9.txt
@@@ -1,7 -1,7 +1,7 @@@
  The LTTng Documentation
  =======================
  Philippe Proulx <pproulx@efficios.com>
 -v2.9, 8 December 2016
 +v2.9, 20 February 2017
  
  
  include::../common/copyright.txt[]
@@@ -641,8 -641,8 +641,8 @@@ sudo lttng create my-kernel-session --o
  --
  [role="term"]
  ----
 -lttng list --kernel
 -lttng list --kernel --syscall
 +sudo lttng list --kernel
 +sudo lttng list --kernel --syscall
  ----
  --
  
@@@ -5494,7 -5494,7 +5494,7 @@@ To output LTTng traces to a non-defaul
  --
  [role="term"]
  ----
- lttng create --output=/tmp/some-directory my-session
+ lttng create my-session --output=/tmp/some-directory
  ----
  --
  
@@@ -6402,7 -6402,7 +6402,7 @@@ remote system. See man:lttng-create(1) 
  
  . On the target system, use the man:lttng(1) command-line tool as usual.
    When tracing is active, the target's consumer daemon sends sub-buffers
 -  to the relay daemon running on the remote system intead of flushing
 +  to the relay daemon running on the remote system instead of flushing
    them to the local file system. The relay daemon writes the received
    packets to the local file system.
  
@@@ -6439,7 -6439,7 +6439,7 @@@ To use LTTng live
  --
  [role="term"]
  ----
- lttng create --live my-session
+ lttng create my-session --live
  ----
  --
  +
@@@ -6506,7 -6506,7 +6506,7 @@@ To take a snapshot
  --
  [role="term"]
  ----
- lttng create --snapshot my-session
+ lttng create my-session --snapshot
  ----
  --
  +
@@@ -6709,7 -6709,7 +6709,7 @@@ trace data after a system crash
  --
  [role="term"]
  ----
- lttng create --shm-path=/path/to/shm
+ lttng create my-session --shm-path=/path/to/shm
  ----
  --