Typo fixes, h/t Michael Bear

content/articles/2025-04-09-frysix-evpn.md

@@ -250,7 +250,7 @@ turning on OSPF for these), makes the whole network shoot to life. Slick!
 I'll point out that one of the devices in this topology is an Arista. We have several of these ready
 for deployment at FrysIX. They are a lot more affordable and easy to find on the second hand /
 refurbished market. These switches come with 32x100G ports, and are really good at packet slinging
-because they're based on the Broadcom _Tomahawk_ chipset. They pack a few less faetures than the
+because they're based on the Broadcom _Tomahawk_ chipset. They pack a few less features than the
 _Trident_ chipset that powers the Nokia, but they happen to have all the features we need to run our
 internet exchange .  So I turn my attention to the Arista in the topology. I am much more
 comfortable configuring the whole thing here, as it's not my first time touching these devices:
@@ -397,7 +397,7 @@ Neighbor             AS Session State AFI/SAFI                AFI/SAFI State   N
 On this leaf node, I'll have a redundant iBGP session with the two core nodes. Since those core
 nodes are peering amongst themselves, and are configured as route-reflectors, this is all I need. No
 matter how many additional Arista (or Nokia) devices I add to the network, all they'll have to do is
-enable OSPF (so they can reach 198.19.16.0 and .1) and turn on iBGP sesions with both core routers.
+enable OSPF (so they can reach 198.19.16.0 and .1) and turn on iBGP sessions with both core routers.
 Voila!
 
 #### VXLAN EVPN: SR Linux
@@ -422,7 +422,7 @@ This creates the plumbing for a VXLAN sub-interface called `vxlan1.2604` which w
 traffic using VNI 2604 (this happens to be the VLAN id we use at FrysIX for our production Peering
 LAN), and it'll use the `system0.0` address to source that traffic from.
 
-The second part is to create what SR Linux calls a MAC-VRF and put some interface in it:
+The second part is to create what SR Linux calls a MAC-VRF and put some interface(s) in it:
 
 ```
 A:pim@nikhef# set / interface ethernet-1/9 admin-state enable
@@ -462,7 +462,7 @@ previous [[article]({{< ref 2022-02-14-vpp-vlan-gym.md >}})] which my buddy Fred
 _VLAN Gymnastics_ because the ports are just so damn flexible. Worth a read!
 
 The second block creates a new _network-instance_ which I'll name `peeringlan`, and it associates
-the newly crated untagged sub-interface `ethernet-1/9/3.0` with the VXLAN interface, and starts a
+the newly created untagged sub-interface `ethernet-1/9/3.0` with the VXLAN interface, and starts a
 protocol for eVPN instructing traffic in and out of this network-instance to use EVI 2604 on the
 VXLAN sub-interface, and signalling of all MAC addresses learned to use the specified 
 route-distinguisher and import/export route-targets. For simplicity I've just used the same for
@@ -493,7 +493,7 @@ interface Vxlan1
    vxlan vlan 2604 vni 2604
 ```
 
-After creating VLAN 2604 on making port Eth9/3 an access port in that VLAN, I'll add a VTEP endpoint
+After creating VLAN 2604 and making port Eth9/3 an access port in that VLAN, I'll add a VTEP endpoint
 called `Loopback1`, and a VXLAN interface that uses that to source its traffic. Here, I'll associate
 local VLAN 2604 with the `Vxlan1` and its VNI 2604, to match up with how I configured the Nokias
 previously.
@@ -666,7 +666,7 @@ entries. One thing to note -- the SR Linux implementation leaves the type-2 rout
 There's one more thing to show, and that's kind of the 'proof is in the pudding' moment. As I said,
 Arend hooked up a Debian machine with an Intel X710-DA4 network card, which sports 4x10G SFP+
 connections.  This network card is a regular in my AS8298 network, as it has excellent DPDK support
-and can pump easily 40Mpps with VPP. IPng 🥰 Intel X710!
+and can easily pump 40Mpps with VPP. IPng 🥰 Intel X710!
 
 ```
 root@debian:~ # ip netns add nikhef
@@ -781,7 +781,7 @@ gold!
 I also want to thank Niek for helping me take my first baby steps onto this platform and patiently
 answering my nerdly questions about the platform, the switch chip, and the configuration philosophy.
 Learning a new NOS is always a fun task, and it was made super fun because Niek spent an hour with
-Arend and me on a video call, giving a bunch of operational tips and tricks along the way.
+Arend and I on a video call, giving a bunch of operational tips and tricks along the way.
 
 Finally, Arend and ERITAP are an absolute joy to work with. We took turns hacking on the lab, which
 Arend made available for me while I am traveling to Mississippi this week. Thanks for the kWh and