Fix: --clock-force-correlate to handle trace collections gathered from various nodes

[babeltrace.git] / doc / babeltrace.1

diff --git a/doc/babeltrace.1 b/doc/babeltrace.1
index 54ff70e7ec24fa33c37d80617551d88ac84aeb5a..db462f46d42a7073f9caa80eccf21add9c4b3e7c 100644 (file)
--- a/doc/babeltrace.1
+++ b/doc/babeltrace.1
@@ -50,8 +50,8 @@ Debug mode (or set BABELTRACE_DEBUG environment variable)
 Do not print time delta between consecutive events
 .TP
 .BR "-n, --names name1<,name2,...>"
-Print field names: (payload OR args OR arg), all, scope, header,
-(context OR ctx), (payload active by default).
+Print field names: (payload OR args OR arg), none, all, scope, header,
+(context OR ctx), (default: payload,context).
 .TP
 .BR "-f, --fields name1<,name2,...>"
 Print additional fields: all, trace, trace:domain, trace:procname,
@@ -92,12 +92,12 @@ Activate debug Babeltrace output.
 .SH "SEE ALSO"
 
 .PP
-babeltrace-log(1), lttng-tools(1), lttng-ust(3), lttng-sessiond(8)
+babeltrace-log(1), lttng(1), lttng-ust(3), lttng-sessiond(8)
 .PP
 .SH "BUGS"
 
 .PP
-No knows bugs at this point.
+No known bugs at this point.
 
 If you encounter any issues or usability problem, please report it on
 our mailing list <lttng-dev@lists.lttng.org> to help improve this