[ovs-dev] [PATCH] Documentation: Fix commands not being shown in code blocks

axel at tripier.fr axel at tripier.fr
Fri Apr 27 14:12:27 UTC 2018

Some commands are not shown in code blocks in the Advances Features
tutorial, they are shown as variable width text because of a missing ":"
to designate them as code blocks.

Signed-off-by: Axel Tripier <axel at tripier.fr>
  Documentation/tutorials/ovs-advanced.rst | 6 +++---
  1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/tutorials/ovs-advanced.rst 
index 676137f3c..c0784db04 100644
--- a/Documentation/tutorials/ovs-advanced.rst
+++ b/Documentation/tutorials/ovs-advanced.rst
@@ -726,7 +726,7 @@ which ought to show roughly the following, with 
extraneous details removed::

  The other way is to inject a packet to take advantage of the learning 
  For example, we can inject a packet on p2 whose destination is the MAC 
-that we just learned on p1:
+that we just learned on p1::

      $ ovs-appctl ofproto/trace br0 \
@@ -763,7 +763,7 @@ the learned port ``p1`` into register ``0``::

  If you read the commands above carefully, then you might have noticed 
that they
  simply have the Ethernet source and destination addresses exchanged.  
-means that if we now rerun the first ``ovs-appctl`` command above, 
+means that if we now rerun the first ``ovs-appctl`` command above, 

      $ ovs-appctl ofproto/trace br0 \
in_port=1,dl_vlan=20,dl_src=f0:00:00:00:00:01,dl_dst=90:00:00:00:00:01 \
@@ -926,7 +926,7 @@ Now, if we rerun our first command::

  ...we can see that the result is no longer a flood but to the specified 
-destination port ``p4``:
+destination port ``p4``::

      Datapath actions: pop_vlan,4


More information about the dev mailing list