summer-reading: another phrasing tweak

[wiki.git] / doc / szs.mdwn

diff --git a/doc/szs.mdwn b/doc/szs.mdwn
index 0dfd3c0c94250b125c95f01c0852f27aa66946ad..9f9adc66f1c5e004f465e6b9e69aba60a8206c43 100644 (file)
--- a/doc/szs.mdwn
+++ b/doc/szs.mdwn
@@ -6,7 +6,7 @@ This service relays messages between [Zephyr](http://sipb.mit.edu/doc/zephyr/) a
 
 ## Zephyr to SMS
 
 
 ## Zephyr to SMS
 

-To send zephyrs to a phone address as an Athena user, use your favorite zephyr client (see [USING ZEPHYR (A.K.A. ZEPHYR FOR DUMMIES)](http://sipb.mit.edu/doc/zephyr/) if you're not sure what this means) to zwrite `daemon.webzephyr` with a class of `szs` and an instance of `1234567890@servicemail.foo`; for instance, in Barnowl, 
+To send zephyrs to a phone address as an Athena user, use your favorite zephyr client (see [Using Zephyr](http://sipb.mit.edu/doc/zephyr/) if you're not sure what this means) to zwrite `daemon.webzephyr` with a class of `szs` and an instance of `1234567890@servicemail.foo`; for instance, in Barnowl, 

 
        ----> zwrite daemon.webzephyr -c szs -i 1234567890@servicemail.foo
        Hi imaginary friend, how are you doing? I'm sending you a text message through Zephyr.
 
        ----> zwrite daemon.webzephyr -c szs -i 1234567890@servicemail.foo
        Hi imaginary friend, how are you doing? I'm sending you a text message through Zephyr.


@@ -79,4 +79,4 @@ Therefore you could have multiple startup files if you wish. However, do note th
 ### Screen
 If you are going to regularly send and receive text messages using the Barnowl client for Zephyr, you will probably want a Barnowl instance running 24/7 so that whoever texts you won't encounter a `user not subscribed` error and so that your text message conversations don't disappear each time you quit Barnowl. 
 
 ### Screen
 If you are going to regularly send and receive text messages using the Barnowl client for Zephyr, you will probably want a Barnowl instance running 24/7 so that whoever texts you won't encounter a `user not subscribed` error and so that your text message conversations don't disappear each time you quit Barnowl. 
 

-A good way to do this is to use screen and run it on the SIPB dialup machine, which allows you to run a Barnowl session within screen on the SIPB dialup machine that's theoretically up 24/7 (sadly outages do occur). See [UsingScreen](http://sipb-www.scripts.mit.edu/doc/wiki/UsingScreen) for more information; the basic idea is to `ssh` to `kusername@linux.mit.edu` and run `add kchen; owl-screen`, and in the future after `ssh`-ing to `kusername@linux.mit.edu` run `screen -dr`.
+A good way to do this is to use screen and run it on the SIPB dialup machine, which allows you to run a Barnowl session within screen on the SIPB dialup machine that's theoretically up 24/7 (sadly outages do occur). See [Using Screen](http://sipb-www.scripts.mit.edu/doc/wiki/UsingScreen) for more information; the basic idea is to `ssh` to `kusername@linux.mit.edu` and run `add kchen; owl-screen`, and in the future after `ssh`-ing to `kusername@linux.mit.edu` run `screen -dr`.