-It can be very annoying to have to close Barnowl when you turn off
+It can be very annoying to have to close BarnOwl when you turn off
your computer. During the time your computer is off, you're missing
many (possibly important) zephyrs. It can be aggravating to be using
zephyr via an unreliable network connection. It can also be
your computer. During the time your computer is off, you're missing
many (possibly important) zephyrs. It can be aggravating to be using
zephyr via an unreliable network connection. It can also be
@@ -308,7+308,7 @@ this? These problems can be solved with the magic of screen.
A more detailed and extensive explanation of this can be found at
[http://web.mit.edu/kchen/arch/common/bin/owl-screen.txt](http://web.mit.edu/kchen/arch/common/bin/owl-screen.txt). Basic commands are [Ctrl-a] followed by [c] to open a new window (like a tab), [Ctrl-a][w] to see a list of open windows, and [Ctrl-a] followed by a number to go to that window.
A more detailed and extensive explanation of this can be found at
[http://web.mit.edu/kchen/arch/common/bin/owl-screen.txt](http://web.mit.edu/kchen/arch/common/bin/owl-screen.txt). Basic commands are [Ctrl-a] followed by [c] to open a new window (like a tab), [Ctrl-a][w] to see a list of open windows, and [Ctrl-a] followed by a number to go to that window.
-Do note that running `owl-screen` as apposed to just runnning `screen` and then a barnowl instance provides niceties such as reminders to renew your tickets (the process `/mit/kchen/arch/i386_rhel4/bin/cont-renew-notify`). Also, Barnowl will always be located on the `0` tab of an `owl-screen` instance, so [Ctrl-a][0] will always take you back to Barnowl.
+Do note that running `owl-screen` as apposed to just runnning `screen` and then a barnowl instance provides niceties such as reminders to renew your tickets (the process `/mit/kchen/arch/i386_rhel4/bin/cont-renew-notify`). Also, BarnOwl will always be located on the `0` tab of an `owl-screen` instance, so [Ctrl-a][0] will always take you back to BarnOwl.