aboutsummaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorColin Okay <cbeok@protonmail.com>2020-08-05 16:31:23 -0500
committerColin Okay <cbeok@protonmail.com>2020-08-05 16:31:23 -0500
commitc7cd3b0d58aa0348591c3442cc190a3585141314 (patch)
treed3f61f1ddea327283f1143f9df33f8b7a0efa206
parent6c765c4edad4a3c713bfd95732e50370c19814fb (diff)
typo and wording
-rw-r--r--README.md10
1 files changed, 5 insertions, 5 deletions
diff --git a/README.md b/README.md
index 4757fa5..3c6e589 100644
--- a/README.md
+++ b/README.md
@@ -603,7 +603,7 @@ trying to get it.
### The Naughty Consumer
-Now that the mysteries that make generators go has been explained in
+Now that the mysteries that make generators go have been explained in
the previous section, you may be tempted to manually call `next` and
`has-next-p` on your generators. If you must do this, you should use
the `with-generator` macro:
@@ -619,10 +619,10 @@ a
```
The `with-generator` form will ensure that the generator is properly
-closed. Could be useful with generators backed by input streams that
-need a custom logic that is hard to build using the basic tools. I'm
-not sure if you ever *will* need it, but the library provides it just
-in case.
+closed. It could be useful with generators backed by input streams
+that need a custom logic, or perhaps in some case where you need to
+interleave operations between multiple generators. I'm not sure if you
+ever *will* need it, but the library provides it just in case.
## The Permutations Example