Small typos

projects/alamesh/setting_up_bird.md

@@ -180,7 +180,7 @@ protocol static {
 # magic happens. We use a template since every peer will essentially
 # have the same BGP configuration. The template name is `alapeers`.
 #
-# Each peer gets its own template nad file under `peers6/*``.
+# Each peer gets its own template and file under `peers/*``.
 #
 # We're using BGP in "exterior" or `eBGP` mode. This means we're using
 # the protocol to define routes between Autonomous Systems, not really
@@ -242,14 +242,16 @@ Done! Adding a new peer just means adding a new file in the peers directory.
 
 # ROA Tables
 
-ROA == Route Origin Authorization. This is basically a central list of who owns what routes and is allowed to send changes. 
+ROA is *Route Origin Authorization*. This is basically a central list of who owns what routes and is allowed to send changes. 
 There's some crypto stuff you can do too, but that's only really important if we start letting arbitrary people join.
 
 There is a concern that one of us messes up the config and starts sending out bad routes, but we'll cross that bridge 
-when we get there (large outage lol). ROA tables might help prevent that.
+when we get there (which would be a large outage lol). ROA tables help prevent that.
 
 # What's Next
 
+> Look below!
+
 Now I need to actually test this with another router. I'll most likely setup another VPS or ask someone else to spin 
 something up.
 
@@ -257,7 +259,6 @@ I need to determine a fake AS number, subnets, etc, and then I'll report back if
 configuration, I plan to connect lykos to a different router running on a different subnet, and then ssh into hyperion 
 from lykos. The routes should "just work" (right lol).
 
-
 # (edit) Testing Bird with Two Routers
 
 I have two DO droplets that will run bird. Here's how I'm setting up the network.