asyncio doc: explain where does the task come from.

diff --git a/Doc/library/asyncio-task.rst b/Doc/library/asyncio-task.rst
index 836125740212e95d13a6a611d463c33883116259..adc344e2168c8bf9f2da0417287c7a2ed92adf6c 100644 (file)
--- a/Doc/library/asyncio-task.rst
+++ b/Doc/library/asyncio-task.rst
@@ -108,10 +108,12 @@ Sequence diagram of the example:
 .. image:: tulip_coro.png
    :align: center
 
-The diagram shows the logical links between the task and the two coroutines, it
-does not describe exactly how things work internally. For example, the sleep
-coroutine creates an internal future which uses
-:meth:`BaseEventLoop.call_later` to wake up the task in 1 second.
+The "Task" is created by the :meth:`BaseEventLoop.run_until_complete` method
+when it gets a coroutine instead of a task.
+
+The diagram shows the control flow, it does not describe exactly how things
+work internally. For example, the sleep coroutine creates an internal future
+which uses :meth:`BaseEventLoop.call_later` to wake up the task in 1 second.
 
 
 InvalidStateError