@@ -115,7 +115,7 @@ function has a companion that takes `Options` (like you have `get` and
115115is not all though, because you cannot really use `get` you see in the main
116116module, because you want to have connection sharing. Wreq's author does not
117117take the gift of automatic connection re-use `Manager` from `http-client`
118−provides, it invents the whole new thing of “sessions”. Only inside a
118+provides, he invents the whole new thing of “sessions”. Only inside a
119119session your connections will be shared and re-used. However with the
120120session stuff you have yet another set of per-method functions like `get`
121121and `getWith` — these are different ones, to be used with sessions! Now if
@@ -129,10 +129,10 @@ inconvenient for common tasks.
129129
130130It's funny that one client I worked for had to have his own little wrapper
131131around `http-client` just because he could not possibly use `wreq` and
132−`http-client` and friends were too low-level. The previous paragraph
133−extracted from a talk with a Haskell developer who works for that client.
134−Then I thought to myself “something is wrong with HTTP client libraries in
135−Haskell if they had to make a wrapper”.
132+`http-client` and friends were too low-level. The previous paragraph is
133+extracted from a talk with a Haskell developer who works for that client. I
134+thought to myself “something is wrong with HTTP client libraries in Haskell
135+if they had to make a wrapper”.
136136
137137What else? I used `servant-client` a couple of times but amount of
138138boilerplate is too high. If you have several query parameters, and you use