From 92402c3e12daebc9215e8968ea9c0faee2fbbf7e Mon Sep 17 00:00:00 2001 From: Ginger Collison Date: Fri, 26 Jun 2020 13:44:57 -0500 Subject: [PATCH] Update README.md --- nats-protocol/nats-protocol/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nats-protocol/nats-protocol/README.md b/nats-protocol/nats-protocol/README.md index d817430..b45185b 100644 --- a/nats-protocol/nats-protocol/README.md +++ b/nats-protocol/nats-protocol/README.md @@ -59,7 +59,7 @@ The following sections explain each protocol message. ### Description -A client will need to start as a plain TCP connection, then wehn the server accepts a connection from the client, it will send information about itself, the configuration and security requirements are necessary for the client to successfully authenticate with the server and exchange messages. +A client will need to start as a plain TCP connection, then when the server accepts a connection from the client, it will send information about itself, the configuration and security requirements are necessary for the client to successfully authenticate with the server and exchange messages. When using the updated client protocol \(see [`CONNECT`](./#connect) below\), `INFO` messages can be sent anytime by the server. This means clients with that protocol level need to be able to asynchronously handle `INFO` messages.