X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=tutorial%2FTutorial;fp=tutorial%2FTutorial;h=c537badb43e89b1c734ebf2d57813aae2dfa47f3;hb=4ff8998c5cbe5abcb3490c2d5b95a2a1e6d47104;hp=b8dfc5488e841a56c6f6c360dce82223e7ebbf52;hpb=29089a540cfa30a834e3ee19a8b4c52ff2e331b2;p=sliver-openvswitch.git

diff --git a/tutorial/Tutorial b/tutorial/Tutorial
index b8dfc5488..c537badb4 100644
--- a/tutorial/Tutorial
+++ b/tutorial/Tutorial
@@ -277,7 +277,7 @@ one way or another, perhaps with common network testing tools like
 difficult with our simulated switch, since it's not visible to the
 operating system.
 
-Bur our simulated switch has a few specialized testing tools.  The
+But our simulated switch has a few specialized testing tools.  The
 most powerful of these tools is "ofproto/trace".  Given a switch and
 the specification of a flow, "ofproto/trace" shows, step-by-step, how
 such a flow would be treated as it goes through the switch.
@@ -511,7 +511,7 @@ Here's how you can interpret each part of the "learn" action above:
         Make the flow that we add to flow table 10 match the same VLAN
         ID that the packet we're currently processing contains.  This
         effectively scopes the MAC learning entry to a single VLAN,
-        which is the ordinary behavior for a VLAN-aware siwtch.
+        which is the ordinary behavior for a VLAN-aware switch.
 
     NXM_OF_ETH_DST[]=NXM_OF_ETH_SRC[]