-You can use `lttng rotate` either at any time when the tracing session
-is active (see man:lttng-start(1)), or a single time once the tracing
-session becomes inactive (see man:lttng-stop(1)).
-
-By default, the `lttng rotate` command ensures that the rotation is done
-before printing the archived trace chunk's path and returning to the
-prompt. The printed path is absolute when the tracing session was
-created in normal mode and relative to the relay daemon's output
-directory (see the nloption:--output option in man:lttng-relayd(8)) when
-it was created in network streaming mode (see man:lttng-create(1)).
-
-With the option:--no-wait option, the command finishes immediately,
-hence a rotation might not be completed when the command is done. In
-this case, there is no easy way to know when the current trace chunk is
-archived, and the command does not print the archived trace chunk's
-path.
-
-Because a rotation causes the tracing session's current sub-buffers to
-be flushed, archived trace chunks are never redundant, that is, they do
-not overlap over time like snapshots can (see man:lttng-snapshot(1)).
-Also, a rotation does not directly cause discarded event records or
-packets.
+You can use `lttng rotate`:
+
+* At any time when the tracing session is active (see
+ man:lttng-start(1)).
+* A single time once the tracing session becomes inactive
+ (see man:lttng-stop(1)).
+
+By default, the `lttng rotate` command ensures that LTTng finished
+performing the tracing session rotation before it prints the archived
+trace chunk's path and exits. The printed path is absolute when the
+tracing session was created in normal mode and relative to the relay
+daemon's output directory (see the nloption:--output option in
+man:lttng-relayd(8)) when it was created in network streaming mode (see
+man:lttng-create(1)).
+
+With the option:--no-wait option, the command finishes immediately, so
+that LTTng might not have completed the rotation when the command exits.
+In this case, there is no easy way to know when the current trace chunk
+becomes archived, and the command does not print the archived trace
+chunk's path.
+
+Because when LTTng performs a tracing session rotation, it flushes the
+tracing session's current sub-buffers, archived trace chunks are never
+redundant, that is, they do not overlap over time like snapshots can
+(see man:lttng-snapshot(1)). Also, a rotation does not directly cause
+discarded event records or packets.