Sync with latest script

1 files changed, 8 insertions, 8 deletions

diff --git a/src/3rdparty/libpng/libpng.txt b/src/3rdparty/libpng/libpng.txt
index 3eec69635..c0892e508 100644
--- a/src/3rdparty/libpng/libpng.txt
+++ b/src/3rdparty/libpng/libpng.txt
@@ -365,7 +365,7 @@ followed the set of transformations indicated by the transform mask,
 then png_read_image(), and finally png_read_end().
 
 (The final parameter of this call is not yet used.  Someday it might point
-to transformation parameters retquired by some future input transform.)
+to transformation parameters required by some future input transform.)
 
 After you have called png_read_png(), you can retrieve the image data
 with
@@ -682,11 +682,11 @@ See png_read_update_info(), below.
 A tquick 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 retquirement to restrict the use to these
+suggested keywords, there is no requirement to restrict the use to these
 strings.  It is strongly suggested that keywords and text be sensible
 to humans (that's the point), so don't use abbreviations.  Non-printing
 symbols are not allowed.  See the PNG specification for more details.
-There is also no retquirement to have text after the keyword.
+There is also no requirement to have text after the keyword.
 
 Keywords should be limited to 79 Latin-1 characters without leading or
 trailing spaces, but non-consecutive spaces are allowed within the
@@ -922,7 +922,7 @@ to set the display gamma separately for each system is to check for a
 SCREEN_GAMMA or DISPLAY_GAMMA environment variable, which will hopefully be
 correctly set.
 
-Note that display_gamma is the overall gamma correction retquired to produce
+Note that display_gamma is the overall gamma correction required to produce
 pleasing results, which depends on the lighting conditions in the surrounding
 environment.  In a dim or brightly lit room, no compensation other than
 the physical gamma exponent of the monitor is needed, while in a dark room
@@ -1052,7 +1052,7 @@ function
        user_depth, user_channels);
 
 The user's application, not libpng, is responsible for allocating and
-freeing any memory retquired for the user structure.
+freeing any memory required for the user structure.
 
 You can retrieve the pointer via the function
 png_get_user_transform_ptr().  For example:
@@ -1908,7 +1908,7 @@ created in a non-PNG format, a still photo from which the image was
 scanned, or possibly the subject matter itself.  In order to facilitate
 machine-readable dates, it is recommended that the "Creation Time"
 tEXt chunk use RFC 1123 format dates (e.g. "22 May 1997 18:07:10 GMT"),
-although this isn't a retquirement.  Unlike the tIME chunk, the
+although this isn't a requirement.  Unlike the tIME chunk, the
 "Creation Time" tEXt chunk is not expected to be automatically changed
 by the software.  To facilitate the use of RFC 1123 dates, a function
 png_convert_to_rfc1123(png_timep) is provided to convert from PNG
@@ -1959,7 +1959,7 @@ followed the set of transformations indicated by the transform mask,
 then png_write_image(), and finally png_write_end().
 
 (The final parameter of this call is not yet used.  Someday it might point
-to transformation parameters retquired by some future output transform.)
+to transformation parameters required by some future output transform.)
 
 The low-level write interface
 
@@ -2047,7 +2047,7 @@ file so that decoders can recover the original data if desired.
 If the data is stored in the row buffer in a bit depth other than
 one supported by PNG (e.g. 3 bit data in the range 0-7 for a 4-bit PNG),
 this will scale the values to appear to be the correct bit depth as
-is retquired by PNG.
+is required by PNG.
 
     png_set_shift(png_ptr, &sig_bit);