summaryrefslogtreecommitdiffstats
path: root/src/3rdparty/libmng/doc
diff options
context:
space:
mode:
Diffstat (limited to 'src/3rdparty/libmng/doc')
-rw-r--r--src/3rdparty/libmng/doc/libmng.txt4
-rw-r--r--src/3rdparty/libmng/doc/man/libmng.34
2 files changed, 4 insertions, 4 deletions
diff --git a/src/3rdparty/libmng/doc/libmng.txt b/src/3rdparty/libmng/doc/libmng.txt
index 67b26f509..95c086db6 100644
--- a/src/3rdparty/libmng/doc/libmng.txt
+++ b/src/3rdparty/libmng/doc/libmng.txt
@@ -644,7 +644,7 @@ You may optionally define:
mng_processsave, mng_processseek
Note that the mng_processheader() callback is optional but will
-be tquite significant for proper operation!
+be quite significant for proper operation!
Displaying an image will fail if you are creating a file or already
displaying one. Yes, you can't display it twice!
@@ -979,7 +979,7 @@ by using the mng_getlasterror() function:
Please note that you must have a pretty good understanding of the chunk
specification. Unlike the read functions, there are virtually no checks,
-so it is tquite possible to write completely wrong files.
+so it is quite possible to write completely wrong files.
It is a good practice to read back your file into the library to verify
its integrity.
diff --git a/src/3rdparty/libmng/doc/man/libmng.3 b/src/3rdparty/libmng/doc/man/libmng.3
index 3c88d8a06..c86faf615 100644
--- a/src/3rdparty/libmng/doc/man/libmng.3
+++ b/src/3rdparty/libmng/doc/man/libmng.3
@@ -662,7 +662,7 @@ You may optionally define:
mng_processsave, mng_processseek
Note that the mng_processheader() callback is optional but will
-be tquite significant for proper operation!
+be quite significant for proper operation!
Displaying an image will fail if you are creating a file or already
displaying one. Yes, you can't display it twice!
@@ -999,7 +999,7 @@ by using the mng_getlasterror() function:
Please note that you must have a pretty good understanding of the chunk
specification. Unlike the read functions, there are virtually no checks,
-so it is tquite possible to write completely wrong files.
+so it is quite possible to write completely wrong files.
It is a good practice to read back your file into the library to verify
its integrity.