Small FAQ updates.

docs/faq/asyncio.rst

@@ -1,4 +1,4 @@
-asyncio usage
+Using asyncio
 =============
 
 .. currentmodule:: websockets

docs/faq/common.rst

@@ -109,10 +109,8 @@ Use :func:`~asyncio.wait_for`::
 
     await asyncio.wait_for(websocket.recv(), timeout=10)
 
-This technique works for most APIs, except for asynchronous context managers.
-See `issue 574`_.
-
-.. _issue 574: https://github.com/aaugustin/websockets/issues/574
+This technique works for most APIs. When it doesn't, for example with
+asynchronous context managers, websockets provides an ``open_timeout`` argument.
 
 How can I pass arguments to a custom protocol subclass?
 -------------------------------------------------------

docs/faq/misc.rst

@@ -33,8 +33,8 @@ Instead, use the real import paths e.g.::
     websockets.client.connect(...)
     websockets.server.serve(...)
 
-Why is websockets slower than another Python library in my benchmark?
-.....................................................................
+Why is websockets slower than another library in my benchmark?
+..............................................................
 
 Not all libraries are as feature-complete as websockets. For a fair benchmark,
 you should disable features that the other library doesn't provide. Typically,

docs/faq/server.rst

@@ -139,7 +139,7 @@ Add error handling according to the behavior you want if the user disconnected
 before the message could be sent.
 
 This example supports only one connection per user. To support concurrent
-connects by the same user, you can change ``CONNECTIONS`` to store a set of
+connections by the same user, you can change ``CONNECTIONS`` to store a set of
 connections for each user.
 
 If you're running multiple server processes, call ``message_user`` in each
@@ -213,7 +213,7 @@ client, as shown in the :doc:`tutorial <../intro/tutorial2>`. When you want to
 authenticate the connection before routing it, this is usually more convenient.
 
 Generally speaking, there is far less emphasis on the request path in WebSocket
-servers than in HTTP servers. When a WebSockt server provides a single endpoint,
+servers than in HTTP servers. When a WebSocket server provides a single endpoint,
 it may ignore the request path entirely.
 
 How do I access HTTP headers?