From 3f2246801725708d86711d36fe1c11fd377bef8b Mon Sep 17 00:00:00 2001
From: jmc <>
Date: Mon, 1 Aug 2005 19:44:53 +0000
Subject: kernal->kernel; from netbsd pr #30872 (anonymous post); ok deraadt@
 krw@

---
 src/lib/libssl/src/test/times | 2 +-
 src/lib/libssl/test/times     | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

(limited to 'src/lib')

diff --git a/src/lib/libssl/src/test/times b/src/lib/libssl/src/test/times
index 49aeebf216..738d569b8f 100644
--- a/src/lib/libssl/src/test/times
+++ b/src/lib/libssl/src/test/times
@@ -68,7 +68,7 @@ eric (adding numbers to speculation)
 --- Appendix ---
 - The time measured is user time but these number a very rough.
 - Remember this is the cost of both client and server sides of the protocol.
-- The TCP/kernal overhead of connection establishment is normally the
+- The TCP/kernel overhead of connection establishment is normally the
   killer in SSL.  Often delays in the TCP protocol will make session-id
   reuse look slower that new sessions, but this would not be the case on
   a loaded server.
diff --git a/src/lib/libssl/test/times b/src/lib/libssl/test/times
index 49aeebf216..738d569b8f 100644
--- a/src/lib/libssl/test/times
+++ b/src/lib/libssl/test/times
@@ -68,7 +68,7 @@ eric (adding numbers to speculation)
 --- Appendix ---
 - The time measured is user time but these number a very rough.
 - Remember this is the cost of both client and server sides of the protocol.
-- The TCP/kernal overhead of connection establishment is normally the
+- The TCP/kernel overhead of connection establishment is normally the
   killer in SSL.  Often delays in the TCP protocol will make session-id
   reuse look slower that new sessions, but this would not be the case on
   a loaded server.
-- 
cgit v1.2.3-55-g6feb