From d10abf84ad9f508e5e58ec76f90e960eef228b3f Mon Sep 17 00:00:00 2001 From: Gordon Bergling Date: Sat, 9 Apr 2022 09:36:34 +0200 Subject: libkern: Fix two typos in source code comments - s/noticably/noticeably/ MFC after: 3 days --- sys/libkern/jenkins_hash.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'sys/libkern') diff --git a/sys/libkern/jenkins_hash.c b/sys/libkern/jenkins_hash.c index 089de4e1d991..250ef458aa67 100644 --- a/sys/libkern/jenkins_hash.c +++ b/sys/libkern/jenkins_hash.c @@ -241,7 +241,7 @@ uint32_t jenkins_hash( const void *key, size_t length, uint32_t initval) * rest of the string. Every machine with memory protection I've seen * does it on word boundaries, so is OK with this. But VALGRIND will * still catch it and complain. The masking trick does make the hash - * noticably faster for short strings (like English words). + * noticeably faster for short strings (like English words). */ switch(length) @@ -394,7 +394,7 @@ uint32_t jenkins_hash( const void *key, size_t length, uint32_t initval) * rest of the string. Every machine with memory protection I've seen * does it on word boundaries, so is OK with this. But VALGRIND will * still catch it and complain. The masking trick does make the hash - * noticably faster for short strings (like English words). + * noticeably faster for short strings (like English words). */ switch(length) -- cgit v1.3