Skip to content

Commit 7cb09e7

Browse files
committed
Fix references to Async
1 parent f8cfb6b commit 7cb09e7

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

documentation.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -328,7 +328,7 @@ Haskell concurrency design patterns along the way.
328328

329329
In fact, [distributed-process-async][distributed-process-async] does not really consider the
330330
*task layer* in great detail. We provide an API comparable to remote's
331-
`Promise` in `Control.Distributed.Process.Platform.Async`. This API however,
331+
`Promise` in `Control.Distributed.Process.Async`. This API however,
332332
is derived from Simon Marlow's [Control.Concurrent.Async][async] package, and is not
333333
limited to blocking queries on `Async` handles in the same way. Instead our
334334
[API][d-p-async-async] handles both blocking and non-blocking queries, polling

tutorials/4ch.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -342,7 +342,7 @@ data BlockingQueue a = BlockingQueue
342342
### Making use of Async
343343

344344
So **how** can we execute this `Closure (Process a)` without blocking the server
345-
process itself? We can use the `Control.Distributed.Process.Platform.Async` API
345+
process itself? We can use the `Control.Distributed.Process.Async` API
346346
to execute each task asynchronously and provide a means for waiting on the result.
347347

348348
In order to use an `Async` handle to get the result of the computation once it's

0 commit comments

Comments
 (0)