Looks good, thanks. Ethan
On Mon, May 14, 2012 at 11:18 AM, Ben Pfaff <b...@nicira.com> wrote: > Signed-off-by: Ben Pfaff <b...@nicira.com> > --- > ofproto/ofproto-unixctl.man | 8 ++++---- > 1 files changed, 4 insertions(+), 4 deletions(-) > > diff --git a/ofproto/ofproto-unixctl.man b/ofproto/ofproto-unixctl.man > index 9d0c8e3..c66ea50 100644 > --- 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 "\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 > similar to that accepted by \Bovs\-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 > -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 > @@ -51,7 +51,7 @@ 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 "\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 > similar to that accepted by \Bovs\-ofctl\fR(8)'s \fBadd\-flow\fR > @@ -60,7 +60,7 @@ 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 > -- > 1.7.2.5 > > _______________________________________________ > dev mailing list > dev@openvswitch.org > http://openvswitch.org/mailman/listinfo/dev _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
