X-Git-Url: https://sipb.mit.edu/gitweb.cgi/wiki.git/blobdiff_plain/d9aa2b8b1efdb7aaa58c4fafb76228515dddf90c..13a7995e3edd6bd7311354bddbd412ccad41b9ff:/doc/UsingZephyr

diff --git a/doc/UsingZephyr b/doc/UsingZephyr
index 3359d83..00885bf 100644
--- a/doc/UsingZephyr
+++ b/doc/UsingZephyr
@@ -80,13 +80,13 @@ Some common classes include:
 
 If you spend enough time on Zephyr, you'll begin noticing some strange phrases and words being thrown around.  Some of these include:
 
-'''i,i foo''':  originated from CMU and means "I have no point here, I just like to say:".  Sometimes people simply use quotes: {{{"foo"}}}.
+'''i,i foo''':  picked up from CMU zephyrland and means "I have no point here, I just like saying:".  Sometimes people simply use quotes: {{{"foo"}}}.
 
 '''mix''':  If somebody accidentally sends a Zephyr to the wrong class or person, they will send another Zephyr to that wrong/class person simply saying "mix".  This basically just means, "oops, sorry, I didn't mean to send that Zephyr here".  You might also see "-i mix", which is the same thing, only with instances.
 
 '''.d''':  You may see an instance change from {{{-i foo}}} to {{{-i foo.d}}}.  This indicates a deviation or tangent from the the original topic.
 
-'''starking''': Answering a question or replying to a topic to a topic several hours (or days, occasionally) later. The term originates from Greg Stark, who would often reply to zephyrs without seeing if anyone had answered yet, or worse, if the instance had moved on to an entirely different topic.
+'''starking''': Answering a question or replying to a topic to a topic several hours (or days, occasionally) later. The term originates from Greg Stark, who would often reply to zephyrs hours or occasionally days later without seeing if anyone had answered yet, or worse, if the instance had moved on to an entirely different topic.
 
 '''ttants''':  Literally, "Things That Are Not The Same".
 
@@ -160,7 +160,7 @@ For more detailed information on filters, visit https://barnowl.scripts.mit.edu:
 
 == Running Barnowl in Screen ==
 
-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 also be frustrating if you leave your computer on with Zephyr up, but go to a different computer and want to check your zephyrs - how do you do this?  These problems can be solved with the magic of screen.
+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 frustrating if you leave your computer on with Zephyr up, but go to a different computer and want to check your zephyrs - how do you do 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/bin/owl-screen.txt.
 
@@ -200,4 +200,10 @@ kinit -l1d -r7d -54
 
 To detach a screen session (for example, if you want to log out), press C-a d (Control-A, then D).  Screen continues to run, but is no longer active.
 
-To reattach a screen session if it isn't detached, run {{{screen -r}}}.  To attach it but keep it attached elsewhere, you can run {{{screen -x}}}; you can use C-a F to resize it to your current window's size.  There are other options available, run {{{man screen}}} to learn more about them.
\ No newline at end of file
+To reattach a screen session, possibly detaching from wherever it's currently attached, run:
+
+{{{
+screen -dr
+}}}
+
+{{{screen}}} can do a whole lot more.   To find out about it, see UsingScreen.
\ No newline at end of file