about summary refs log tree commit diff
path: root/malloc/malloc.c
diff options
context:
space:
mode:
authorOndřej Bílka <neleai@seznam.cz>2013-08-29 09:08:54 +0200
committerOndřej Bílka <neleai@seznam.cz>2013-08-29 09:11:45 +0200
commit6f65e668957a50e153cba6822f747d13ad1b40ad (patch)
treedec30aa85e57419ac1eafffeab8548c973cac02f /malloc/malloc.c
parentd0721e703d222c01a9e8c329311c4fb01dac6972 (diff)
downloadglibc-6f65e668957a50e153cba6822f747d13ad1b40ad.tar.gz
glibc-6f65e668957a50e153cba6822f747d13ad1b40ad.tar.xz
glibc-6f65e668957a50e153cba6822f747d13ad1b40ad.zip
Fix typos.
Diffstat (limited to 'malloc/malloc.c')
-rw-r--r--malloc/malloc.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/malloc/malloc.c b/malloc/malloc.c
index be472b2ba3..dd295f522c 100644
--- a/malloc/malloc.c
+++ b/malloc/malloc.c
@@ -1167,7 +1167,7 @@ nextchunk-> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     the malloc code, but "mem" is the pointer that is returned to the
     user.  "Nextchunk" is the beginning of the next contiguous chunk.
 
-    Chunks always begin on even word boundries, so the mem portion
+    Chunks always begin on even word boundaries, so the mem portion
     (which is returned to the user) is also on an even word boundary, and
     thus at least double-word aligned.