Sisyphus doc updates (#218)

* Update lab_pp expected output. (#192)

* Add clarification about epoll() usage. (#209)

_docs/networking_mp.md

@@ -46,6 +46,8 @@ So why would we ever want to use edge triggered behavior? Well, consider what ha
 
 Edge triggered mode (together with the `EPOLLONESHOT` flag) guarantees that a single thread will handle all the data that arrived on that given socket, so (although with some additional code complexity) it's not possible that two threads accidentally 'steal' the file descriptor data from each other.
 
+**Note**: You **must** use `epoll()` for this assignment. If you do not, you will get a 0 on all tests that use your server.
+
 ## The Problem
 
 You'll be writing the client and server for a simplified file sharing application. TCP is used for everything here, so reliability is taken care of. The server uses non-blocking I/O (with epoll) to handle concurrent requests. The application supports four basic operations - `GET`, `PUT`, `LIST` and `DELETE`. Their functions are as follows:

_docs/perilous_pointers.md

@@ -49,7 +49,7 @@ Hello World!
 == seven() ==
 0.000000 0.100000 0.200000 0.300000 0.400000 0.500000 0.600000 0.700000 0.800000 0.900000
 == eight() ==
-0 10 40 90 160 250 360 490 640 810
+0 10 40 90 160 250 360 490 640 810 
 == nine() ==
 orange and blue!
 ORANGE and blue!
@@ -59,17 +59,17 @@ orange and blue!
 The radius of the circle is: 17.500000.
 The radius of the circle is: 10.000000.
 == clear_bits() ==
-170
-0
-171
-0
-20
-0
-== little finite automatons
-5
-4
-6
-7
+cleared_value: 170
+cleared_value: 0
+cleared_value: 171
+cleared_value: 0
+cleared_value: 20
+cleared_value: 0
+== little finite automata ==
+final state: 5
+final state: 4
+final state: 6
+final state: 7
 ```
 
 Note that you can just diff with ```part1-expected-output```.