From: Josh Soref <jsoref@users.noreply.github.com>
Date: Sun, 23 Jul 2017 18:54:32 +0000 (-0400)
Subject: spelling: necessarily
X-Git-Tag: trac5124a_base~35^2~95
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=55cb83f3cbc01c58dcb8f86eaf9b8ef21f47ef28;p=thirdparty%2Fkea.git

spelling: necessarily
---

diff --git a/src/lib/asiodns/io_fetch.cc b/src/lib/asiodns/io_fetch.cc
index fcc8d52bce..a836871aa0 100644
--- a/src/lib/asiodns/io_fetch.cc
+++ b/src/lib/asiodns/io_fetch.cc
@@ -234,7 +234,7 @@ IOFetch::operator()(boost::system::error_code ec, size_t length) {
         return;
 
     // On Debian it has been often observed that boost::asio async
-    // operations result in EINPROGRESS. This doesn't neccessarily
+    // operations result in EINPROGRESS. This doesn't necessarily
     // indicate an issue. Thus, we continue as if no error occurred.
     } else if (ec && (ec.value() != boost::asio::error::in_progress)) {
         logIOFailure(ec);
diff --git a/src/lib/asiolink/tests/tcp_acceptor_unittest.cc b/src/lib/asiolink/tests/tcp_acceptor_unittest.cc
index fbfe5e6dc3..a88a07a971 100644
--- a/src/lib/asiolink/tests/tcp_acceptor_unittest.cc
+++ b/src/lib/asiolink/tests/tcp_acceptor_unittest.cc
@@ -97,7 +97,7 @@ public:
             // error code, but simply wait for the connection to get
             // established before the handler is invoked. It turns out, however,
             // that on some OSes the connect handler may receive this error code
-            // which doesn't neccessarily indicate a problem. Making an attempt
+            // which doesn't necessarily indicate a problem. Making an attempt
             // to write and read from this socket will typically succeed. So,
             // we ignore this error.
             if (ec.value() != boost::asio::error::in_progress) {
diff --git a/src/lib/asiolink/tests/tcp_socket_unittest.cc b/src/lib/asiolink/tests/tcp_socket_unittest.cc
index 5d9400a8f8..e247722099 100644
--- a/src/lib/asiolink/tests/tcp_socket_unittest.cc
+++ b/src/lib/asiolink/tests/tcp_socket_unittest.cc
@@ -358,7 +358,7 @@ TEST(TCPSocket, sequenceTest) {
     EXPECT_EQ(TCPCallback::OPEN, client_cb.called());
 
     // On some operating system the async_connect may return EINPROGRESS.
-    // This doesn't neccessarily indicate an error. In most cases trying
+    // This doesn't necessarily indicate an error. In most cases trying
     // to asynchronously write and read from the socket would work just
     // fine.
     if ((client_cb.getCode()) != 0 && (client_cb.getCode() != EINPROGRESS)) {
diff --git a/src/lib/http/tests/listener_unittests.cc b/src/lib/http/tests/listener_unittests.cc
index 4ccc0a51eb..3b6aa025ce 100644
--- a/src/lib/http/tests/listener_unittests.cc
+++ b/src/lib/http/tests/listener_unittests.cc
@@ -139,7 +139,7 @@ public:
                 // EINPROGRESS error code, but simply wait for the connection
                 // to get established before the handler is invoked. It turns out,
                 // however, that on some OSes the connect handler may receive this
-                // error code which doesn't neccessarily indicate a problem.
+                // error code which doesn't necessarily indicate a problem.
                 // Making an attempt to write and read from this socket will
                 // typically succeed. So, we ignore this error.
                 if (ec.value() != boost::asio::error::in_progress) {