diff mbox series

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

Message ID 775d84eaa8f6d8f6a457518eb6a682d6@tripier.fr
State Accepted
Headers show
Series [ovs-dev] Doc: Fix commands not being shown in code blocks | expand

Commit Message

axel@tripier.fr April 27, 2018, 2:59 p.m. UTC 
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@tripier.fr>
---
 Documentation/tutorials/ovs-advanced.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

Comments

Ben Pfaff May 9, 2018, 9:34 p.m. UTC | #1 
On Fri, Apr 27, 2018 at 04:59:50PM +0200, axel@tripier.fr wrote:
> 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@tripier.fr>

Thanks, I applied this to master and branch-2.9.
diff mbox series

Patch

diff --git a/Documentation/tutorials/ovs-advanced.rst b/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 entry.
 For example, we can inject a packet on p2 whose destination is the MAC address
-that we just learned on p1:
+that we just learned on p1::
 
     $ ovs-appctl ofproto/trace br0 \
         in_port=2,dl_src=90:00:00:00:00:01,dl_dst=f0:00:00:00:00:01 -generate
@@ -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.  That
-means that if we now rerun the first ``ovs-appctl`` command above, e.g.:
+means that if we now rerun the first ``ovs-appctl`` command above, e.g.::
 
     $ 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::
         -generate
 
 ...we can see that the result is no longer a flood but to the specified learned
-destination port ``p4``:
+destination port ``p4``::
 
     Datapath actions: pop_vlan,4