X-Git-Url: https://git.ozlabs.org/?a=blobdiff_plain;f=ccan%2Fhash%2Fhash.c;h=88d88fcc74614fa4a86e3bb5038329c5a8d4c21a;hb=d1a951b82386391b82e48b32403891f85e253565;hp=5ccc695505e76929cffccc7a4f5dbbde44e7f72d;hpb=55d814230f7fb628bb5303cd53498209c7928040;p=ccan

diff --git a/ccan/hash/hash.c b/ccan/hash/hash.c
index 5ccc6955..88d88fcc 100644
--- a/ccan/hash/hash.c
+++ b/ccan/hash/hash.c
@@ -281,7 +281,7 @@ static uint32_t hashlittle( const void *key, size_t length, uint32_t *val2 )
      * 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).
      *
      * Not on my testing with gcc 4.5 on an intel i5 CPU, at least --RR.
      */
@@ -458,7 +458,7 @@ static uint32_t hashbig( const void *key, size_t length, uint32_t *val2)
      * 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).
      *
      * Not on my testing with gcc 4.5 on an intel i5 CPU, at least --RR.
      */