event-rule: introduce event rule syscall

[lttng-tools.git] / doc / man / lttng-enable-channel.1.txt

diff --git a/doc/man/lttng-enable-channel.1.txt b/doc/man/lttng-enable-channel.1.txt
index 95e62e6f1ec069f0438033725433502ad173d2d9..7ddbe48b4416deb017e003aa9e7370ff62edf5f1 100644 (file)
--- a/doc/man/lttng-enable-channel.1.txt
+++ b/doc/man/lttng-enable-channel.1.txt
@@ -1,5 +1,6 @@
 lttng-enable-channel(1)
 =======================
+:revdate: 9 November 2018
 
 
 NAME
@@ -245,12 +246,12 @@ no space left in the last file, _trace file rotation_ happens: the first
 file is cleared and new sub-buffers containing events are written there.
 
 LTTng does not guarantee that you can view the trace of an active
-tracing session (before you run the man:lttng-stop(1) command), even
+tracing session before you run the man:lttng-stop(1) command, even
 with multiple trace files, because LTTng could overwrite them at any
 moment, or some of them could be incomplete. You can archive a
 tracing session's current trace chunk while the tracing session is
 active to obtain an unmanaged and self-contained LTTng trace: see
-man:lttng-rotate(1) and man:lttng-enable-rotation(1).
+the man:lttng-rotate(1) and man:lttng-enable-rotation(1) commands.
 
 
 include::common-cmd-options-head.txt[]