From: Mark Adler Date: Sun, 30 Oct 2016 15:36:13 +0000 (-0700) Subject: Fix some typos. X-Git-Tag: 1.9.9-b1~730 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=a1b5cbc8c87ff252c7bdc4195632ca26200bf4f1;p=thirdparty%2Fzlib-ng.git Fix some typos. --- diff --git a/ChangeLog.zlib b/ChangeLog.zlib index 909d11f9b..2adb46810 100644 --- a/ChangeLog.zlib +++ b/ChangeLog.zlib @@ -200,7 +200,7 @@ Changes in 1.2.5.2 (17 Dec 2011) - Add a transparent write mode to gzopen() when 'T' is in the mode - Update python link in zlib man page - Get inffixed.h and MAKEFIXED result to match -- Add a ./config --solo option to make zlib subset with no libary use +- Add a ./config --solo option to make zlib subset with no library use - Add undocumented inflateResetKeep() function for CAB file decoding - Add --cover option to ./configure for gcc coverage testing - Add #define ZLIB_CONST option to use const in the z_stream interface @@ -1273,7 +1273,7 @@ Changes in 1.0.1 (20 May 96) [1.0 skipped to avoid confusion] - fix array overlay in deflate.c which sometimes caused bad compressed data - fix inflate bug with empty stored block - fix MSDOS medium model which was broken in 0.99 -- fix deflateParams() which could generated bad compressed data. +- fix deflateParams() which could generate bad compressed data. - Bytef is define'd instead of typedef'ed (work around Borland bug) - added an INDEX file - new makefiles for DJGPP (Makefile.dj2), 32-bit Borland (Makefile.b32), diff --git a/zlib.h b/zlib.h index 48187e9ca..94119d594 100644 --- a/zlib.h +++ b/zlib.h @@ -484,7 +484,7 @@ ZEXTERN int ZEXPORT inflate(z_stream *strm, int flush); instead use raw inflate, see inflateInit2() below, or inflateBack() and perform their own processing of the gzip header and trailer. When processing gzip-wrapped deflate data, strm->adler32 is set to the CRC-32 of the output - producted so far. The CRC-32 is checked against the gzip trailer. + produced so far. The CRC-32 is checked against the gzip trailer. inflate() returns Z_OK if some progress has been made (more input processed or more output produced), Z_STREAM_END if the end of the compressed data has @@ -1410,7 +1410,7 @@ ZEXTERN int ZEXPORT gzflush(gzFile file, int flush); If the flush parameter is Z_FINISH, the remaining data is written and the gzip stream is completed in the output. If gzwrite() is called again, a new gzip stream will be started in the output. gzread() is able to read such - concatented gzip streams. + concatenated gzip streams. gzflush should be called only when strictly necessary because it will degrade compression if called too often.