From 4ff8998c5cbe5abcb3490c2d5b95a2a1e6d47104 Mon Sep 17 00:00:00 2001 From: Ben Pfaff Date: Mon, 22 Apr 2013 21:17:50 -0700 Subject: [PATCH] tutorial: Correct typos. Reported-by: Yeming Zhao Signed-off-by: Ben Pfaff --- tutorial/Tutorial | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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[] -- 2.43.0