From ca18311b486bfcb4e9b8e3b3d3c4cb7cdec69fb5 Mon Sep 17 00:00:00 2001 From: xla Date: Wed, 1 Sep 2021 15:21:25 +0200 Subject: [PATCH] Finput Co-authored-by: Fintan Halpenny --- docs/rfc/0696-p2p-node.adoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/rfc/0696-p2p-node.adoc b/docs/rfc/0696-p2p-node.adoc index 321391e0c..f2639a0b8 100644 --- a/docs/rfc/0696-p2p-node.adoc +++ b/docs/rfc/0696-p2p-node.adoc @@ -21,7 +21,7 @@ regards to the configuration given (e.g. tracking behaviour) and lifetime of the process (i.e. socket-activated or long-running). It also strives to recommend APIs and mechanisms -- in the form of non-core -protocols - which remove the need for online requests made by clients to a +protocols -- which remove the need for online requests made by clients to a running node. == Terminology and Conventions @@ -50,9 +50,9 @@ outputs of these protocols are used for effect management. === Subroutines -This section expands on the auxilliary routines driven by the node on top of the -core protocol. Where each SHOULD be allow to be disabled through configuration. -A subroutine acts as reactor driving a protocol by feeding inputs - usually +This section expands on the auxiliary routines driven by the node on top of the +core protocol. Where each SHOULD be allowed to be disabled through configuration. +A subroutine acts as a reactor driving a protocol by feeding inputs - usually results of effects (i/o, timers, etc.) - to it and capturing the outputs to schedule new effects (i/o, timers, etc.).