Automated update from Qt3

1 files changed, 4 insertions, 4 deletions

diff --git a/src/3rdparty/libpng/libpng.3 b/src/3rdparty/libpng/libpng.3
index 249fc0959..b54b54799 100644
--- a/src/3rdparty/libpng/libpng.3
+++ b/src/3rdparty/libpng/libpng.3
@@ -957,7 +957,7 @@ pointers to error handling functions, and a pointer to a data struct for
 use by the error functions, if necessary (the pointer and functions can
 be NULL if the default error handlers are to be used).  See the section
 on Changes to Libpng below regarding the old initialization functions.
-The structure allocation functions tquietly return NULL if they fail to
+The structure allocation functions quietly return NULL if they fail to
 create the structure, so your application should check for that.
 
     png_structp png_ptr = png_create_read_struct
@@ -1470,7 +1470,7 @@ rowbytes, as some of the transformations could increase the space
 needed to hold a row (expand, filler, gray_to_rgb, etc.).
 See png_read_update_info(), below.
 
-A tquick word about text_ptr and num_text.  PNG stores comments in
+A quick word about text_ptr and num_text.  PNG stores comments in
 keyword/text pairs, one pair per chunk, with no limit on the number
 of text chunks, and a 2^31 byte limit on their size.  While there are
 suggested keywords, there is no requirement to restrict the use to these
@@ -2626,7 +2626,7 @@ structure (that is, the value of "i", which is the order in which
 the chunk was either read from the input file or defined with
 png_set_unknown_chunks).
 
-A tquick word about text and num_text.  text is an array of png_text
+A quick word about text and num_text.  text is an array of png_text
 structures.  num_text is the number of valid structures in the array.
 Each png_text structure holds a language code, a keyword, a text value,
 and a compression type.
@@ -3200,7 +3200,7 @@ library code itself needs to know about interactions between your
 chunk and existing `intrinsic' chunks.
 
 If you need to write a new intrinsic chunk, first read the PNG
-specification. Actquire a first level of
+specification. Acquire a first level of
 understanding of how it works.  Pay particular attention to the
 sections that describe chunk names, and look at how other chunks were
 designed, so you can do things similarly.  Second, check out the