@@ -12,7 +12,7 @@ by individually sending a (RESTful) HTTP API request to some third party API
12
12
for each record. Estimating each call to take around ` 0.3s ` means that having
13
13
` 10000 ` users processed sequentially, you would have to wait around 50 minutes
14
14
for all jobs to complete. This works perfectly fine for a small number of
15
- operations, but keeping thousands of jobs in memory at once may easly take up
15
+ operations, but keeping thousands of jobs in memory at once may easily take up
16
16
all resources on your side.
17
17
Instead, you can use this library to stream your arbitrarily large input list
18
18
as individual records to a non-blocking (async) transformation handler. It uses
@@ -141,7 +141,7 @@ also takes care of mangaging streaming throughput and back-pressure.
141
141
The transformation handler can be any non-blocking (async) callable that uses
142
142
[ promises] ( #promises ) to signal its eventual results. This callable receives
143
143
a single data argument as passed to the writable side and must return a
144
- promise. A succesful fulfillment value will be forwarded to the readable end
144
+ promise. A successful fulfillment value will be forwarded to the readable end
145
145
of the stream, while an unsuccessful rejection value will emit an ` error `
146
146
event and then ` close() ` the stream.
147
147
@@ -306,7 +306,7 @@ passed through its transformation handler which is responsible for processing
306
306
and transforming this data (see above for more details).
307
307
308
308
The ` Transformer ` takes care of passing data you pass on its writable side to
309
- the transformation handler argument and forwarding resuling data to it
309
+ the transformation handler argument and forwarding resulting data to it
310
310
readable end.
311
311
Each operation may take some time to complete, but due to its async nature you
312
312
can actually start any number of (queued) operations. Once the concurrency limit
@@ -341,7 +341,7 @@ $transformer->write('http://example.com/');
341
341
```
342
342
343
343
This handler receives a single data argument as passed to the writable side
344
- and must return a promise. A succesful fulfillment value will be forwarded to
344
+ and must return a promise. A successful fulfillment value will be forwarded to
345
345
the readable end of the stream, while an unsuccessful rejection value will
346
346
emit an ` error ` event, try to ` cancel() ` all pending operations and then
347
347
` close() ` the stream.
0 commit comments