From 373fc1a7ae21a8b29543238e9a911a7c381db481 Mon Sep 17 00:00:00 2001 From: Levi Notik Date: Tue, 11 Jun 2013 23:00:08 -0400 Subject: [PATCH] Fix typo in docs --- akka-docs/rst/general/actor-systems.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/akka-docs/rst/general/actor-systems.rst b/akka-docs/rst/general/actor-systems.rst index c63c8c470a..580b288752 100644 --- a/akka-docs/rst/general/actor-systems.rst +++ b/akka-docs/rst/general/actor-systems.rst @@ -117,7 +117,7 @@ Blocking Needs Careful Management In some cases it is unavoidable to do blocking operations, i.e. to put a thread to sleep for an indeterminate time, waiting for an external event to occur. Examples are legacy RDBMS drivers or messaging APIs, and the underlying reason -in typically that (network) I/O occurs under the covers. When facing this, you +is typically that (network) I/O occurs under the covers. When facing this, you may be tempted to just wrap the blocking call inside a :class:`Future` and work with that instead, but this strategy is too simple: you are quite likely to find bottlenecks or run out of memory or threads when the application runs