Add Nicira vendor extension action NXAST_DEC_TTL_CNT_IDS.

[openvswitch] / ofproto / ofproto-unixctl.man

diff --git a/ofproto/ofproto-unixctl.man b/ofproto/ofproto-unixctl.man
index 9d0c8e32783e0ee1dccd7ef7197d7abb56683e55..3e36fe6362db14fa90fad4b6bc6feba08567ee5f 100644 (file)
--- a/ofproto/ofproto-unixctl.man
+++ b/ofproto/ofproto-unixctl.man
@@ -31,13 +31,13 @@ utilities provide easier ways.
 .IP
 The second form specifies the packet's contents implicitly:
 .RS
 .IP
 The second form specifies the packet's contents implicitly:
 .RS

-.IP "\flow\fR"
+.IP "\fIflow\fR"

 A flow in one of two forms: either the form printed by
 \fBovs\-dpctl\fR(8)'s \fBdump\-flows\fR command, or in a format
 A flow in one of two forms: either the form printed by
 \fBovs\-dpctl\fR(8)'s \fBdump\-flows\fR command, or in a format

-similar to that accepted by \Bovs\-ofctl\fR(8)'s \fBadd\-flow\fR
+similar to that accepted by \fBovs\-ofctl\fR(8)'s \fBadd\-flow\fR

 command.  This is not an OpenFlow flow: besides other differences, it
 never contains wildcards.  \fB\*(PN\fR generates an arbitrary packet
 command.  This is not an OpenFlow flow: besides other differences, it
 never contains wildcards.  \fB\*(PN\fR generates an arbitrary packet

-that has the specified \flow\fR.
+that has the specified \fIflow\fR.

 .RE
 .IP
 \fB\*(PN\fR will respond with extensive information on how the packet
 .RE
 .IP
 \fB\*(PN\fR will respond with extensive information on how the packet


@@ -51,16 +51,16 @@ Traces the path of a packet in an imaginary flow through
 .IP "\fIswitch\fR"
 The switch on which the packet arrived (one of those listed by
 \fBofproto/list\fR).
 .IP "\fIswitch\fR"
 The switch on which the packet arrived (one of those listed by
 \fBofproto/list\fR).

-.IP "\flow\fR"
+.IP "\fIflow\fR"

 A flow in one of two forms: either the form printed by
 \fBovs\-dpctl\fR(8)'s \fBdump\-flows\fR command, or in a format
 A flow in one of two forms: either the form printed by
 \fBovs\-dpctl\fR(8)'s \fBdump\-flows\fR command, or in a format

-similar to that accepted by \Bovs\-ofctl\fR(8)'s \fBadd\-flow\fR
+similar to that accepted by \fBovs\-ofctl\fR(8)'s \fBadd\-flow\fR

 command.  This is not an OpenFlow flow: besides other differences, it
 never contains wildcards.
 .RE
 .IP
 \fB\*(PN\fR will respond with extensive information on how a packet
 command.  This is not an OpenFlow flow: besides other differences, it
 never contains wildcards.
 .RE
 .IP
 \fB\*(PN\fR will respond with extensive information on how a packet

-in \flow\fR would be handled if it were received by
+in \fIflow\fR would be handled if it were received by

 \fIswitch\fR.  No packet will actually be sent.  Some side effects may
 occur, but MAC learning in particular will not.
 .IP
 \fIswitch\fR.  No packet will actually be sent.  Some side effects may
 occur, but MAC learning in particular will not.
 .IP