manpages: Highlight --ct-next option.

This makes it look like other options.

Acked-by: Yi-Hung Wei <yihung.wei@gmail.com>
Signed-off-by: Ilya Maximets <i.maximets@samsung.com>
Signed-off-by: Ben Pfaff <blp@ovn.org>

diff --git a/ofproto/ofproto-unixctl.man b/ofproto/ofproto-unixctl.man
index 2db4fe6330f9846ccd89afbb31588fa734e62552..925752343e87831c2f7124277983690a1d78fa8b 100644 (file)
--- a/ofproto/ofproto-unixctl.man
+++ b/ofproto/ofproto-unixctl.man
@@ -70,7 +70,7 @@ OpenFlow version.  One exception is that, when \fIactions\fR includes
 an action that only OpenFlow 1.1 and later supports (such as
 \fBpush_vlan\fR), \fB\-\-consistent\fR is automatically enabled.
 .
-.IP "--ct-next \fIflags\fR"
+.IP "\fB\-\-ct-next\fR \fIflags\fR"
 When the traced flow triggers conntrack actions, \fBofproto/trace\fR
 will automatically trace the forked packet processing pipeline with
 user specified ct_state.  This option sets the ct_state flags that the
@@ -107,8 +107,9 @@ changed.
 .RE
 .
 .IP
-When --ct-next is unspecified, or when there are fewer --ct-next options than
-ct actions, the \fIflags\fR default to trk,new.
+When \fB\-\-ct-next\fR is unspecified, or when there are fewer
+\fB\-\-ct-next\fR options than ct \fIactions\fR, the \fIflags\fR default to
+\fBtrk,new\fR.
 .
 .RE
 .