From 76d5b5874e34d380a12ab3fb95944d952ba08a13 Mon Sep 17 00:00:00 2001 From: Olaf Barthel Date: Thu, 10 Jul 2025 13:17:30 +0200 Subject: [PATCH] Very minor documentation cleanup --- library/changes | 4 ++-- library/stdlib_malloc.c | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/library/changes b/library/changes index f6b57d8..fbffe64 100644 --- a/library/changes +++ b/library/changes @@ -177,7 +177,7 @@ c.lib 1.206 (24.4.2015) - Removed the remains of all the stack extension and stack overflow/underflow checking code. It never actually worked. The bit that does work is the stack - usage measurement code, plus the bit that sets up the the custom stack + usage measurement code, plus the bit that sets up the custom stack according to local setting or by calling a query function. @@ -1355,7 +1355,7 @@ c.lib 1.187 (29.1.2005) adding/subtracting the local time zone. - Changed the algorithm that calculates the number of days that have passed - so far as used by the the __convert_time() function and the conversion + so far as used by the __convert_time() function and the conversion code in strftime(). - Also changed the algorithm used by strftime() to produce the week numbers diff --git a/library/stdlib_malloc.c b/library/stdlib_malloc.c index d228ab6..5678338 100644 --- a/library/stdlib_malloc.c +++ b/library/stdlib_malloc.c @@ -414,7 +414,7 @@ STDLIB_DESTRUCTOR(stdlib_memory_exit) /* Make sure that freeing any memory does not also * trigger the alloca cleanup operations. Otherwise, - * the the data structures used by alloca() to track + * the data structures used by alloca() to track * the scope in which allocated memory remains * valid and should not be freed just yet may be * freed, corrupting them.