From 7b9f7a5cac7d9182a9f4333f47cbd9163177c451 Mon Sep 17 00:00:00 2001 From: dizgotti Date: Fri, 19 Feb 2021 10:46:11 -0800 Subject: [PATCH] Update README.rst fixed typos --- README.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.rst b/README.rst index c35f63a84f1..6d2cb307c27 100644 --- a/README.rst +++ b/README.rst @@ -24,7 +24,7 @@ Ouroboros-Network protocols which to run ouroboros family of protocols, multiplexing layer. - The `Byron Proxy`_ is a network protocol proxy between Byron and Shelley. It now lives - in a seaprate repository. + in a separate repository. Ouroboros-Network API --------------------- @@ -38,7 +38,7 @@ The API consisists of three layers: it (e.g. ``Ouroboros.Network.Protocol.ChainSync.Client.chainSyncClientPeer``) • callback ``ptcl -> channel -> m ()`` where ``ptcl`` is enumeration for each - mini-protoicol, this is either ``NodeToNodeProtocols`` or + mini-protocol, this is either ``NodeToNodeProtocols`` or ``NodeToClientProtocols``. The callback is wrapped in ``OuroborosApplication`` GADT which allows to differentiate the initiator / responder (or client / server) callbacks. @@ -47,7 +47,7 @@ The API consisists of three layers: version data (the tricky part here is that version data type can be different between different versions; there is a simple way of building this map using a semigroup). You can use ``simpleSingletonVersion`` if your application does - not depend on negotated version data. However, + not depend on negotiated version data. However, ``Ouroboros.Network.NodeToNode`` and ``Ouroboros.Network.NodeToClient`` expose ``V1`` api which hides versioning from the caller.