1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/networking/openvswitch.txt b/Documentation/networking/openvswitch.txt
index b8a048b8df3a..8fa2dd1e792e 100644
--- a/Documentation/networking/openvswitch.txt
+++ b/Documentation/networking/openvswitch.txt
@@ -118,7 +118,7 @@ essentially like this, ignoring metadata:
 Naively, to add VLAN support, it makes sense to add a new "vlan" flow
 key attribute to contain the VLAN tag, then continue to decode the
 encapsulated headers beyond the VLAN tag using the existing field
-definitions.  With this change, an TCP packet in VLAN 10 would have a
+definitions.  With this change, a TCP packet in VLAN 10 would have a
 flow key much like this:
    eth(...), vlan(vid=10, pcp=0), eth_type(0x0800), ip(proto=6, ...), tcp(...)

diff --git a/Documentation/networking/openvswitch.txt b/Documentation/networking/openvswitch.txt index b8a048b8df3a..8fa2dd1e792e 100644 --- a/Documentation/networking/openvswitch.txt +++ b/Documentation/networking/openvswitch.txt
@@ -118,7 +118,7 @@ essentially like this, ignoring metadata:
118	Naively, to add VLAN support, it makes sense to add a new "vlan" flow	118	Naively, to add VLAN support, it makes sense to add a new "vlan" flow
119	key attribute to contain the VLAN tag, then continue to decode the	119	key attribute to contain the VLAN tag, then continue to decode the
120	encapsulated headers beyond the VLAN tag using the existing field	120	encapsulated headers beyond the VLAN tag using the existing field
121	definitions. With this change, an TCP packet in VLAN 10 would have a	121	definitions. With this change, a TCP packet in VLAN 10 would have a
122	flow key much like this:	122	flow key much like this:
123		123
124	eth(...), vlan(vid=10, pcp=0), eth_type(0x0800), ip(proto=6, ...), tcp(...)	124	eth(...), vlan(vid=10, pcp=0), eth_type(0x0800), ip(proto=6, ...), tcp(...)