Finput

Co-authored-by: Fintan Halpenny <[email protected]>

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.).