From 9b233ba3eacb8e5a9a2816e2d6b508297243c675 Mon Sep 17 00:00:00 2001
From: James Ray <16969914+jamesray1@users.noreply.github.com>
Date: Fri, 27 Jul 2018 18:46:45 +1000
Subject: [PATCH] Fix repeatedly spelling, more and more, add a clarification
 (#376)

Correct me if saying "close connections to non-responsive remotes (which would then de-allocate memory for the ping)" is wrong.
---
 ping/README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/ping/README.md b/ping/README.md
index 454458b8..6fa1dcfe 100644
--- a/ping/README.md
+++ b/ping/README.md
@@ -18,13 +18,13 @@ future that is signalled only when the remote answers. If the remote is not resp
 future will never be signalled.
 
 For implementation reasons, resources allocated for a ping are only ever fully reclaimed after
-a pong has been received by the remote. Therefore if you repeatidely ping a non-responsive
-remote you will end up using more and memory memory (albeit the amount is very very small every
+a pong has been received by the remote. Therefore if you repeatedly ping a non-responsive
+remote you will end up using more and more memory (albeit the amount is very very small every
 time), even if you destroy the future returned by `ping`.
 
 This is probably not a problem in practice, because the nature of the ping protocol is to
 determine whether a remote is still alive, and any reasonable user of this crate will close
-connections to non-responsive remotes.
+connections to non-responsive remotes (which would then de-allocate memory for the ping).
 
 # Example