@@ -126,7 +126,7 @@ $ chmod 600 ~/.ssh/authorized_keys
126126If you'd like to verify that everything is working as expected, you can test
127127locally on your own machine.
128128
129- First, authorized yourself for ssh. (Make sure to replace 'chrishunt' with
129+ First, authorize yourself for ssh. (Make sure to replace 'chrishunt' with
130130* your* Github username)
131131
132132``` bash
@@ -150,7 +150,7 @@ $ gh-auth remove chrishunt
150150Removing 2 key(s) from ' /Users/chris/.ssh/authorized_keys'
151151```
152152
153- Since you've removed your keys, verify now that you can no longer login to your
153+ Now that you've removed your keys, verify that you can no longer log in to your
154154machine with public key authentication:
155155
156156``` bash
@@ -193,7 +193,7 @@ $ curl http://remote-ip.herokuapp.com
193193### It's still not working! :(
194194
195195In almost all cases, your laptop is not directly plugged into your modem.
196- You're on a wirelress network or plugged directly into a router or switch. This
196+ You're on a wireless network or plugged directly into a router or switch. This
197197means the external IP address that your pair is connecting to is not your
198198machine, it's actually your router.
199199
@@ -214,7 +214,7 @@ ssh -p <port> username@external-ip-address
214214Yes! A nice solution to this is to have a machine ** somewhere else** that both
215215of you can ssh into. Place this machine on a network that you * do* have the
216216ability to forward ports. Maybe this machine is at home, a friend's house, or
217- at a company your worked for in the past that forgot to turn it off.
217+ at a company you worked for in the past that forgot to turn it off.
218218
219219If this isn't possible, then you can use a VPS provider like
220220[ Linode] ( http://www.linode.com ) to setup a pairing machine in the cloud or a
0 commit comments