Update lua-introduction.rst

readthedocs/lua-introduction.rst

@@ -338,8 +338,10 @@ This is perhaps the most advanced feature in Lua, and not one that can be demons
   -- above will print 'world' 
   -- status above will be true
   -- but now the coroutine has ended so further calls to resume will return status as false
-  
-In the Lua documentation, the return value from ``coroutine.create()`` is called a ``thread``. However this is misleading as Lua does not have threads. You can think of this thread as another Lua stack. Basically when Lua executes any code - the code operates on a Lua stack. Initially there is only one stack. When you create a coroutine, a new stack is allocated, and the all functions called from the coroutine will operate on this new stack. Since the Lua stack is a heap allocated structure - suspending the coroutine is equivalent to returning back to the caller using a ``longjmp()``. The stack is preserved, so that the that function that yielded can be resumed from wherever it suspended itself.
+ 
+By the fact that 'hello' is printed before 'world' we can tell that the coroutine was suspended and then resumed. 
+ 
+In the Lua documentation, the return value from ``coroutine.create()`` is called a ``thread``. However this is misleading as Lua does not have threads. You can think of this ``thread`` as another Lua stack. Basically whenever Lua executes any code - the code operates on a Lua stack. Initially there is only one stack. When you create a coroutine, a new stack is allocated, and the all functions called from the coroutine will operate on this new stack. Since the Lua stack is a heap allocated structure - suspending the coroutine is equivalent to returning back to the caller using a ``longjmp()``. The stack is preserved, so that the function that yielded can be resumed from wherever it suspended itself.