From be826babb79bdde24f67544fbe2c60436ae37c17 Mon Sep 17 00:00:00 2001 From: Ginger Collison Date: Thu, 6 Feb 2020 12:25:04 -0600 Subject: [PATCH] Update caches.md --- developing-with-nats/sending/caches.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/developing-with-nats/sending/caches.md b/developing-with-nats/sending/caches.md index 309e258..dca1ab5 100644 --- a/developing-with-nats/sending/caches.md +++ b/developing-with-nats/sending/caches.md @@ -113,6 +113,6 @@ nc.close(); ## Flush and Ping/Pong -Many of the client libraries use the [PING/PONG interaction](../connecting/pingpong.md) built into the NATS protocol to insure that flush pushed all of the buffered messages to the server. When an application calls flush, most libraries will put a PING on the outgoing queue of messages, and wait for the server to respond with a PONG before saying that the flush was successful. +Many of the client libraries use the [PING/PONG interaction](../connecting/pingpong.md) built into the NATS protocol to ensure that flush pushed all of the buffered messages to the server. When an application calls flush, most libraries will put a PING on the outgoing queue of messages, and wait for the server to respond with a PONG before saying that the flush was successful. Even though the client may use PING/PONG for flush, pings sent this way do not count towards [max outgoing pings](../connecting/pingpong.md).