@@ -193,7 +193,7 @@ mapM f (Stream step1 state1) = Stream step state
193193```
194194
195195* For the input streams use numbering for `step` and `state` e.g.
196− step1/state1. For the ouput stream use `step` and `state`.
196+ step1/state1. For the output stream use `step` and `state`.
197197* For state argument of `step`, use `st`.
198198* For result of executing a `step` use `r` or `res`
199199* For the yielded element use `x`
@@ -221,7 +221,7 @@ type inference minimal and type errors can be discovered incrementally by
221221increasing the scope a little bit at a time. If you use type signatures on all
222222top level declarations then you do not even need to comment out the code. This
223223organization results in a better order of type errors which makes it easier to
224−fix them and when necessary use elimination method by commenting out some code.
224+fix them and when necessary, use elimination method by commenting out some code.
225225
226226Similarly when you put modules in the cabal file in dependency order you can
227227do the same there, just comment out a tail of the module list and your library