Fix typos and add backticks for PEP-3156. (#202)

pep-3156.txt

@@ -183,7 +183,7 @@ interprocess I/O.
 There is almost always a 1:1 relationship between transport and
 protocol objects: the protocol calls transport methods to send data,
 while the transport calls protocol methods to pass it data that has
-been received.  Neither transport not protocol methods "block" -- they
+been received.  Neither transport nor protocol methods "block" -- they
 set events into motion and then return.
 
 The most common type of transport is a bidirectional stream transport.
@@ -1224,7 +1224,7 @@ Methods For All Transports
 Bidirectional Stream Transports
 '''''''''''''''''''''''''''''''
 
-A bidrectional stream transport is an abstraction on top of a socket
+A bidirectional stream transport is an abstraction on top of a socket
 or something similar (for example, a pair of UNIX pipes or an SSL/TLS
 connection).
 
@@ -1338,12 +1338,12 @@ Unidirectional Stream Transports
 ''''''''''''''''''''''''''''''''
 
 A writing stream transport supports the ``write()``, ``writelines()``,
-``write_eof()``, ``can_write_eof()``, close() and ``abort()`` methods
-described for bidrectional stream transports.
+``write_eof()``, ``can_write_eof()``, ``close()`` and ``abort()`` methods
+described for bidirectional stream transports.
 
 A reading stream transport supports the ``pause_reading()``,
 ``resume_reading()`` and ``close()`` methods described for
-bidrectional stream transports.
+bidirectional stream transports.
 
 A writing stream transport calls only ``connection_made()`` and
 ``connection_lost()`` on its associated protocol.
@@ -1679,7 +1679,7 @@ package are provided:
 - ``asyncio.wait_for(f, timeout)``.  This is a convenience to wait for
   a single coroutine or Future with a timeout.  When a timeout occurs,
   it cancels the task and raises TimeoutError.  To avoid the task
-  cancellation, wrap it in shield().
+  cancellation, wrap it in ``shield()``.
 
 - ``asyncio.gather(f1, f2, ...)``.  Returns a Future which waits until
   all arguments (Futures or coroutines) are done and return a list of
@@ -1871,7 +1871,7 @@ Synchronization
 
 Locks, events, conditions and semaphores modeled after those in the
 ``threading`` module are implemented and can be accessed by importing
-the ``asyncio.locks`` submodule.  Queus modeled after those in the
+the ``asyncio.locks`` submodule.  Queues modeled after those in the
 ``queue`` module are implemented and can be accessed by importing the
 ``asyncio.queues`` submodule.