Skip to content

Commit 19f5556

Browse files
authored
Fix typos
1 parent bd8947a commit 19f5556

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

EXERCISE-4.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -133,7 +133,7 @@ P4 program as well as the ONOS app to make it work.
133133
### Implementing NDP handling for the switch interface IPv6 addresses
134134

135135
We already provide ways to handle NDP NS and NA exchanged by hosts connected to
136-
the same subnet (see `l2_ternary_table`). However, for hosts the Linux
136+
the same subnet (see `l2_ternary_table`). However, for hosts, the Linux
137137
networking stack takes care of generating a NDP NA reply. For the switches in
138138
our fabric, there's no Linux networking stack associated to it.
139139

@@ -147,13 +147,13 @@ There are multiple solutions to this problem:
147147
write P4 code that takes care of replying to NDP requests without any
148148
intervention from the control plane.
149149

150-
We choose to implement the last option to show and interesting use case of P4.
150+
We choose to implement the last option to show an interesting use case of P4.
151151

152152
The idea is simple, NDP NA packets have the same header structure as NDP NS
153153
ones. They are both ICMPv6 packets with different header field values, such as
154154
different ICMPv6 type, different Ethernet addresses etc. A switch that knows the
155155
MAC address of a given IPv6 target address found in an NDP NS request, can
156-
transform the same packet to and NDP NA reply by modifying some of its fields.
156+
transform the same packet to an NDP NA reply by modifying some of its fields.
157157

158158
## Exercise steps
159159

0 commit comments

Comments
 (0)