summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJakub Sitnicki <jkbs@redhat.com>2017-09-06 15:50:55 +0200
committerRussell Bryant <russell@ovn.org>2017-09-06 17:19:05 -0400
commit1bced3944b70ffd342323a8e119ae079f010eb70 (patch)
treeb1b7ec597a0c988872181bd822a705ba78a211da
parentdb5d0555ed7947c738134d8c3a333b989b9fdd6d (diff)
downloadopenvswitch-1bced3944b70ffd342323a8e119ae079f010eb70.tar.gz
doc: Fix typo in ovn-sandbox tutorial
ovn-trace example refers to a non-existent output port. Correct it. Fixes: 46a2dc58781a ("Document OVN support in ovs-sandbox.") Signed-off-by: Jakub Sitnicki <jkbs@redhat.com> Acked-By: Mark Michelson <mmichels@redhat.com> Signed-off-by: Russell Bryant <russell@ovn.org>
-rw-r--r--Documentation/tutorials/ovn-sandbox.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/tutorials/ovn-sandbox.rst b/Documentation/tutorials/ovn-sandbox.rst
index d47fcf529..d1e749f31 100644
--- a/Documentation/tutorials/ovn-sandbox.rst
+++ b/Documentation/tutorials/ovn-sandbox.rst
@@ -136,7 +136,7 @@ Using ovn-trace
Once you have configured resources in OVN, try using ``ovn-trace`` to see
how OVN would process a sample packet through its logical pipeline.
-For example, we can trace an IP packet from ``sw0-port1`` to ``sw0-port2``.
+For example, we can trace an IP packet from ``sw0-port1`` to ``sw1-port1``.
The ``--minimal`` output shows each visible action performed on the packet,
which includes: