Skip to content

Commit 2fe443b

Browse files
aaronj1335qwwdfsad
authored andcommitted
grammatical tweaks
thanks for the thorough docs!
1 parent 153e21f commit 2fe443b

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/exception-handling.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -360,9 +360,9 @@ Caught original java.io.IOException
360360
As we have studied before, cancellation is a bidirectional relationship propagating through the whole
361361
coroutines hierarchy. But what if unidirectional cancellation is required?
362362

363-
Good example of such requirement can be a UI component with the job defined in its scope. If any of UI's child task
364-
has failed, it is not always necessary to cancel (effectively kill) the whole UI component,
365-
but if UI component is destroyed (and its job is cancelled), then it is necessary to fail all children jobs as their result is no longer required.
363+
A good example of such a requirement is a UI component with the job defined in its scope. If any of the UI's child tasks
364+
have failed, it is not always necessary to cancel (effectively kill) the whole UI component,
365+
but if UI component is destroyed (and its job is cancelled), then it is necessary to fail all child jobs as their results are no longer required.
366366

367367
Another example is a server process that spawns several children jobs and needs to _supervise_
368368
their execution, tracking their failures and restarting just those children jobs that had failed.

0 commit comments

Comments
 (0)