diff options
| author | luz.paz <luzpaz@users.noreply.github.com> | 2018-05-21 14:22:49 -0400 |
|---|---|---|
| committer | luz.paz <luzpaz@users.noreply.github.com> | 2018-05-21 14:22:49 -0400 |
| commit | 1e012029923cf95f34483d81d889ad3f20793a57 (patch) | |
| tree | 907bb1f4deeb56f920b14c1326979781a1098ac7 /src/cmserr.c | |
| parent | 684dfb820b6eb797fb18e35cdfe05c1ae70e9816 (diff) | |
| download | lcms2-1e012029923cf95f34483d81d889ad3f20793a57.tar.gz | |
Misc. typos
Found via `codespell -q 3`
Diffstat (limited to 'src/cmserr.c')
| -rw-r--r-- | src/cmserr.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/cmserr.c b/src/cmserr.c index 30408f8..1c2d0d0 100644 --- a/src/cmserr.c +++ b/src/cmserr.c @@ -435,7 +435,7 @@ void* _cmsSubAllocDup(_cmsSubAllocator* s, const void *ptr, cmsUInt32Number size // There is no error handling at all. When a function fails, it returns proper value. // For example, all create functions does return NULL on failure. Other return FALSE // It may be interesting, for the developer, to know why the function is failing. -// for that reason, lcms2 does offer a logging function. This function does recive +// for that reason, lcms2 does offer a logging function. This function does receive // a ENGLISH string with some clues on what is going wrong. You can show this // info to the end user, or just create some sort of log. // The logging function should NOT terminate the program, as this obviously can leave |