1.1 --- a/README	Mon Aug 25 04:11:58 2014 +0200
     1.2 +++ b/README	Mon Aug 25 11:38:47 2014 +0200
     1.3 @@ -83,8 +83,8 @@
     1.4  
     1.5  Obviously, this isn't something we want to do in every function that accepts
     1.6  sequential data. Therefore, we usually decide for one of the two first forms
     1.7 -and therefore disallow the other possible representation of sequential data to
     1.8 -be passed to the function.
     1.9 +and thus disallow the other possible representation of sequential data to be
    1.10 +passed to the function.
    1.11  
    1.12  This extension, however, modifies Lua's ``ipairs`` statement in such way that
    1.13  it automatically accepts either a table or an iterator function as argument.
    1.14 @@ -143,8 +143,10 @@
    1.15  Though, if such behavior is desired, it can still be implemented through the
    1.16  ``__ipairs`` metamethod.
    1.17  
    1.18 -Unless manually done by the user in the ``__ipairs`` metamethod, this extension
    1.19 -never creates any closures or other values that need to be garbage collected.
    1.20 +Unless manually done by the user in the ``__ipairs`` metamethod, the ``ipairs``
    1.21 +function as well as the corresponding C functions and macros provided by this
    1.22 +extension never create any closures or other values that need to be garbage
    1.23 +collected.
    1.24  
    1.25  
    1.26