--- a/README.rst	Mon Jul 01 23:25:58 2013 -0700
+++ b/README.rst	Mon Jul 01 23:26:50 2013 -0700
@@ -18,8 +18,8 @@
 
 Use the language you are the more used to. Prefer scripting languages like
 Python (you definitely want slices, built-in lists, dictionaries and Unicode
-support). You'll find some solutions in C here but I actually never did
-anything in C during an interview.
+support). You'll find some solutions in C, but I actually never did anything in
+C during an interview.
 
 During phone screens you'll be coding on something like collabedit_, during
 on-site interviews you'll be coding on a whiteboard. In both cases you won't be
@@ -28,13 +28,17 @@
 
 .. _collabedit: http://collabedit.com/
 
+Phone screens usually last 45 minutes, but dont be worried if you need more
+time to work on the exercises presented here. First, that's the point, and
+second your interviewer will help you.
+
 Also
 ----
 
 You'll also get dumb questions like “What is a zombie process”, “What's the
-between hard and symbolic links”, “How many hosts in a /22 ?”. Be prepared for
-some scripting exercises. You should have done some sysadmin and be familiar
-with Linux.
+difference between hard and symbolic links”, “How many hosts in a /22?”. Be
+prepared for some scripting exercises. You should have done some sysadmin and
+be familiar with Linux.
 
 This doesn't include design or troubleshooting questions, I can give you some
 in private.
@@ -42,4 +46,6 @@
 Instead of phone screens, some companies can ask you to do a small project at
 home, again use the tools you are the most familiar with.
 
+Actually probably relevant: http://www.prologin.org/training/.
+
 More lulz: http://projecteuler.net/.