From b0771d6f2b4e5c9a6020ec81f5178ff2690db8bf Mon Sep 17 00:00:00 2001 From: Cais Manai Date: Thu, 1 Nov 2018 16:53:47 +0000 Subject: [PATCH] Fixing a single typo (#4152) changing "areshared" to "are shared" --- docs/source/api-flows.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/api-flows.rst b/docs/source/api-flows.rst index 2b6a383df5..682c600a95 100644 --- a/docs/source/api-flows.rst +++ b/docs/source/api-flows.rst @@ -798,7 +798,7 @@ Because of this, care must be taken when performing locking or waiting operation Locking ^^^^^^^ -Flows should avoid using locks or interacting with objects that areshared between flows (except for ``ServiceHub`` and other +Flows should avoid using locks or interacting with objects that are shared between flows (except for ``ServiceHub`` and other carefully crafted services such as Oracles. See :doc:`oracles`). Locks will significantly reduce the scalability of the node, and can cause the node to deadlock if they remain locked across flow context switch boundaries (such as when sending and receiving from peers, as discussed above, or sleeping, as discussed below).