From 8d770ece9a55befb36364ae7975f5be4e67efe6d Mon Sep 17 00:00:00 2001 From: Andrew Murray Date: Tue, 16 Jun 2015 15:07:20 +1000 Subject: [PATCH] Fixed typos --- NEWS | 2 +- README.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/NEWS b/NEWS index 2fecd4ac..1a6aaa07 100644 --- a/NEWS +++ b/NEWS @@ -36,7 +36,7 @@ API/ABI modifications: (see abi_compat_report in dev-utils/scripts) Misc: - * OpenJPEG is now officialy conformant with JPEG 2000 Part-1 + * OpenJPEG is now officially conformant with JPEG 2000 Part-1 and will soon become official reference software at the JPEG committee. * Huge amount of bug fixes. See CHANGES for details. diff --git a/README.md b/README.md index 71610954..ab31260c 100644 --- a/README.md +++ b/README.md @@ -36,11 +36,11 @@ See [NEWS](https://github.com/uclouvain/openjpeg/blob/master/NEWS) for user visi ## API/ABI OpenJPEG strives to provide a stable API/ABI for your applications. As such it -only exposes a limited subset of its functions. It uses a mecanism of +only exposes a limited subset of its functions. It uses a mechanism of exporting/hiding functions. If you are unsure which functions you can use in your applications, you should compile OpenJPEG using something similar to gcc: `fvisibility=hidden` compilation flag. See also: http://gcc.gnu.org/wiki/Visibility -On windows, MSVC directly supports export/hidding function and as such the only +On windows, MSVC directly supports export/hiding function and as such the only API available is the one supported by OpenJPEG.