Skip to content

Commit af428dd

Browse files
committed
Fix some typos in README
1 parent a735926 commit af428dd

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ indicating whether ``x`` can be iterated. It is important to note that
2121
a ``true`` return value does *not* indicate that one can call the
2222
``start`` method on ``x``, instead a consumer *must* call ``getiterator(x)``
2323
if ``isiterable(x)`` returned true, and can then call ``start`` on the
24-
instance that is returned by ``getiterator``. The proper pattern to
24+
instance that is returned by ``getiterator``. The proper pattern for
2525
consumer code therefore looks like this:
2626
````julia
2727
if isiterable(x)
@@ -32,7 +32,7 @@ if isiterable(x)
3232
end
3333
````
3434
This consumer pattern will work with iterators that don't opt into the
35-
extensions in this package here and with iterators that have opted into
35+
extensions in this package and with iterators that have opted into
3636
the extended interface defined in this package.
3737

3838
There are two scenarios when a source might participate in this extended
@@ -46,7 +46,7 @@ of a different type with enough type information for a type stable
4646
implementation of the core iterator interface that iterates the elements
4747
of the original source.
4848

49-
Sometimes such a source might not want to implement the ``start``, ``next``
49+
Second, sometimes such a source might not want to implement the ``start``, ``next``
5050
and ``done`` method at all for its core type. If that is the case, this
5151
source can add a method to ``isiterable`` that returns ``true``, even
5252
though the source does not have a ``start`` method. As long as this source

0 commit comments

Comments
 (0)