mention four meeting requirement

[wiki.git] / join.mdwn

diff --git a/join.mdwn b/join.mdwn
index bc6ad4a74ac836455666a33835d207244708e735..20658ef7b2ca747a2b448eb6eceaf93968c647f7 100644 (file)
--- a/join.mdwn
+++ b/join.mdwn
@@ -16,17 +16,17 @@ topics technical and otherwise.
 
 Prospective members are encouraged to **hang out around the SIPB office** during
 meetings (they're Mondays at 7:30PM) and at other times (check the door icon on
-[sipb.mit.edu](http://sipb.mit.edu/) to see if the office is open).
+[sipb.mit.edu](http://sipb.mit.edu/) to see if the office is open). (Coming to at least four meetings is required to be membered, though usually this happens before prospectives are otherwise ready to be membered.)
 
 You can also participate in SIPB activities like hackathons,
 [cluedumps](http://cluedumps.mit.edu/), and [IAP
-classes](http://sipb.mit.edu/iap). Our [[calendar]] contains the many of our
+classes](http://sipb.mit.edu/iap). Our [[calendar]] contains many of our
 events.
 
 ### "Furthering the Goals of SIPB"
 
-"Furthering the Goals of SIPB", or FTGOSing, usually means working on some SIPB
-[[projects]].
+"Furthering the Goals of SIPB", or FTGOSing, usually means **working on some SIPB
+[[projects]]**.
 
 Our technical [[projects]] can generally absorb arbitrary amounts of attention. If
 you are already familiar with the relevant skills, you may be able to find the
@@ -47,7 +47,7 @@ progress to the SIPB.  The most successful SIPB projects have often been things
 that the people involved really wanted to do, and found resources or
 collaborators to do them through SIPB.
 
-### One route
+### A possible route
 
 There are many possible ways to get involved in SIPB, but one route is: