docs: Removed contradicting information about the event_loop fixture not setting the global event loop.

Signed-off-by: Michael Seifert <[email protected]>

Author: seifertm

README.rst

@@ -123,19 +123,16 @@ Fixtures
 
 ``event_loop``
 ~~~~~~~~~~~~~~
-Creates and injects a new instance of the default asyncio event loop. By
-default, the loop will be closed at the end of the test (i.e. the default
-fixture scope is ``function``).
+Creates a new asyncio event loop based on the current event loop policy. The new loop
+is available as the return value of this fixture or via `asyncio.get_running_loop <https://docs.python.org/3/library/asyncio-eventloop.html#asyncio.get_running_loop>`__.
+The event loop is closed when the fixture scope ends. The fixture scope defaults
+to ``function`` scope.
 
 Note that just using the ``event_loop`` fixture won't make your test function
 a coroutine. You'll need to interact with the event loop directly, using methods
 like ``event_loop.run_until_complete``. See the ``pytest.mark.asyncio`` marker
 for treating test functions like coroutines.
 
-Simply using this fixture will not set the generated event loop as the
-default asyncio event loop, or change the asyncio event loop policy in any way.
-Use ``pytest.mark.asyncio`` for this purpose.
-
 .. code-block:: python
 
     def test_http_client(event_loop):