Spotted http://docs.openvswitch.org/en/latest/howto/sflow/,
grepping the tree found another instance in ovn.
---
Documentation/howto/sflow.rst | 6 +++---
ovn/northd/ovn-northd.8.xml | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/howto/sflow.rst b/Documentation/howto/sflow.rst
index ae7737faf..c6ab0764c 100644
--- a/Documentation/howto/sflow.rst
+++ b/Documentation/howto/sflow.rst
@@ -21,9 +21,9 @@
Avoid deeper levels because they do not render well.
-================================
-Monitoring VM Trafic Using sFlow
-================================
+=================================
+Monitoring VM Traffic Using sFlow
+=================================
This document describes how to use Open vSwitch is to monitor traffic sent
between two VMs on the same host using an sFlow collector.
diff --git a/ovn/northd/ovn-northd.8.xml b/ovn/northd/ovn-northd.8.xml
index aab8f6974..e6417220f 100644
--- a/ovn/northd/ovn-northd.8.xml
+++ b/ovn/northd/ovn-northd.8.xml
@@ -341,7 +341,7 @@
</li>
<li>
- A priority-65535 flow that drops all trafic in the reply direction
+ A priority-65535 flow that drops all traffic in the reply direction
with <code>ct_label.blocked</code> set meaning that the connection
should no longer be allowed due to a policy change. Packets
in the request direction are skipped here to let a newly created
--
2.21.0
_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
