X-Git-Url: http://git.lttng.org./?a=blobdiff_plain;f=contents%2Fusing-lttng%2Fcontrolling-tracing%2Flttng-live.md;h=ef6c9affa2dc403a75e56045bf555a2181b19860;hb=3b5b45ec9eeae44744acb849c1a04eddd9d971c4;hp=1f932f58ba2b4f622d7cf6fa8007fd6fad2730d4;hpb=4280f59215672366f9c47f76c2a2f6dee9757ff7;p=lttng-docs.git

diff --git a/contents/using-lttng/controlling-tracing/lttng-live.md b/contents/using-lttng/controlling-tracing/lttng-live.md
index 1f932f5..ef6c9af 100644
--- a/contents/using-lttng/controlling-tracing/lttng-live.md
+++ b/contents/using-lttng/controlling-tracing/lttng-live.md
@@ -14,9 +14,8 @@ _LTTng live_.
 
 LTTng live is implemented, in LTTng, solely on the relay daemon side.
 As trace data is sent over the network to a relay daemon by a (possibly
-remote) consumer daemon, a _tee_ may be created: trace data will be
-recorded to trace files _as well as_ being transmitted to a
-connected live viewer:
+remote) consumer daemon, a _tee_ is created: trace data is recorded to
+trace files _as well as_ being transmitted to a connected live viewer:
 
 <div class="img img-90">
     <object data="/images/docs26/lttng-live-relayd.svg" type="image/svg+xml">
@@ -31,18 +30,18 @@ mode on the target system:
 lttng create --live
 </pre>
 
-An optional parameter may be passed to `--live` to set the interval
-of time (in microseconds) between flushes to the network
-(1&nbsp;second is the default):
+An optional parameter may be passed to `--live` to set the period
+(in microseconds) between flushes to the network
+(1&nbsp;second is the default). With:
 
 <pre class="term">
 lttng create --live 100000
 </pre>
 
-will flush every 100&nbsp;ms.
+the daemons flush their data every 100&nbsp;ms.
 
 If no network output is specified to the `create` command, a local
-relay daemon will be spawned. In this very common case, viewing a live
+relay daemon is spawned. In this very common case, viewing a live
 trace is easy: enable events and start tracing as usual, then use
 `lttng view` to start the default live viewer:
 
@@ -50,7 +49,7 @@ trace is easy: enable events and start tracing as usual, then use
 lttng view
 </pre>
 
-The correct arguments will be passed to the live viewer so that it
+The correct arguments are passed to the live viewer so that it
 may connect to the local relay daemon and start reading live events.
 
 You may also wish to use a live viewer not running on the target
@@ -73,7 +72,7 @@ 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.:
+using LTTng live:
 
 <pre class="term">
 babeltrace --input-format lttng-live net://localhost/host/hostname/my-session